'Picking request file' and 'Picking confirmation file'...

Hi,
Suppose the business scenario like this:
After delivery created in SAP system, then the system generate an 'Picking request file' to 3rd party shipper service provider.
And then 3rd party shipper service provide will generate an 'Picking confirmation file' to our SAP system.
Upon receiving the picking confimation, then further invoice or PGI will be done.
In your previous experience, what kind of data exchaging mechanism is used for this kind of exchanging??
And what the exact content or data in your case for these 2 documents??
One is Picking request..
One is Picking confirmation...
Thank you very much.

You can explore using EDI
u2022 943: Receiving Schedule
u2022 944: Receiving Confirmation
regards
Biju

Similar Messages

Need API Name for PIck Release and Ship Confirm for WMS Module

Hi All,
One if my requirement is that Initially I will create Internal Sales Order and send to the other system (legacy) there they do the shipping then they provide the flat file which contains shipping information. Based on the incoming file I will close the order. Here they are using the WMS to process the pick release and ship confirm.
Can any one please help me how to do pick release and ship confirm by using an API or Interface in WMS. If knows please provide the name of the API's and flow.
Thanks,
Prasanna

For external orders we have a solution on WMS_DEVICE_CONFIRMATION_PUB api.
may be you have done pick release using this api in WMS enabled organizations. After pick release
you can use WSH api to do Ship Confirm.
Anatoly.

Order Entry Without Pick Release And Ship Confirm

I would like to create a sales order in Order Entry (Release 11), but due to some integration requirement, I do not want to go through the Pick Release And Ship Confirmation process but then I would like to go through the AR interface and Autoinvoice process. Are there some interface tables that I can update and processes that I can submit in the background to simulate the Pick Release and Ship Confirm processes. Your advice is much appreciate. Thank you and God bless you.

Speaking as a functional person you can create an Invoice Only cycle, and it will not need to go through the Inventory module, requesting the Pick Release and Ship Confirmation. <BLOCKQUOTE>quote:<HR>Originally posted by williamson ():
I would like to create a sales order in Order Entry (Release 11), but due to some integration requirement, I do not want to go through the Pick Release And Ship Confirmation process but then I would like to go through the AR interface and Autoinvoice process. Are there some interface tables that I can update and processes that I can submit in the background to simulate the Pick Release and Ship Confirm processes. Your advice is much appreciate. Thank you and God bless you. <HR></BLOCKQUOTE>
null

I tried syncing my iPhone to Mac and got this message when iPhoto pictures got synced: " this iPhone couldn't be synced. The requested file could not be found". Help what do I do now?

I tried syncing my iPhone to Mac and got this message when iPhoto pictures got synced: " this iPhone couldn't be synced. The requested file could not be found". Help what do I do now?

Try deleting the iPod Photo Cache from your computer.
http://support.apple.com/kb/ts1314

Concurrent Request 를 처리하는 File과 Tables

제품 : AOL
작성날짜 : 2003-12-02
Concurrent Request 를 처리하는 File과 Tables
=================================================
PURPOSE
이 Note는 Concurrent Reqeust output & Log 의 저장위치와 DB내 저장되는
Object들에 대한 설명입니다. Purge Concurrent Request and Output을 실행할때 다음 table들의 해당 record들이 삭제됩니다.
Explanations
- FND_CONCURRENT_REQUESTS
This table contains a complete history of all concurrent requests and
stores information about all submitted jobs(requested directly or by a
report set) within applications.
There's one request_id for each requested job in this tables.
- FND_RUN_REQUESTS
When a user submits a report set, this table stores information about the
reports in the report set and the parameter values for each report.
Stores information about all request sets submittted within applications.
Columns parent_request_id and request_id reflect the job# for the
report-set and the jobs it calls to.
- FND_CONC_REQUEST_ARGUMENTS
This table records arguments passed by the concurrent manager to each program
it starts running.
FND_DUAL
This table records when requests do not update database tables.
FND_CONCURRENT_PROCESSES
This table records information about Oracle Applications and operating system
processes.
FND_CONC_STAT_LIST
This table collects runtime performance statistics for concurrent requests.
FND_CONC_STAT_SUMMARY
This table contains the concurrent program performance statistics generated by
the Purge Concurrent Request and/or Manager Data program.
The Purge Concurrent Request and/or Manager Data program uses the data in
FND_CONC_STAT_LIST to compute these statistics.
FND_CONC_PP_ACTIONS
Stores the post request processing actions(e.g., print, notify) for each
submitted request. There's a concurrent_request_id here for each request_id
in the FND_CONCURRENT_REQUESTS.
FND_RUN_REQ_PP_ACTIONS
Stores the post request processing actions(e.g., print, notify) for
submitted request set programs that are stored in FND_RUN_REQUESTS.
Reference Documents
Note 132823.1

Partial Pick Confirming Sales Order

