WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes not updating delivery..

Hi guys,
If I am not wrong is the API to update delivery details in WSH_DELIVERY_DETALS TABLE.
Here i am updating tracking_number for a given delivery_detail_id, but its not working.
Please help me if I am doing amy mistake.
create OR REPLACE procedure UPDATE_DETAILS_PROC_SAT is
l_changed_rec WSH_DELIVERY_DETAILS_PUB.ChangedAttributeTabType;
l_init_rec WSH_DELIVERY_DETAILS_PUB.ChangedAttributeRecType;
l_return_status VARCHAR2(1000);
l_msg_count NUMBER;
l_msg_data VARCHAR2(1000);
error exception;
begin
WSH_DELIVERY_DETAILS_PUB.Init_Changed_Attribute_Rec(p_init_rec => l_init_rec,
x_return_status => l_return_status);
l_init_rec.delivery_detail_id :=111482;
l_init_rec.tracking_number := 184854;
l_init_rec.shipped_quantity := 1;
l_changed_rec(1) :=l_init_rec;
WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes(p_api_version_number => 1.0,
p_init_msg_list => FND_API.G_TRUE,
p_commit => FND_API.G_TRUE,
x_return_status => l_return_status,
x_msg_count => l_msg_count,
x_msg_data => l_msg_data,
p_changed_attributes => l_changed_rec,
p_source_code => 'OE');
end;

What is the status of this delivery detail ID? Why are you passing the shipped quantity? Do you want to ship the delivery (hence associated details) and update the tracking number?
Remove the shipped_quantity and try updating first and then use deliveries actions to ship the delivery.
Thanks
Nagamohan

Similar Messages

Changing Handling unit weight does not update delivery header weight

Dears,
when we pack an item on a palett, system calculates tara-weight + material weight = gross weight and inserts this value to the likp-btgew. this is correct.
now it happens, that shipping departement uses a scale to get the 'real' weight of the handling unit. if the weigth differs, they change the loading weight of the HU. system calculates correct the new gross weight of the HU.
But when going back to delivery view, the likp-btgew is not updated. Do we miss a setting?
thanks a lot for your help!
Michael

wrong forum

Cannot update delivery attributes: the following field(s) are not updatable

