Self pick up freight order
Hi,
What is the basic difference between self pick up freight order and standard freight order.
For self pick FO; is it the same FO we use in the pre carriage ( stage 1) for transporting goods from shipper to the station on export side.
Hi, Dipak
Self pick-up freight order is related to self pick-up stage, which is a special stage type as the name indicates the customer pick-up his goods by himself. For this kind of stage, the carrier/freight forwarder don't have to deliver it, and thus don't need any planning for it and won't charge customer for it.
Best regards
Sensen
Similar Messages
-
Ocean Freight booking number from freight order - SAP TM
Hello experts,
I have a requirement to display Freight Booking Number on Adobe form (copy of standard SAP TM Form /SCMTMS/FP_FBL).
{ Steps to execute the form:- Go to NWBC - Freight Order Management - Edit Freight Order - Output Management - Generate List of Actions (Custom Action is configured here) - Document preview to open the form }
For the ocean freight order I need to display Ocean freight booking number on the form. Now on the print structure of the Form '/SCMTMS/S_PRINTOUT_FBL' only the existing document (ie freight order) related information is available not for the predecessor or successor documents.
I have found that these 2 documents (freight order & freight booking ) are related to freight unit (in my case ocean dry container) but I am unable to identify how they are directly related to each other in the system. Checked below link but still cant find any relation.
(Pick-up and Delivery Freight Orders - Freight Order Management - SAP Library)
Is there any way I can identify the freight booking number from freight order in SAP TM system?
Thanks in advance.
PuneetHi Matt,
you can find associations DRAYAGE_TOR (from booking to freight order(s)) and DRAYTOR_BOOK (from freight order to booking) under the ROOT node of business object /SCMTMS/TOR. If you check those in TA /BOBF/CONF_UI, you can also have a look at the corresponding implementing classes - however, there should be no need to do this
Technically, the references are stored on ITEM_TR level, but as determining the correct references can be tricky, I would strongly recommend to use the above mentioned associations in order to get the pre-carriage order (or booking vice versa), instead of trying to determine them on your own from various DB tables - we already implemented the tricky part in the associations, so there is no need for you to worry about that
Best regards,
Sabine -
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;
ThanksHi,
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. -
Issue in Credit Memo Posting in ECC against SAP TM Freight Order
Hello Experts,
I have created Credit Memo against TM Freight Order and Transferred to ECC.
Sender Outbound Service Interface on TM Side "TransportationOrderSUITEInvoicingPreparationRequest_Out" was successful.
But Receiver Inbound Service Interface on ECC Side is failing "TransportationOrderSUITEInvoicingPreparationRequest_In"
XML analysis gives below error message:
No instance of object type Purchase Order has been created. External reference
PO header data still faulty
Enter a vendor
Please enter items first
I was able to create a Service PO and Service Entry Sheet for FSD created against same Freight Order, so I don't see any issue in Config.
Thanks and Regards,
Arnab BiswasHi Arnab,
As understood, standard interface creates Service PO in ECC for your Freight order in SAP TM.
Then you are trying to create Invoicing document linked to the created service PO, which is just like FWSD of Freight order. Inbound XML data will give you thorough picture of this issue.
General Analysis :
When FWSD created in TM for Freight Order interface "TranspOrderSUITEInvoicingPreparationRequest_Out" is triggered and it will pass the same TM data of Freight Order to create invoice in ECC and not like the Service PO.
Kindly check your inbound XML with data in it.
You might need to change in outbound interface BADI while sending data out from SAP TM, or in inbound BADI to modify incoming data in ECC.
In SAP TM SPRO search with below content.
BAdI for TranspOrderSUITEInvoicingPreparationRequest_Out
or
you need to search inbound BADI in ECC side to make changes in inbound data.
Reward if found useful..
Thanks and Regards,
Kalpesh -
Automatic picked up purchase order during shipment cost cal
Hi,
We have one issue system picked up automatically Purchase order which having account assignment category "U".We have config new account assignment category "I" for some specific reason.Now we want that during shipment cost calculation (VI01) system automatically picked up purchase order with having account assignment category "I" intead of u.
Please guide.
Regards'
KumarDear Arif,
Please check the shipment document is there any error log exists
Check the shipment cost having the value and Transporter(Vendor) and it is getting transfer to FI.
After checking the transfer chek sytem will create the PO while saving the shipment cost document.
I hope it will help you,
Regards,
Murali. -
Condition type not picked in Inquiry but picked up in order
Hi Guys,
We have a problem where a pricing condition type is picked up in order but it is not picked up in quotation/inquiry. So we have the price difference for the material. Points will be awarded.
Can you guys please help?
Thanks
VenkyHi venky
generally in Inquiry pricing is not at all required.
but in quotation it may require sometimes. but when you create an order with reference to quotation , the price varies, this is because of the pricing type .
check the pricing type in VTAA quotation, the pricing type will be different for sales order and for quotation.
Regards
Srinath -
Can I buy online with a mexican credit card, and pick up my order in store days later?
Hello,
I live in Mexico, and i will be in San Diego for vacations next week.
I would like to buy some things from the apple store online with my mexican credit card,
so, i need to know if i can buy from here in Mexico with my credit card, and then when i arrive
to San Diego CA. i can pick-up my order in the Fashion valley Apple Store.
Can i do it this way? Thank you so much for your help. I will be waiting your answer.
Greetings,
Vanessa.No. A Mexican credit card will not be accepted in a US store. Even if you place your order in the Mexican online store, the order cannot ship to the US. If your permanent residence is in Mexico, then buy in Mexico where your warranties are honored.
-
I want to know that because I want to buy a iphone 4S unlocked with my father's credit card but the trouble is that we live in ECUADOR so my father cannot pick up that order.... but I have a uncle who live in United State that can pick up.... so I want to know if my uncle can pick up.
Sorry i don't speak english very well...
Thank you.I can't think of any way to do that other than have your uncle purchase the phone with your uncle's credit card, and you reimburse him.
Keep in mind that if the phone needs to be repaired it must be returned to the US. You would be better off buying it in Equador - https://www.apple.com/la/iphone/ -
Check the Freight order locked status in TM 8.0
Hi All,
Is there any method to check whether the Freight order is locked for processing, other than the messages obtained when the
Freight order is called for update and it returns a message, the Order is locked and cannot be processed.
Also can you please provide me the links, where I can find useful information regarding the TM 8.0
Regards,
Joseph MGo to EDIT Freight order link, open the FO
DATA: lo_srvmgr_tor TYPE REF TO /bobf/if_tra_service_manager,
lt_tor_key TYPE /bobf/t_frw_key,
lo_message TYPE REF TO /bobf/if_frw_message,
ls_tor_id TYPE /scmtms/tor_id,
lt_tor_id TYPE /scmtms/t_tor_id.
lo_srvmgr_tor = /bobf/cl_tra_serv_mgr_factory=>get_service_manager( iv_bo_key = /scmtms/if_tor_c=>sc_bo_key ).
ls_tor_id = '00000000000000010037'.
APPEND ls_tor_id TO lt_tor_id.
CALL METHOD lo_srvmgr_tor->convert_altern_key(
EXPORTING
iv_node_key = /scmtms/if_tor_c=>sc_node-root
iv_altkey_key = /scmtms/if_tor_c=>sc_alternative_key-root-tor_id
it_key = lt_tor_id
IMPORTING
et_key = lt_tor_key ).
CALL METHOD lo_srvmgr_tor->retrieve
EXPORTING
iv_node_key = /scmtms/if_tor_c=>sc_node-root
iv_edit_mode = /bobf/if_conf_c=>sc_edit_exclusive
it_key = lt_tor_key
iv_fill_data = abap_false
IMPORTING
eo_message = lo_message
lo_message will have MT_MESSAGE that will be filled with message.
/SCMTMS/MSG 251 252 253 -
Hi
I am new to TM 8.0. Currently I am working on an enhancement related to Freight order. I need to perform Charge calculation in the Freight order to create Freight settlement document, which will be invoiced later in ECC system.
I need to know where I can create the Freight agreement, since the charge calculation fails stating that "Freight agreement does not exist"
Is there any transaction where I can create Freight agreement other than NWBC.
Please help me in this regard.
Regards,
Joseph MHi Joseph,
This is part of master data. Go to: Master Data -> Charge Management -> Freight Agreements.
For the thing you are doing you probably also need to create a calculation sheet, and maybe also rate tables and scales.
Kind regards,
Nico. -
Forwarding order as a subsequent transaction for Freight order
Hi Experts,
I have a scenario like Shipper sub contracts the containers to different trucks and subsequently same containers loaded into vessel and later on these containers delivered to consignee using another sub contract with trucking company.
So here I want to link the initial subcontract freight order to the vessel forwarding order and the document flow would be like - Freight order - Forwarding order - Freight order.
Please advise if above scenario is possible.
Regards,
Shaktihttp://help.sap.com/transportationmanagement91
International Outbound scenario explained in standard SAP documentation will be helpful.
I don't have any standard document to explain this. I can publish a blog for this [This will take some time].
However, the design depends on the master data you have for lanes and schedules.
One possible way to execute the above scenario is: [Manual planning]
1. Assign the Port of Netherlands to Berlin Plant as a transshipment location
2. Assign Port of Houston to Customer Location as transshipment location.
3. Maintain lanes for Berlin to Port of Netherlands, Port of Netherlands to Port of Houston and Port of Houston to Customer location.
4. Use rough cut planning and use transportation proposal in cockpit. This will spilt the FU stage into three.
5. Plan individually these three stages in separate cockpits for Truck and Ocean to create FOs and FB accordingly.
Note: You can automate many of these planning stages if you have proper master data. -
Why do I have to change source input to mono when it's recorded in stereo through my interface from an acoustic pick up in order to hear anything in playback?
It's a dean markley acoustic pick up with a mono 1/4" jack. It's plugged into a focusrite interface. GarageBand only records it in stereo and only plays it back in mono.Watts100woo wrote:
with a mono 1/4" jack. It's plugged into a focusrite interface. GarageBand only records it in stereo and only plays it back in mono.
you appear to already know the answer, however...
GB is not recording it in stereo, nor could it
the short story:
http://www.bulletsandbones.com/GB/GBFAQ.html#leftspeakeronly
(Let the page FULLY load. The link to your answer is at the top of your screen)
the long story:
http://www.bulletsandbones.com/GB/Tutorials.html#bsqstereovsmono
(Let the page FULLY load. The link to your answer is at the top of your screen) -
Fetch Charge item present under TransportCharges node for Freight order
Hi All,
I need to fetch the details of the charge elements for carrier for freight order.
I was able to traverse till node "TransportCharges" for the business object /scmtms/tor.
I am not to traverse further to the charge item present under the node 'TransportCharges'.
Which method I should use to fetch the details like 'Retrieve by association' or 'Retrieve' of service manager.
I was able to see the details in transaction /bobf/test_ui. I need to implement the code for the same functionality.
Please help me which parameters needs to be passed to the method to fetch the data, as I am getting dump when I trying to fetch the charge item details.
Regards,
Joseph MHi All,
Transport charge being a dependent object, to access the parameters need to use the class
/scmtms/cl_common_helper=>get_do_keys_4_rba( ).
This is done to convert the meta model keys to run time keys for processing.
Regards,
Joseph M -
Error when attempting to allocate a pick wave move order
Hi All,
We have a Sales order booked and pick released with Auto Allocate='No'.The lines on the sales order went to "Releases to warehouse" status and we need to do a move order. We Queried the move order and when checked found that the Allocated Quantity on the transact Move orders form is shown as Zero(normally when pick released with Auto Allocate='No' it should show the allocated quantity as null but i dont understand why its showing zero quantity??)
When attempting to allocate this pick wave move order by selecting the "Allocate" button , the following error occurs.:INV_PICK_RELEASE_PICK_CONFIRM_FAILED
Could any one help in transacting this move order please?
Thanks,
PVHi PV;
What is your EBS-DB and OS?
Please check below notes and see its helpful:
Get Error INV_PICK_RELEASE_PICK_CONFIRM_FAILED When Allocate Move Orders [ID 365082.1]
Bug 9720530: INV_PICK_RELEASE_PICK_CONFIRM_FAILED WHEN ALLOCATING A PICK WAVE MOVE ORDER
Bug 4436721: DATAFIX: UNABLE ALLOCATE MOVE ORDER, INV_PICK_RELEASE_PICK_CONFIRM_FAILED
Ps: If non of helps you please search word as "INV_PICK_RELEASE_PICK_CONFIRM_FAILED" in metalink.There are already 17 docs avaliable
Regard
Helios -
Auto batch determination at the time of picking by transfer order
Hello,
Our problem is, at the time of creation of transfer order with reference to delivery, system can not pick up the batches automatically as per the SLED. We have to manually enter the batches as per the SLED. Could you please guide me step by step procedure of automatic batch determination as per SLED at the time of creation of transfer order with reference to out bound delivery? (Please state step by step procedure of automatic batch determination as per the SLED at the time of picking with transfer order)
Thanks
MilindHi,
As for remaining shelf life please check OSS note 33396, 72771. Additonally this may also help:
http://www.renet-web.net/2008/09/05/sap-batch-determination-made-easy/comment-page-1/
As for sorting according to SLED date please read OSS note 769036.
Regards,
Csaba
Maybe you are looking for
-
How to turn off automatic photo sorting in camera roll?
Hi, I was wondering if there was a way to turn off the automatic sorting of pictures added to the camera roll? My problem is that I hardly take any pictures of my own using my ipad; instead I like to save funny pictures/memes, screen shots, fan art,
-
Standard individual purchase order -Delivery error
Dear All, I'm having issue on individual purchase order, Using TAB item category. Please understand my issue: Without purchase order +MIGO + MIRO + I am creating outbound delivery number but PGI, but is not allowing. Here my question: without creatin
-
MESSAGES - How to pause/stop check new mail?
Background: I handle mobile email by forwarding my multiple email accounts into a separate POP account to be accessed only by my Playbook. I only use it once or twice a week when I go out on the road. My problem is that I receive hundreds of emails d
-
Ora-01031 insufficient privileges oracle
Hi to all, I have installed oracle 10g and created new database. When i try to create the simple view its showing the following error. ora-01031 insufficient privileges oracle Note: if i have logged thru admin user, i could able to create the view (s
-
Handling multiple currencies in ALV in same colums
hi, I have a scenario, where I need to display amount values in a single column of ALV with different currencies. I am using RESUES_ALV_LIST_DISPLAY to display ALV and handling the currencies by using the below code. FIELDCAT-currency = currency_