Hi Folks,
I have a requirement where I have to Pick Confirm and Ship confirm Sales Order through API.
1. When the quantites to be picked are same as quantity ordered the code seems to work just fine.
But suppose in my example my quantity in SO line is 50 and I want to partially Ship confirm the lines lets say 20 quantites.
then which API i need to use?
The approach I am following is while pick confirming I am passing 20 quantites only and the ship confirming it.
I researched and found that we can use the following API to update shipping attributes 'WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes' but when I run it (I tried before and after Pick confirm) the API runs fine but no changes are getting affected and the code Pick confirms all the quantity.
Could some please help me with this.
Please find the codes for pick confirm and updating shipping attributes
Pick confirm code
DECLARE
lv_order_num number := 700145812;
vMoveOrderLineId NUMBER;
p_pick_conf_qty NUMBER;
pStatus VARCHAR2(100);
pMsgData VARCHAR2(4000);
v_movehdr_rec INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_movehdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_moveln_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_zero_tbl_p INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_d INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_tbl_o INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
v_moveln_val_tbl INV_MOVE_ORDER_PUB.TROLIN_VAL_TBL_TYPE;
v_mold_tbl INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
v_mold_tbl_p INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_mold_tbl INV_MO_LINE_DETAIL_UTIL.G_MMTT_TBL_TYPE;
l_moveln_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_trolin_rec INV_MOVE_ORDER_PUB.TROLIN_REC_TYPE;
l_trolin_tbl INV_MOVE_ORDER_PUB.TROLIN_TBL_TYPE;
l_return_status VARCHAR2(240);
l_msg_count NUMBER;
l_msg_data VARCHAR2(2000);
l_move_hdr_id NUMBER;
l_move_order_no NUMBER := 0;
v_return_values VARCHAR2(2000) := FND_API.G_TRUE;
v_move_hdr_rec INV_MOVE_ORDER_PUB.TROHDR_REC_TYPE;
v_move_hdr_val_rec INV_MOVE_ORDER_PUB.TROHDR_VAL_REC_TYPE;
v_api_pick_confirm NUMBER;
cv_fail VARCHAR2(100) := 'Fail';
cv_success VARCHAR2(100) := 'Success';
g_user_id number;
g_resp_id number;
g_resp_appl_id number;
p_user_name varchar2(100) := 'SYSADMIN';
p_resp_name varchar2(100) := 'Order Management Super User';
p_mo_apps varchar2(100) := 'ONT';
CURSOR c_mmtt_recs(vMoveOrderLineId NUMBER) IS
 SELECT transaction_header_id,
 transaction_temp_id,
 source_code,
 source_line_id,
 transaction_mode,
 lock_flag,
 last_update_date,
 last_updated_by,
 creation_date,
 created_by,
 last_update_login,
 request_id,
 program_application_id,
 program_id,
 program_update_date,
 inventory_item_id,
 revision,
 organization_id,
 subinventory_code,
 locator_id,
 transaction_quantity,
 primary_quantity,
 transaction_uom,
 transaction_cost,
 transaction_type_id,
 transaction_action_id,
 transaction_source_type_id,
 transaction_source_id,
 transaction_source_name,
 transaction_date,
 acct_period_id,
 distribution_account_id,
 transaction_reference,
 requisition_line_id,
 requisition_distribution_id,
 reason_id,
 lot_number,
 lot_expiration_date,
 serial_number,
 receiving_document,
 demand_id,
 rcv_transaction_id,
 move_transaction_id,
 completion_transaction_id,
 wip_entity_type,
 schedule_id,
 repetitive_line_id,
 employee_code,
 primary_switch,
 schedule_update_code,
 setup_teardown_code,
 item_ordering,
 negative_req_flag,
 operation_seq_num,
 picking_line_id,
 trx_source_line_id,
 trx_source_delivery_id,
 physical_adjustment_id,
 cycle_count_id,
 rma_line_id,
 customer_ship_id,
 currency_code,
 currency_conversion_rate,
 currency_conversion_type,
 currency_conversion_date,
 ussgl_transaction_code,
 vendor_lot_number,
 encumbrance_account,
 encumbrance_amount,
 ship_to_location,
 shipment_number,
 transfer_cost,
 transportation_cost,
 transportation_account,
 freight_code,
 containers,
 waybill_airbill,
 expected_arrival_date,
 transfer_subinventory,
 transfer_organization,
 transfer_to_location,
 new_average_cost,
 value_change,
 percentage_change,
 material_allocation_temp_id,
 demand_source_header_id,
 demand_source_line,
 demand_source_delivery,
 item_segments,
 item_description,
 item_trx_enabled_flag,
 item_location_control_code,
 item_restrict_subinv_code,
 item_restrict_locators_code,
 item_revision_qty_control_code,
 item_primary_uom_code,
 item_uom_class,
 item_shelf_life_code,
 item_shelf_life_days,
 item_lot_control_code,
 item_serial_control_code,
 item_inventory_asset_flag,
 allowed_units_lookup_code,
 department_id,
 department_code,
 wip_supply_type,
 supply_subinventory,
 supply_locator_id,
 valid_subinventory_flag,
 valid_locator_flag,
 locator_segments,
 current_locator_control_code,
 number_of_lots_entered,
 wip_commit_flag,
 next_lot_number,
 lot_alpha_prefix,
 next_serial_number,
 serial_alpha_prefix,
 shippable_flag,
 posting_flag,
 required_flag,
 process_flag,
 error_code,
 error_explanation,
 attribute_category,
 attribute1,
 attribute2,
 attribute3,
 attribute4,
 attribute5,
 attribute6,
 attribute7,
 attribute8,
 attribute9,
 attribute10,
 attribute11,
 attribute12,
 attribute13,
 attribute14,
 attribute15,
 movement_id,
 reservation_quantity,
 shipped_quantity,
 transaction_line_number,
 task_id,
 to_task_id,
 source_task_id,
 project_id,
 source_project_id,
 pa_expenditure_org_id,
 to_project_id,
 expenditure_type,
 final_completion_flag,
 transfer_percentage,
 transaction_sequence_id,
 material_account,
 material_overhead_account,
 resource_account,
 outside_processing_account,
 overhead_account,
 flow_schedule,
 cost_group_id,
 demand_class,
 qa_collection_id,
 kanban_card_id,
 overcompletion_transaction_id,
 overcompletion_primary_qty,
 overcompletion_transaction_qty,
 end_item_unit_number,
 scheduled_payback_date,
 line_type_code,
 parent_transaction_temp_id,
 put_away_strategy_id,
 put_away_rule_id,
 pick_strategy_id,
 pick_rule_id,
 common_bom_seq_id,
 common_routing_seq_id,
 cost_type_id,
 org_cost_group_id,
 move_order_line_id,
 task_group_id,
 pick_slip_number,
 reservation_id,
 transaction_status,
 transfer_cost_group_id,
 lpn_id,
 transfer_lpn_id,
 pick_slip_date,
 content_lpn_id
 FROM MTL_MATERIAL_TRANSACTIONS_TEMP
 WHERE move_order_line_id = vMoveOrderLineId;