Hi. I create in EBS simple Order
Now , my goal is to create a delivery , pick , change shipping quantity and ship confirm. Here is my code
DECLARE
p_sales_order NUMBER := 10014445;
p_line_number NUMBER := 1.1;
p_org_id NUMBER := 308;
l_shipped_quantity NUMBER := 5;
p_api_version_number NUMBER := 1.0;
init_msg_list VARCHAR2(200);
l_commit VARCHAR2(30);
x_msg_details VARCHAR2(3000);
x_msg_summary VARCHAR2(3000);
x_return_status VARCHAR2(3);
x_msg_count NUMBER;
x_msg_data VARCHAR2(3000);
p_validation_level NUMBER;
v_errbuf VARCHAR2(2000);
v_retcode VARCHAR2(20);
v_released_status wsh_delivery_details.released_status%TYPE;
v_inv_interfaced_flag wsh_delivery_details.inv_interfaced_flag%TYPE;
v_oe_interfaced_flag wsh_delivery_details.oe_interfaced_flag%TYPE;
v_source_code wsh_delivery_details.source_code%TYPE;
v_pending_interface_flag wsh_trip_stops.pending_interface_flag%TYPE;
l_changed_attributes wsh_delivery_details_pub.changedattributetabtype;
l_source_code VARCHAR2(30) := 'OE';
-- Parameters for WSH_DELIVERIES_PUB
p_delivery_name VARCHAR2(30);
p_action_code VARCHAR2(15);
p_asg_trip_id NUMBER;
p_asg_trip_name VARCHAR2(30);
p_asg_pickup_stop_id NUMBER;
p_asg_pickup_loc_id NUMBER;
p_asg_pickup_loc_code VARCHAR2(30);
p_asg_pickup_arr_date DATE;
p_asg_pickup_dep_date DATE;
p_asg_dropoff_stop_id NUMBER;
p_asg_dropoff_loc_id NUMBER;
p_asg_dropoff_loc_code VARCHAR2(30);
p_asg_dropoff_arr_date DATE;
p_asg_dropoff_dep_date DATE;
p_sc_action_flag VARCHAR2(10);
p_sc_intransit_flag VARCHAR2(10);
p_sc_close_trip_flag VARCHAR2(10);
p_sc_create_bol_flag VARCHAR2(10);
p_sc_stage_del_flag VARCHAR2(10);
p_sc_trip_ship_method VARCHAR2(30);
p_sc_actual_dep_date VARCHAR2(30);
p_sc_report_set_id NUMBER;
p_sc_report_set_name VARCHAR2(60);
p_sc_defer_interface_flag VARCHAR2(60);
p_sc_send_945_flag VARCHAR2(60);
p_sc_rule_id NUMBER;
p_sc_rule_name VARCHAR2(60);
p_wv_override_flag VARCHAR2(10);
p_asg_pickup_stop_seq NUMBER;
p_asg_dropoff_stop_seq NUMBER;
x_trip_id VARCHAR2(30);
x_trip_name VARCHAR2(30);
fail_api EXCEPTION;
x_debug_file VARCHAR2(100);
l_ship_method_code VARCHAR2(100);
l_user_id NUMBER;
l_resp_id NUMBER;
l_appl_id NUMBER;
CURSOR c_ord_details IS
SELECT DISTINCT det.source_header_number sales_order,
det.org_id,
det.source_line_number,
det.source_header_id,
det.source_line_id,
det.source_header_type_name,
det.inventory_item_id,
det.requested_quantity,
det.delivery_detail_id,
(SELECT concatenated_segments
FROM mtl_system_items_kfv
WHERE inventory_item_id = det.inventory_item_id
AND organization_id = det.organization_id) ordered_item,
det.organization_id,
det.src_requested_quantity,
det.shipped_quantity,
del.delivery_id,
del.status_code delivery_status_code,
det.released_status pick_release_status,
det.oe_interfaced_flag,
det.inv_interfaced_flag
FROM wsh_delivery_details det,
wsh_delivery_assignments asn,
wsh_new_deliveries del
WHERE 1 = 1
AND det.delivery_detail_id = asn.delivery_detail_id
AND asn.delivery_id = del.delivery_id(+)
AND det.source_header_number = 1199656
AND det.source_line_number = '1.1'
AND det.org_id = 10102
AND shipped_quantity IS NULL
AND NVL(del.status_code, 'OP') <> 'CL'
and det.delivery_detail_id =21439836
/* AND det.released_status = 'Y'*/;
BEGIN
-- Initializing the Applications
SELECT user_id INTO l_user_id FROM fnd_user WHERE user_name = 'MSHAPIRA';
SELECT responsibility_id, application_id
INTO l_resp_id, l_appl_id
FROM fnd_responsibility_vl
WHERE responsibility_name = 'OM Super User - UDS UK';
fnd_global.apps_initialize(l_user_id, l_resp_id, l_appl_id);
FOR i IN c_ord_details LOOP
DBMS_OUTPUT.put_line('Initializing the Application for Shipping Transactions');
-- Mandatory initialization for R12
mo_global.set_policy_context('S', i.org_id);
mo_global.init;
-- Ship Confirming
p_delivery_name := TO_CHAR(i.delivery_id);
DBMS_OUTPUT.put_line('Before Shipping, Calling WSH_DELIVERY_DETAILS_PUB API to Update Shipping Attributes');
DBMS_OUTPUT.put_line('=============================================');
l_changed_attributes(1).delivery_detail_id := i.delivery_detail_id;
l_changed_attributes(1).shipped_quantity := 5;
wsh_delivery_details_pub.update_shipping_attributes(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
p_commit => l_commit,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_changed_attributes => l_changed_attributes,
p_source_code => l_source_code);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
RAISE fail_api;
DBMS_OUTPUT.put_line('Failed to Update the Shipping Attributes');
ELSE
DBMS_OUTPUT.put_line('Successfully Updated the Shipping Attributes');
END IF;
BEGIN
SELECT shipping_method_code
INTO l_ship_method_code
FROM oe_order_headers_all
WHERE order_number = i.sales_order
AND org_id = i.org_id;
EXCEPTION
WHEN OTHERS THEN
l_ship_method_code := NULL;
END;
p_action_code := 'CONFIRM'; -- The action code for ship confirm
p_sc_action_flag := 'S'; -- Ship entered quantity.
p_sc_intransit_flag := 'Y';
--In transit flag is set to 'Y' closes the pickup stop and sets the delivery in transit.
p_sc_close_trip_flag := 'Y'; -- Close the trip after ship confirm
p_sc_trip_ship_method := l_ship_method_code; -- The ship method code
p_sc_defer_interface_flag := 'Y';
p_sc_stage_del_flag := 'Y';
p_sc_create_bol_flag := 'N';
p_wv_override_flag := 'N';
-- API Call for Ship Confirmation
DBMS_OUTPUT.put_line('Calling WSH_DELIVERIES_PUB to Perform Ship Confirmation');
DBMS_OUTPUT.put_line('=============================================');
wsh_deliveries_pub.delivery_action(p_api_version_number => 1.0,
p_init_msg_list => init_msg_list,
x_return_status => x_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_action_code => p_action_code,
p_delivery_id => i.delivery_id,
p_delivery_name => p_delivery_name,
p_asg_trip_id => p_asg_trip_id,
p_asg_trip_name => p_asg_trip_name,
p_asg_pickup_stop_id => p_asg_pickup_stop_id,
p_asg_pickup_loc_id => p_asg_pickup_loc_id,
p_asg_pickup_stop_seq => p_asg_pickup_stop_seq,
p_asg_pickup_loc_code => p_asg_pickup_loc_code,
p_asg_pickup_arr_date => p_asg_pickup_arr_date,
p_asg_pickup_dep_date => p_asg_pickup_dep_date,
p_asg_dropoff_stop_id => p_asg_dropoff_stop_id,
p_asg_dropoff_loc_id => p_asg_dropoff_loc_id,
p_asg_dropoff_stop_seq => p_asg_dropoff_stop_seq,
p_asg_dropoff_loc_code => p_asg_dropoff_loc_code,
p_asg_dropoff_arr_date => p_asg_dropoff_arr_date,
p_asg_dropoff_dep_date => p_asg_dropoff_dep_date,
p_sc_action_flag => p_sc_action_flag,
p_sc_intransit_flag => p_sc_intransit_flag,
p_sc_close_trip_flag => p_sc_close_trip_flag,
p_sc_create_bol_flag => p_sc_create_bol_flag,
p_sc_stage_del_flag => p_sc_stage_del_flag,
p_sc_trip_ship_method => p_sc_trip_ship_method,
p_sc_actual_dep_date => p_sc_actual_dep_date,
p_sc_report_set_id => p_sc_report_set_id,
p_sc_report_set_name => p_sc_report_set_name,
p_sc_defer_interface_flag => p_sc_defer_interface_flag,
p_sc_send_945_flag => p_sc_send_945_flag,
p_sc_rule_id => p_sc_rule_id,
p_sc_rule_name => p_sc_rule_name,
p_wv_override_flag => p_wv_override_flag,
x_trip_id => x_trip_id,
x_trip_name => x_trip_name);
IF (x_return_status <> wsh_util_core.g_ret_sts_success) THEN
DBMS_OUTPUT.put_line('Ship confirm has not been Completed For SO => ');
ROLLBACK;
RAISE fail_api;
ELSE
DBMS_OUTPUT.put_line('Ship confirm Successfully Completed For SO => ');
COMMIT;
DBMS_OUTPUT.put_line('Checking the Delivery Status after delivery action API Call');
DBMS_OUTPUT.put_line('==========================================');
SELECT wdd.source_code,
wdd.released_status,
wdd.inv_interfaced_flag,
wdd.oe_interfaced_flag,
wts.pending_interface_flag
INTO v_source_code,
v_released_status,
v_inv_interfaced_flag,
v_oe_interfaced_flag,
v_pending_interface_flag
FROM wsh_trips wtr,
wsh_trip_stops wts,
wsh_delivery_legs wlg,
wsh_new_deliveries wnd,
wsh_delivery_assignments wda,
wsh_delivery_details wdd
WHERE wtr.trip_id = wts.trip_id
AND wts.stop_id = wlg.pick_up_stop_id
AND wts.pending_interface_flag = 'Y'
AND wdd.inv_interfaced_flag <> 'Y'
AND wlg.delivery_id = wnd.delivery_id
AND wnd.delivery_id = wda.delivery_id
AND wda.delivery_detail_id = wdd.delivery_detail_id
AND wnd.delivery_id = p_delivery_name
AND wdd.source_line_id = i.source_line_id;
IF (v_source_code = 'OE' AND v_released_status = 'C' AND
v_inv_interfaced_flag <> 'Y' AND v_oe_interfaced_flag <> 'Y' AND
v_pending_interface_flag = 'Y') THEN
DBMS_OUTPUT.put_line('The Delivery has been Shipped & the Next Step is - Run Interface');
DBMS_OUTPUT.put_line('===========================================');
-- API Call for Submitting Interface Trip Stop
wsh_ship_confirm_actions.interface_all_wrp(errbuf => v_errbuf,
retcode => v_retcode,
p_mode => 'ALL',
p_stop_id => NULL,
p_delivery_id => p_delivery_name,
p_log_level => 0,
p_batch_id => NULL,
p_trip_type => NULL,
p_organization_id => i.organization_id,
p_num_requests => 1,
p_stops_per_batch => 1);
ELSE
DBMS_OUTPUT.put_line('The Delivery has not Shipped Properly');
END IF;
END IF;
END LOOP;
EXCEPTION
WHEN fail_api THEN
DBMS_OUTPUT.put_line('==============');
DBMS_OUTPUT.put_line('Error Details If Any');
DBMS_OUTPUT.put_line('==============');
wsh_util_core.get_messages(p_init_msg_list => 'Y',
x_summary => x_msg_summary,
x_details => x_msg_details,
x_count => x_msg_count);
IF x_msg_count > 1 THEN
x_msg_data := x_msg_summary ||' '||x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
ELSE
x_msg_data := x_msg_summary||' '|| x_msg_details;
DBMS_OUTPUT.put_line(x_msg_data);
END IF;
END;
But at the stage of updating delivery attributes I get the following error message
Warning: For Delivery Detail 21439836, the following field(s) are not updatable: SHIPPED_QUANTITY.
Why?