l_moveln_fidx NUMBER;
l_moveln_lidx NUMBER;
n_mvln_cntr NUMBER;
l_Index NUMBER := 1;
v_records_in_mmtt NUMBER := 0;
REC C_MMTT_RECS%ROWTYPE;
BEGIN
select user_id
 into g_user_id
 from fnd_user
 where user_name = p_user_name;
select responsibility_id, application_id
 into g_resp_id, g_resp_appl_id
 from apps.fnd_responsibility_vl
 where responsibility_name = p_resp_name;
Apps.FND_Global.Apps_Initialize(g_user_id, g_resp_id, g_resp_appl_id);
MO_GLOBAL.INIT(p_mo_apps);
for mol in (select wda.delivery_id,
 wda.delivery_detail_id,
 wda.parent_delivery_detail_id,
 wdd.source_code,
 wdd.inventory_item_id,
 wdd.organization_id,
 wdd.ship_from_location_id,
 wdd.ship_to_location_id,
 wdd.requested_quantity,
 wdd.requested_quantity_uom,
 wdd.move_order_line_id,
 wdd.org_id,
 mtrl.quantity,
 mtrl.quantity_delivered
 from wsh_delivery_details wdd,
 wsh_delivery_assignments wda,
 oe_order_lines_all ol,
 oe_order_headers_all oh,
 mtl_txn_request_lines mtrl,
 mtl_txn_request_headers mtrh
 where wdd.source_line_id = ol.line_id
 and wdd.delivery_detail_id = wda.delivery_detail_id
 and ol.header_id = oh.header_id
 and wdd.move_order_line_id = mtrl.line_id(+)
 and mtrl.header_id = mtrh.header_id(+)
 and oh.order_number = lv_order_num) loop
 vMoveOrderLineId := mol.move_order_line_id;
 p_pick_conf_qty := mol.quantity - nvl(mol.quantity_delivered,0);
 SELECT COUNT(move_order_line_id)
 INTO v_records_in_mmtt
 FROM MTL_MATERIAL_TRANSACTIONS_TEMP
 WHERE move_order_line_id = vMoveOrderLineId;
 IF v_records_in_mmtt > 1 THEN
 pStatus := cv_fail;
 pMsgData := 'Wrong number of records in MMTT for the MOVE_ORDER_LINE_ID : ' ||
 vMoveOrderLineId;
 DBMS_OUTPUT.PUT_LINE('Multiple records in MMTT for move_order_line_id = ' ||
 vMoveOrderLineId);
 v_api_pick_confirm := 0;
 GOTO end_of_pkcnf;
 ELSIF v_records_in_mmtt = 0 THEN
 --means that the delivery is already pick confirmed
 pStatus := cv_success;
 DBMS_OUTPUT.PUT_LINE('No records in MMTT for move_order_line_id = ' ||
 vMoveOrderLineId ||
 ' hence it is already pick confirmed');
 v_api_pick_confirm := 0;
 GOTO end_of_pkcnf;
 END IF;
 SELECT mtrh.header_id, mtrh.request_number
 INTO l_move_hdr_id, l_move_order_no
 FROM mtl_txn_request_headers mtrh, mtl_txn_request_lines mtrl
 WHERE mtrh.header_id = mtrl.header_id
 AND mtrl.line_id = vMoveOrderLineId;
 DBMS_OUTPUT.PUT_LINE('Obtained MTRH.HEADER_ID = ' || l_move_hdr_id ||
 ' MTRH.REQUEST_NUMBER = ' || l_move_order_no ||
 ' for move_order_line_id = ' || vMoveOrderLineId);
 INV_MOVE_ORDER_PUB.GET_MOVE_ORDER(p_api_version_number => 1.0,
 p_init_msg_list => FND_API.G_FALSE,
 p_return_values => v_return_values,
 x_return_status => l_return_status,
 x_msg_count => l_msg_count,
 x_msg_data => l_msg_data,
 p_header_id => l_move_hdr_id,
 p_header => l_move_order_no,
 x_trohdr_rec => v_move_hdr_rec,
 x_trohdr_val_rec => v_move_hdr_val_rec,
 x_trolin_tbl => v_moveln_tbl,
 x_trolin_val_tbl => v_moveln_val_tbl);
 COMMIT;
 DBMS_OUTPUT.PUT_LINE('Return status of INV_MOVE_ORDER_PUB.GET_MOVE_ORDER = ' ||
 l_return_status);
 IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
 pStatus := cv_fail;
 pMsgData := 'Failed to get move order inv_move_order_pub.get_move_order for MOVE_ORDER_LINE_ID : ' ||
 vMoveOrderLineId;
 GOTO end_of_pkcnf;
 END IF;
 OPEN c_mmtt_recs(vMoveOrderLineId);
 FETCH c_mmtt_recs
 INTO rec;
 CLOSE c_mmtt_recs;
 v_mold_tbl(1).transaction_header_id := rec.transaction_header_id;
 v_mold_tbl(1).transaction_temp_id := rec.transaction_temp_id;
 v_mold_tbl(1).source_code := rec.source_code;
 v_mold_tbl(1).source_line_id := rec.source_line_id;
 v_mold_tbl(1).transaction_mode := rec.transaction_mode;
 v_mold_tbl(1).lock_flag := rec.lock_flag;
 v_mold_tbl(1).last_update_date := rec.last_update_date;
 v_mold_tbl(1).last_updated_by := rec.last_updated_by;
 v_mold_tbl(1).creation_date := rec.creation_date;
 v_mold_tbl(1).created_by := rec.created_by;
 v_mold_tbl(1).last_update_login := rec.last_update_login;
 v_mold_tbl(1).request_id := rec.request_id;
 v_mold_tbl(1).program_application_id := rec.program_application_id;
 v_mold_tbl(1).program_id := rec.program_id;
 v_mold_tbl(1).program_update_date := rec.program_update_date;
 v_mold_tbl(1).inventory_item_id := rec.inventory_item_id;
 v_mold_tbl(1).revision := rec.revision;
 v_mold_tbl(1).organization_id := rec.organization_id;
 v_mold_tbl(1).subinventory_code := rec.subinventory_code;
 v_mold_tbl(1).locator_id := rec.locator_id;
 v_mold_tbl(1).transaction_quantity := rec.transaction_quantity;
 v_mold_tbl(1).primary_quantity := rec.primary_quantity;
 v_mold_tbl(1).transaction_uom := rec.transaction_uom;
 v_mold_tbl(1).transaction_cost := rec.transaction_cost;
 v_mold_tbl(1).transaction_type_id := rec.transaction_type_id;
 v_mold_tbl(1).transaction_action_id := rec.transaction_action_id;
 v_mold_tbl(1).transaction_source_type_id := rec.transaction_source_type_id;
 v_mold_tbl(1).transaction_source_id := rec.transaction_source_id;
 v_mold_tbl(1).transaction_source_name := rec.transaction_source_name;
 v_mold_tbl(1).transaction_date := rec.transaction_date;
 v_mold_tbl(1).acct_period_id := rec.acct_period_id;
 v_mold_tbl(1).distribution_account_id := rec.distribution_account_id;
 v_mold_tbl(1).transaction_reference := rec.transaction_reference;
 v_mold_tbl(1).requisition_line_id := rec.requisition_line_id;
 v_mold_tbl(1).requisition_distribution_id := rec.requisition_distribution_id;
 v_mold_tbl(1).reason_id := rec.reason_id;
 v_mold_tbl(1).lot_number := rec.lot_number;
 v_mold_tbl(1).lot_expiration_date := rec.lot_expiration_date;
 v_mold_tbl(1).serial_number := rec.serial_number;
 v_mold_tbl(1).receiving_document := rec.receiving_document;
 v_mold_tbl(1).demand_id := rec.demand_id;
 v_mold_tbl(1).rcv_transaction_id := rec.rcv_transaction_id;
 v_mold_tbl(1).move_transaction_id := rec.move_transaction_id;
 v_mold_tbl(1).completion_transaction_id := rec.completion_transaction_id;
 v_mold_tbl(1).wip_entity_type := rec.wip_entity_type;
 v_mold_tbl(1).schedule_id := rec.schedule_id;
 v_mold_tbl(1).repetitive_line_id := rec.repetitive_line_id;
 v_mold_tbl(1).employee_code := rec.employee_code;
 v_mold_tbl(1).primary_switch := rec.primary_switch;
 v_mold_tbl(1).schedule_update_code := rec.schedule_update_code;
 v_mold_tbl(1).setup_teardown_code := rec.setup_teardown_code;
 v_mold_tbl(1).item_ordering := rec.item_ordering;
 v_mold_tbl(1).negative_req_flag := rec.negative_req_flag;
 v_mold_tbl(1).operation_seq_num := rec.operation_seq_num;
 v_mold_tbl(1).picking_line_id := rec.picking_line_id;
 v_mold_tbl(1).trx_source_line_id := rec.trx_source_line_id;
 v_mold_tbl(1).trx_source_delivery_id := rec.trx_source_delivery_id;
 v_mold_tbl(1).physical_adjustment_id := rec.physical_adjustment_id;
 v_mold_tbl(1).cycle_count_id := rec.cycle_count_id;
 v_mold_tbl(1).rma_line_id := rec.rma_line_id;
 v_mold_tbl(1).customer_ship_id := rec.customer_ship_id;
 v_mold_tbl(1).currency_code := rec.currency_code;
 v_mold_tbl(1).currency_conversion_rate := rec.currency_conversion_rate;
 v_mold_tbl(1).currency_conversion_type := rec.currency_conversion_type;
 v_mold_tbl(1).currency_conversion_date := rec.currency_conversion_date;
 v_mold_tbl(1).ussgl_transaction_code := rec.ussgl_transaction_code;
 v_mold_tbl(1).vendor_lot_number := rec.vendor_lot_number;
 v_mold_tbl(1).encumbrance_account := rec.encumbrance_account;
 v_mold_tbl(1).encumbrance_amount := rec.encumbrance_amount;
 v_mold_tbl(1).ship_to_location := rec.ship_to_location;
 v_mold_tbl(1).shipment_number := rec.shipment_number;
 v_mold_tbl(1).transfer_cost := rec.transfer_cost;
 v_mold_tbl(1).transportation_cost := rec.transportation_cost;
 v_mold_tbl(1).transportation_account := rec.transportation_account;
 v_mold_tbl(1).freight_code := rec.freight_code;
 v_mold_tbl(1).containers := rec.containers;
 v_mold_tbl(1).waybill_airbill := rec.waybill_airbill;
 v_mold_tbl(1).expected_arrival_date := rec.expected_arrival_date;
 v_mold_tbl(1).transfer_subinventory := rec.transfer_subinventory;
 v_mold_tbl(1).transfer_organization := rec.transfer_organization;
 v_mold_tbl(1).transfer_to_location := rec.transfer_to_location;
 v_mold_tbl(1).new_average_cost := rec.new_average_cost;
 v_mold_tbl(1).value_change := rec.value_change;
 v_mold_tbl(1).percentage_change := rec.percentage_change;
 v_mold_tbl(1).material_allocation_temp_id := rec.material_allocation_temp_id;
 v_mold_tbl(1).demand_source_header_id := rec.demand_source_header_id;
 v_mold_tbl(1).demand_source_line := rec.demand_source_line;
 v_mold_tbl(1).demand_source_delivery := rec.demand_source_delivery;
 v_mold_tbl(1).item_segments := rec.item_segments;
 v_mold_tbl(1).item_description := rec.item_description;
 v_mold_tbl(1).item_trx_enabled_flag := rec.item_trx_enabled_flag;
 v_mold_tbl(1).item_location_control_code := rec.item_location_control_code;
 v_mold_tbl(1).item_restrict_subinv_code := rec.item_restrict_subinv_code;
 v_mold_tbl(1).item_restrict_locators_code := rec.item_restrict_locators_code;
 v_mold_tbl(1).item_revision_qty_control_code := rec.item_revision_qty_control_code;
 v_mold_tbl(1).item_primary_uom_code := rec.item_primary_uom_code;
 v_mold_tbl(1).item_uom_class := rec.item_uom_class;
 v_mold_tbl(1).item_shelf_life_code := rec.item_shelf_life_code;
 v_mold_tbl(1).item_shelf_life_days := rec.item_shelf_life_days;
 v_mold_tbl(1).item_lot_control_code := rec.item_lot_control_code;
 v_mold_tbl(1).item_serial_control_code := rec.item_serial_control_code;
 v_mold_tbl(1).item_inventory_asset_flag := rec.item_inventory_asset_flag;
 v_mold_tbl(1).allowed_units_lookup_code := rec.allowed_units_lookup_code;
 v_mold_tbl(1).department_id := rec.department_id;
 v_mold_tbl(1).department_code := rec.department_code;
 v_mold_tbl(1).wip_supply_type := rec.wip_supply_type;
 v_mold_tbl(1).supply_subinventory := rec.supply_subinventory;
 v_mold_tbl(1).supply_locator_id := rec.supply_locator_id;
 v_mold_tbl(1).valid_subinventory_flag := rec.valid_subinventory_flag;
 v_mold_tbl(1).valid_locator_flag := rec.valid_locator_flag;
 v_mold_tbl(1).locator_segments := rec.locator_segments;
 v_mold_tbl(1).current_locator_control_code := rec.current_locator_control_code;
 v_mold_tbl(1).number_of_lots_entered := rec.number_of_lots_entered;
 v_mold_tbl(1).wip_commit_flag := rec.wip_commit_flag;
 v_mold_tbl(1).next_lot_number := rec.next_lot_number;
 v_mold_tbl(1).lot_alpha_prefix := rec.lot_alpha_prefix;
 v_mold_tbl(1).next_serial_number := rec.next_serial_number;
 v_mold_tbl(1).serial_alpha_prefix := rec.serial_alpha_prefix;
 v_mold_tbl(1).shippable_flag := rec.shippable_flag;
 v_mold_tbl(1).posting_flag := rec.posting_flag;
 v_mold_tbl(1).required_flag := rec.required_flag;
 v_mold_tbl(1).process_flag := rec.process_flag;
 v_mold_tbl(1).error_code := rec.error_code;
 v_mold_tbl(1).error_explanation := rec.error_explanation;
 v_mold_tbl(1).attribute_category := rec.attribute_category;
 v_mold_tbl(1).attribute1 := rec.attribute1;
 v_mold_tbl(1).attribute2 := rec.attribute2;
 v_mold_tbl(1).attribute3 := rec.attribute3;
 v_mold_tbl(1).attribute4 := rec.attribute4;
 v_mold_tbl(1).attribute5 := rec.attribute5;
 v_mold_tbl(1).attribute6 := rec.attribute6;
 v_mold_tbl(1).attribute7 := rec.attribute7;
 v_mold_tbl(1).attribute8 := rec.attribute8;
 v_mold_tbl(1).attribute9 := rec.attribute9;
 v_mold_tbl(1).attribute10 := rec.attribute10;
 v_mold_tbl(1).attribute11 := rec.attribute11;
 v_mold_tbl(1).attribute12 := rec.attribute12;
 v_mold_tbl(1).attribute13 := rec.attribute13;
 v_mold_tbl(1).attribute14 := rec.attribute14;
 v_mold_tbl(1).attribute15 := rec.attribute15;
 v_mold_tbl(1).movement_id := rec.movement_id;
 v_mold_tbl(1).reservation_quantity := rec.reservation_quantity;
 v_mold_tbl(1).shipped_quantity := rec.shipped_quantity;
 v_mold_tbl(1).transaction_line_number := rec.transaction_line_number;
 v_mold_tbl(1).task_id := rec.task_id;
 v_mold_tbl(1).to_task_id := rec.to_task_id;
 v_mold_tbl(1).source_task_id := rec.source_task_id;
 v_mold_tbl(1).project_id := rec.project_id;
 v_mold_tbl(1).source_project_id := rec.source_project_id;
 v_mold_tbl(1).pa_expenditure_org_id := rec.pa_expenditure_org_id;
 v_mold_tbl(1).to_project_id := rec.to_project_id;
 v_mold_tbl(1).expenditure_type := rec.expenditure_type;
 v_mold_tbl(1).final_completion_flag := rec.final_completion_flag;
 v_mold_tbl(1).transfer_percentage := rec.transfer_percentage;
 v_mold_tbl(1).transaction_sequence_id := rec.transaction_sequence_id;
 v_mold_tbl(1).material_account := rec.material_account;
 v_mold_tbl(1).material_overhead_account := rec.material_overhead_account;
 v_mold_tbl(1).resource_account := rec.resource_account;
 v_mold_tbl(1).outside_processing_account := rec.outside_processing_account;
 v_mold_tbl(1).overhead_account := rec.overhead_account;
 v_mold_tbl(1).flow_schedule := rec.flow_schedule;
 v_mold_tbl(1).cost_group_id := rec.cost_group_id;
 v_mold_tbl(1).demand_class := rec.demand_class;
 v_mold_tbl(1).qa_collection_id := rec.qa_collection_id;
 v_mold_tbl(1).kanban_card_id := rec.kanban_card_id;
 v_mold_tbl(1).overcompletion_transaction_id := rec.overcompletion_transaction_id;
 v_mold_tbl(1).overcompletion_primary_qty := rec.overcompletion_primary_qty;
 v_mold_tbl(1).overcompletion_transaction_qty := rec.overcompletion_transaction_qty;
 v_mold_tbl(1).end_item_unit_number := rec.end_item_unit_number;
 v_mold_tbl(1).scheduled_payback_date := rec.scheduled_payback_date;
 v_mold_tbl(1).line_type_code := rec.line_type_code;
 v_mold_tbl(1).parent_transaction_temp_id := rec.parent_transaction_temp_id;
 v_mold_tbl(1).put_away_strategy_id := rec.put_away_strategy_id;
 v_mold_tbl(1).put_away_rule_id := rec.put_away_rule_id;
 v_mold_tbl(1).pick_strategy_id := rec.pick_strategy_id;
 v_mold_tbl(1).pick_rule_id := rec.pick_rule_id;
 v_mold_tbl(1).common_bom_seq_id := rec.common_bom_seq_id;
 v_mold_tbl(1).common_routing_seq_id := rec.common_routing_seq_id;
 v_mold_tbl(1).cost_type_id := rec.cost_type_id;
 v_mold_tbl(1).org_cost_group_id := rec.org_cost_group_id;
 v_mold_tbl(1).move_order_line_id := rec.move_order_line_id;
 v_mold_tbl(1).task_group_id := rec.task_group_id;
 v_mold_tbl(1).pick_slip_number := rec.pick_slip_number;
 v_mold_tbl(1).reservation_id := rec.reservation_id;
 v_mold_tbl(1).transaction_status := rec.transaction_status;
 v_mold_tbl(1).transfer_cost_group_id := rec.transfer_cost_group_id;
 v_mold_tbl(1).lpn_id := rec.lpn_id;
 v_mold_tbl(1).transfer_lpn_id := rec.transfer_lpn_id;
 v_mold_tbl(1).pick_slip_date := rec.pick_slip_date;
 v_mold_tbl(1).content_lpn_id := rec.content_lpn_id;
 v_mold_tbl(1).transaction_quantity := p_pick_conf_qty;
 v_mold_tbl(1).primary_quantity := p_pick_conf_qty;
 v_mold_tbl(1).shipped_quantity := p_pick_conf_qty;
 INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM(p_api_version_number => 1.0,
 p_init_msg_list => FND_API.G_FALSE,
 p_commit => FND_API.G_FALSE,
 x_return_status => l_return_status,
 x_msg_count => l_msg_count,
 x_msg_data => l_msg_data,
 p_move_order_type => 3 -- PickWave - Order
 p_transaction_mode => 1 -- 1:On-Line, 2:Concurrent, 3:Background
 p_trolin_tbl => v_moveln_tbl_d,
 p_mold_tbl => v_mold_tbl,
 x_mmtt_tbl => v_mold_tbl,
 x_trolin_tbl => v_moveln_tbl_o,
 p_transaction_date => SYSDATE);
 COMMIT;
 DBMS_OUTPUT.PUT_LINE('Return status of INV_PICK_WAVE_PICK_CONFIRM_PUB.PICK_CONFIRM = ' ||
 l_return_status);
 IF l_return_status != FND_API.G_RET_STS_SUCCESS THEN
 pStatus := cv_fail;
 pMsgData := 'Failed to pick confirm move order inv_pick_wave_pick_confirm_pub.pick_confirm for MOVE_ORDER_LINE_ID : ' ||
 vMoveOrderLineId;
 GOTO end_of_pkcnf;
 END IF;
 v_api_pick_confirm := 1;
 dbms_output.put_line('Status of the Pick Confirm is : ' ||
 l_return_status);
 <<end_of_pkcnf>>
 NULL;
end loop;
END;
Updating Shipping attributes
DECLARE
--Standard Parameters.
p_api_version NUMBER;
init_msg_list VARCHAR2(30);
p_commit VARCHAR2(30);
--Parameters for WSH_DELIVERY_DETAILS_PUB.update_shipping_attributes.
source_code VARCHAR2(15);
changed_attributes WSH_DELIVERY_DETAILS_PUB.ChangedAttributeTabType;
--out parameters
x_return_status VARCHAR2(10);
x_msg_count NUMBER;
x_msg_data VARCHAR2(2000);
x_msg_details VARCHAR2(3000);
x_msg_summary VARCHAR2(3000);
-- Handle exceptions
vApiErrorException EXCEPTION;
BEGIN
-- Initialize return status
x_return_status := WSH_UTIL_CORE.G_RET_STS_SUCCESS;
-- Call this procedure to initialize applications parameters
FND_GLOBAL.APPS_INITIALIZE(user_id => 0,
 resp_id => 21623,
 resp_appl_id => 660);
source_code := 'OE';
changed_attributes(1).delivery_detail_id := 9317811; -- delivery_detail_id
changed_attributes(1).shipped_quantity := 0; -- quantity to update
changed_attributes(1).cycle_count_quantity := 30;
--Call to WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes.
WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes(p_api_version_number => 1.0,
 p_init_msg_list => init_msg_list,
 p_commit => p_commit,
 x_return_status => x_return_status,
 x_msg_count => x_msg_count,
 x_msg_data => x_msg_data,
 p_changed_attributes => changed_attributes,
 p_source_code => source_code);
 commit;