Hi Paul
Looks like the authorisation is failing due to a bad registration for some reason.
Would you be kind enough to clear out the registration to ensure we are dealing with a fresh start and no information is being used which may have become corrupt. You may do this by following this procedure;
Remove existing reg details
# usr/lib/cc-ccr/bin/eraseCCRRepository
List /tmp/RegistrationProfile.properties file
# cat /tmp/RegistrationProfile.properties
Attempt re-registration
# sconadm register -a -r /tmp/RegistrationProfile.properties
Send us the full output of the commands above if you would please.

PGI status at delivery header level has not updated

Dear Friends,
We had created deliver, picking was completed and PGI was completed successfully. However when we try to create Billing, an error occurs stating that PGI is not completed.
Further when we check the delivery, the Goods Issue status at item level is completed but at the Header level the GM is B which is partially completed. In the Document flow we can see the PGI Status is completed.
I think there might be some table which was not update. Is there any way to update the status in the delivery?
Further we tried to reverse the PGI through VL09, but system is not able to find the delivery ..this might be because the system might be checking in some table where the statues has not updated.
Please suggest me how should I complete this.

HI,
Go to transaction "SE16N" and enter table "VBUK" and give the delivery number in the field sales document number. Now you type "&SAP_EDIT" in the transaction bar and execute. Here you can change the status(Total goods movement). And see If you can actually bill the document. Kindly please let me know If you need any more information on this.
Regards,
Ram Pedarla

Value of planned delivery time in days not updating

Hello Experts,
i have created a material using BAPI_MATERIAL_SAVEDATA.
IN Mrp2 VIEW
PLANNED DELIVERY TIME IN DAys is not updating
i have passed
la_plantdata-plnd_delry = P_PLND_DELRY.
la_plantdatax-plnd_delry = 'x'.
i have commited the work too but the field is not updated
Please help.
Thanks & Regards,
Naresh

Hi,
This question is not related to APO, i would suggest you to post the thread in ABAP forum.
However can you check
can you check whether la_plantdatax-plnd_delry field is 3 charcter or one character field.
Generally it will be like below.
la_plantdata-plnd_delry = 100
la_plantdatax-plnd_delry = 'X
Regards,
Srini

Inbound Delivery Idoc not update PIC and PGI with split batch.

Dear Experts,
Delivery outbound with split batch send to third party Warehouse to PIC and PGI from SAP, then receive the delivery inbound IDOC to update the PIC and PGI in SAP from third party. Basic Idoc DELIVERY03 it's works fine with out split batch, with split batch it's not updating PIC and PGI at the same time no error. Please advice on this
E1EDL24-HIPOS = "HIGHER LEVEL ITEM NUMEBR"
E1EDL24-HIEVW = "VALUE 1"
E1EDL19-QALF = "BAS"
Thanks and Regards,
Thiru.