IF (x_return_status <> WSH_UTIL_CORE.G_RET_STS_SUCCESS) THEN
 RAISE vApiErrorException;
ELSE
 dbms_output.put_line('The shipped quantity is updated with ' ||
 changed_attributes(1)
 .shipped_quantity || ' for the delivery detail ' ||
 changed_attributes(1).delivery_detail_id);
END IF;
EXCEPTION
WHEN vApiErrorException THEN
 WSH_UTIL_CORE.get_messages('Y',
 x_msg_summary,
 x_msg_details,
 x_msg_count);
 IF x_msg_count > 1 THEN
 x_msg_data := x_msg_summary || x_msg_details;
 DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
 ELSE
 x_msg_data := x_msg_summary;
 DBMS_OUTPUT.PUT_LINE('Message Data : ' || x_msg_data);
 END IF;
WHEN OTHERS THEN
 DBMS_OUTPUT.PUT_LINE('Unexpected Error: ' || SQLERRM);
END;
Thanks

Hi,
Goto VTFL.Select you valid combination.
Click on item.Select yout item category there.Goto details.
Select the Pos/neg quantity field as "+".
Maintain the billing quantity as "A".
Maintain VBRK/VBRP as "001".
Save.
Goto VOV7 and select your item category.Details.
Select completion rule as "B" and billing relevance as "F".
Save.
Pls go through the follwing threads that are posted by me earlier.
[Invoice split|Re: Invoice split]
[Splitiing of invoice|Re: Invoice split]
Regards,
Krishna.