Hi,
You also have to create a segment with following data as well (for batches).
E1EDL19-QUALF = "QUA".
Cheers,

Billing status in delivery not updated for free-of-charge flow

Hi,
I have a free-of-charge flow: sales order-delivery-invoice. The invoice has the net value 0 and do not goes in accounting. The problem is that the billing status in delivery is still "not invoiced" and because of this i can make more invoices for the same delivery/qty. Why the status in not updated? The item categ is relevant for billing (A).
Thanks.

You can refer SAP Note 33258 - Processing free-of-charge items.
Where they talk about Item cat setting, use of Cond Type R100.
Regards
JP

PO item change is not updated after Delivery completion

Dear All,
PO item change is not updated in the PO at the completion of the delivery.for a particular line item. In our QA system, its updated but client is facing an issue with the production system. Pls check the attached screen which I got from QA. There is no such log in the production system. Kindly help me to have a solution for this.
Regards
Sujith

Hi Dev,
After we post the GR for a PO line item, PO history is updated (line) and at the same time that particular change log is available under PO line item. But in production system, said log is not updated after GR is completed fully.
Rgs
Sujith

Delivery block not updated in sales order after released VKM3

Hi all,
I am facing below error
after released credit block throuh VKM3 also i am unable to delivery becasue it is not updated still block exist in sales order level.
i made all nacessary settings for that and also i tried through VKM1 but this tcode through error no poosible entries.
Thanks in advance
Srinivasa

hi,
check the following steps of assignment you did right or not
1)first check in t- code FD32 U assigned authorization person & each credit limit U shud assign
an authorization person along with credit limit
2) check - conditon records with KRML output is there or not
please read standard SAP config help as a check point doc.[Credit mgmt|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBFCM/SDBFCM.pdf]
Let me know if it is soling your issue...
rgards,
rajeev

Status is not updated from delivery to sales order item.

Dear Folks,
One user created sales order with 10 line items and he created delivery and later he deleted line item 30 in that delivery document and with remaining 9 line item he done the PGI & Billing.Here what is the problem is the deleted line item in sales order status showing as completed and delivered quatity showing as 10.Status is not updated from delivery to sales order item.Please let me know how to resolve this?
Thanks & Regards,
murali.

Dear Murali,
Please go to VTLA transaction then select your delivery and order types after that go in to the details of the item level settings here you check field called Update document flow under Control data tab.
I hope it will help you,
Regards,
Murali.

Delivery adress is not updated in SC

Hi all,
We are going from SRM 5 to SRM 7 and we have BADI BBP_DOC_CHANGE_BADI~BBP_SC_CHANGE implemented in order to change some fields from Delivery adress tab (IT_PARTNER). In SRM 5 it was working fine but now in SRM 7 these fields are not updated with the new values.
All exporting tables are informed and I checked by debug that all fields are well informed in the internal table.
I have found some threads with the same problem in SMR 7 asking the same but there are no answers. Also I checked for OSS notes but I didn't find anything.
Do you have any idea?
Thx,
Manel

We have assigned an adress to the root of HR org structure and then we clear ADDR_NO from IT_PARTNER. New vales from IT_PARTNER are well updated

Delivery document is not updated " update was terminated"

Hi all,
I have a problem with creating delivery order using vl01n. When i'm creating delivery it is successfully saved and system giving delivery number also but problem is when i'm opend my delivery using vlo2 sytem not displaying my delivery. And one more thing while i saving the delivery document using vl01n after saving document i'm receiving message delivery is not updated; Express document " update was terminated" received from author DDIC. What is mean that i unable to solve this problem. Please solve my problem as eraly as possible.
Thanks & regards
kesav

vi 110:delivery type FA
For the above error message, if the system could not determine the partner function Sold To Party, system will throw this error.
So please check your partner function assignment.
thanks
G. Lakshmipathi

Outbound delivery document flow is not updated after LT0G

Hello Gurus,
after executing LT0G Returd to stock from delivery, a document flow of outbound delivery is not updated. Still an OvrllPickStatus remains = C Fully picked and OverallWMStatus = C WM trsf ord confirmd. This though the goods result to be returned correctly from 916 into stock.. What can be the reason for this malfunctioning?
Jari

Many thank for your feedback. The transaction LT0G is executed succefully and a destination storage bin results a correct quantity. Anyway I checked SM13 and a log is empty.
The notes you mentioned seemed very promising, but unfortunately they are not relevant as a release in where I am working is SAP ECC 6.0 SAPKH60013.
I am still trying to find some possible other notes but without a success so far.
Jari

Picked Quantity is not updated After delivery in Vl03n

After delivey in Order (VA03), the picked quantity is not updated Properly(VL03n). It is coming as Zero.
Is it any configurations needed or writng any code.
For that I put Break point in FMs like SD_DELIVERY_UPDATE_PICKING in program RVADEK01.
But it is not stopping the Program.
Please give any possible solution.

Hi Vinod,
Thank u For ur Answer.
Just my Fuctional Consultant given Procedure.
How to test the picking list. The problem is after Deliver the Order quantity in VA03 and after saving, this will creates One Out Bound delivery.
Now We r checking VL03n. Now it is updating the Picked Quantity Correctly, For that We r using the Standard Print program: RVADEK01, Form: RVPICSKSIN.
Output Type: EK00, Application: V4.
Here My problem is We copied the Form and print Program and modified according to our requirement and they configured in Nace with our own Output type. We haven't chenged the updated Functionality and Not even Standard program. We wrote some include program for getting new values in scripts.
Now the picked quantity is not updated after picking in VL03n.

Delivery not updated

Hi all,
I have a problem with creating delivery order using vl01n. When i'm creating delivery it is successfully saved and system giving delivery number also but problem is when i'm opend my delivery using vlo2 sytem not displaying my delivery order (error:delivery doesn't exist) And one more thing while i saving the delivery document using vl01n after saving document i'm receiving message delivery is not updated; *Express document " update was terminated" received from author DDIC. and i have checked with sm13 there system telling that error in function module rv_delivery_save. Please give me solution for this problem as early as possible.
Thanks & regards
kesav

Hi,
In SM13 it will show you the dump details. Check the same.
Put a breakpoint at the place where the update is terminating.
Start the delivery creation process and before saving enter into debug mode and turn on Update debugging and System debugging. It should stop at your breakpoint. Then try to check why it is failing.
As Martin suggested; the problm should be due to some iincorrect coding in a user exit.
Regards,
Ankur Parab

WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes not updating delivery..

Similar Messages

Maybe you are looking for