Is there a way to see the details of transport request files

hello friends
for some reason when I try to create a package with objects like function group and function modules, I am not able to import the function modules on the other server.
So i would like to see if the transport request files that I have created (K900226.EC1 and R900226.EC1) has these modules included in them.
Is there a way that I can see what objects are included in the released transport request files.
Your help will be greatly appreciated.
Thanks
Ram

Hi Ram,
You can see the objects included in a transport request by going to se09 and opening your transport request and drill down to the task and below the task you would have all the objects that are included in the tranport. You can also use se03 to get the details by drilling down the tansport request.
The problem with importing the function module might be because either the function module or the function group may not be active which may cause the tranport to fail. please check if both are active or not.

An error occurred during the compilation of the requested file, or one of its dependencies.

An error occurred during the compilation of the requested file, or one of its dependencies. The type or namespace name 'Directory Services' does not exist in the namespace 'System' (are you missing an assembly reference?)

Hello,
What you are trying to achieve and where you are getting this error?
If you facing issue with namespace then refer this link:
http://stackoverflow.com/questions/265096/system-directoryservices-is-not-recognised-in-the-namespace-system
http://stackoverflow.com/questions/10691001/the-type-or-namespace-name-directoryservices-does-not-exist-in-the-namespace
Hemendra:Yesterday is just a memory,Tomorrow we may never see
Please remember to mark the replies as answers if they help and unmark them if they provide no help

Disable auto Pick confirmation for EK00 output - Outbound Delivery

Hello experts,
Need help with Outbound Delivery Picking output typ EK00, I have setup the output type to be triggered automatically upon Delivery creation, It's printing the pick List as desired, But the problem is it's also confirming the Pick quantity automatically. Is there a way to set up this output to just print the PickList and not confirm the Pick Qty ?
Thanks for your help.
Kris T

Hello Kris,
If you want to deactivate automatic picking confirmation, you have remove condition type WMTA which results in automatic confirmation of picking.
Go to NACE
Application V2
Here output type/ Condition record WMTA needs to be removed.
Also you have reconfigure movement type settings.
SPRO>>LOGISTICS EXECUTION>>WAREHOUSE MANAGEMENT>>ACTIVITIES>>TRANSFERS>>DEFINE MOVEMENT TYPES
Execute.
select combination of warehouse number and movement type
ands reset the automatic TO indicator to keep it 'BLANK' in background processing Tab.
With this settings maintained you can stop picking status to 'C' automatically when delivery is cerated.
Br,
Tushar

Developing Permission Request File

Hi Everyone,
I am developing an ocap 'permission request file' to grant/fetch permissions for my application.
I am referring MHP1.2, particularly chapter 12 - Security in the spec.
First question:
Is <file> permission request is for requesting access to persistent files? I do not understand the necessity of this when <persistentfilecredential> is available. Can someone explain?
What does it mean if I specify <file value'"false"></file> in my permission request file?
Second question:
The spec says Conditional Access Permission is optional. But if present, the DTD definition for CA Permission is <!ELEMENT capermission (casystemid)+> and casystemid has a files "id" which is REQUIRED.
Who defines "casystemids"? Or simply what value should I use for a casystemid?
I would really appreciate your help.
Thanks.

First, thank you for your response and for the information. I appreciate it.
I humbly disagree on your first response that <file> is not an element of PRF (Permissions Request File).
Well in Application Description File, there is an element - <file> and also in Permission Request File.
In section 12.6.2.1.4 of MHP1.2, the DTD for the Permission Request File has the following definition:
<!ELEMENT permissionrequestfile (file?,capermission?,,......etc.,)
<!ELEMENT file EMPTY>
<!ATTLIST file
value (true|false) "true">
I was referring to this element <file> in my question.
Thanks for the explanation about Persist File Credential. Now, why element <file> when there is an
element <persistfilecredential> in Permission Request File? Please clarify?
Regarding, getCASystemIds(), thanks for pointing this out but someone (like me) who is defining a
Permission Request File for my application do not have the access to call this API, I mean I am
defining PRF to sign my application and so I am not touching my source and no compilation involved
at this point of time. Do you see my point? If not let me know, I will try in another way.
Thanks again for your time and information.

The requested file was not a valid font file

I have a serius problem with OTF fonts shipped with CS3 collection.
I had to reinstall windows to solve this issue a couple of months ago and now it's bugging me again.
When I double click on Minion (or other adobe OTF fonts) in fonts (control panel) i get this error:
"The requested file c:\windows\fonts\MinionPro-BoldCn.otf was not a valid font file"
And the worst thing is that the fonts are not being listed in any of the applications.
I opened my project today and I got an error saying that Minion pro bold was not found. I was working on that project yesterday. what could have heppened since then?
Please help me ASAP.
Thank you.

Chinese Arabic or Russian?
I hope some one can help me. It's not like my life depends on knowing this or not but I would really like to know what this clock is saying. It came in the mail from China a week ago and I have not been able to figure it out. I would guess because this LDU Company business is in China that it is Chinese, but you never know, maybe the clock was made in China for Russians? The website is www.lducompany.com and the link to the sega sonic the hedgehog clock is on this page http://www.liangdianup.com/clocks_1.htm
There is a video on thier website on the sonic hedgehog clock page and you can hear what the clock is saying. If some one could tell me exactly what it is saying I would appreciate it. Thank you :)

Transport request files creation

Hi to all,
I have one stand alone system which is not connected to any transport layer.
In this system we do lot's of development and now we install Development system We want to transport some requests from this stand alone system to our development system.
Problem is that after release of our transport requests files on usr\sap\trans\.... are not created. Becasue of that we can not copy files for transport on develeopment and import then there.
It's there some program, FM or tool so I can create transport files from transport requests.
Thanks a lot,
Drazen

Hi DL ,
one way to get changes is Manual Copy of Cofiles and Datafiles into ur DEV server.
Hi DL ,
just tell me Y SAP will not create Cofile and Data files , when i am creating Transport Request ? So u mean to say Transport Request contains nothing ?
Regards
Prabhu
Message was edited by:
Prabhu Peram

How to install transport request files into the SAP system

Hi Experts,
I want to install transport request files into my SAP source and target system . I am from BW/BI background so can anyone help me out with the step by step procedure for the above installation.
Thanks in advance
Regards
Shiva

Hi,
What I understand is, you want to transport request from one server to another.
for example, Development to Qualtiy or Quality to Production.
For this your transport system must be configured. Please search help.sap.com or google for "How to configure Transport System (STMS)".
If you want to copy transport request from one system to another system which is not in your landscape, you need to physically move/copy transport request (cofile and datafile) to the target system in /usr/sap/trans/cofiles and /usr/sap/trans/data
Then import that request using SCC1.
You can alos perform TEST import for result.
Regards.
Rajesh Narkhede

Picking confirmation using IDOC

Hi,
I have to create pick confirmation from WMS to SAP. I'm uing SHPCON message type and DELVRY03 basic type and idoc_input_delvry FM from my development. very this is fine i have got all fields reqired in basic type the problem is
1. IF WMS don;t send any pick quantity for line item or if it sends '0' quantity the line item has to be deleted from the Delivery.
2. If in case pick qty is more than the delivery qty it should generate an error.
3.Thre is a concept called Batch split in Outbound delivery. What it the functionality of the batch split.
Can any one come accross these kind of scenario plz help me.
Thanks & Regards,
Naren.

i think u r going to generate the 51 status for the conditions in ur idoc
for 1 and 2 .
Pick quantity is not maintained for the table . The reference for this is the Delivered Quantity.
Goto delivery (vl02n) and enter a delivery now see the delivery qty for a particular item .
say 16 for Del qty now keep pick qty as 0.
and save .
now see the over all pick status . this will be 'A'.
repeat the same process and now keep pick qty as 4 .
and save .
now see the over all pick status . this will be 'B'.
this becomes 'C' means completely picked if the pick qty is eq 16 in this scenario.
i cannot pick 17 as this is out of scope error will be triggered.
Pickup the segment which is populating the pick qty and keep the options above u
and compare it with delivered qty.
for 3 ..
refer this..
Let me put it this way.
The process is suppose a sales order is there
and that is scheduled
16 on dec 29
24 on dec 30
if i create a delivery as of today ie dec 29
then the pick qty is 16
and i create a delivery on dec 30 ie tommow
then the pick qty is 24.
total quantity for that item is 40 (break
16+24).
For this break up u need to look into Vbep
Entries .
This is the process of scheduling where in two
deliveries are created for one sales order .(as
example).
regards,
vijay.

Enhancement for picking confirmation inbound idoc

Hi Friends,
I'm using Message type SHPCON , Basic Type Delvry03 and process code DELV for picking confirmation. where as i have to extend the basic type for a field LIPS-UECHA ( Batch split Indicator) which is not avilable in basic type. which userexit or badi i have to use to plopoualte this filed data in to SAP? Can any one help.
Thanks&Regards,
Naren.

Hi,
You exttend the basic IDOC type DELVRY03. To which Segment you want to add this under E1EDL24 or E1EDL37. Change the process code inorder to fetch the data from the application.
WE31 to add the field to the segments and create a new segment
WE30 extend the basic type and add the newly created segment
WE82 to add the extended basic type to Message type.
change the process code.
Regards
Kannaiah

'Picking request file' and 'Picking confirmation file'...

Similar Messages

Maybe you are looking for