Repeat transportorder confirmation - update delivery notes

Hello everyone,
Transport orders (WM) - based on delivery's - have been created and were confirmed. Unfortunately the corresponding update of delivery notes failed. (e.g. VBFA, LIPS not updeated).
We are searching desperately for a solution to redo the confirmation (as everyone knows: delivery notes can not be invoiced until goods issue). We have batch management in place so it is possible that there are a couple batch splits. (means that manually adjusting tables is a no no - besides all other good reasons).
If anybody out there has any idea (or programm) to do this, we would be very greatful.
Regards
Thomas
EDIT: If this is the wrong thread, please let me know!
Message was edited by:
Thomas Hager

Hello Thomas,
Are you using one step or Two step confirmation?
Please check out this OSS note.
Note 574887 - Tables LIPS and VBUP/VBFA not in a consistent state
Note 755506 - Incorrect updation of Picking & WM status for Std. Materials
Note 664316 - Tips for the delayed delivery update for TO confirmation
Hope this helps.
Regards,
Arif Mansuri
Reward if answer is helpful.

Similar Messages

How to update delivery note comment while creating return order

Hi all.
I need to update the delivery note comment in return sales order.Could you pls let me know is there any FM to achieve this pls?
Thanks in advance.
Thanks & Regards,
sami.

Hi,
Try using SD_SALESDOCUMENT_CHANGE function module. Give the text in SALES_TEXT parameter.
KR Jaideep,

BAPI to update delivery note

hi all,
Is there any BAPI available with which we can update a delivery note and also if possible do PGI using it.
In case there are separate BAPI's for both the processes that will do for me.
Kindly help
Regards
Varun

Hi Varun,
You can use <b>WS_DELIVERY_UPDATE</b> or <b>WS_DELIVERY_UPDATE_2</b> ..
Following sample code works for Automatic PGI of an existing delivery. Use this as a basis and code for your requirement.
DATA: ls_vbkok LIKE vbkok,
        lv_error_pgi TYPE xfeld,
        lt_prot LIKE prott OCCURS 0 WITH HEADER LINE,
        lwa_prot like prott.
ls_vbkok-vbeln_vl = <your Delivery Note number>.
ls_vbkok-wabuc = c_true.
CALL FUNCTION 'WS_DELIVERY_UPDATE'
    EXPORTING
      vbkok_wa                           = ls_vbkok
      synchron                           = c_true
*         NO_MESSAGES_UPDATE                 = ' '
      commit                             = c_true
      delivery                           = <your Delivery Note number>
*         UPDATE_PICKING                     = ' '
*         NICHT_SPERREN                      = ' '
*         IF_CONFIRM_CENTRAL                 = ' '
*         IF_WMPP                            = ' '
*         IF_GET_DELIVERY_BUFFERED           = ' '
*         IF_NO_GENERIC_SYSTEM_SERVICE       = ' '
*         IF_DATABASE_UPDATE                 = '1'
*         IF_NO_INIT                         = ' '
*         IF_NO_READ                         = ' '
*         IF_ERROR_MESSAGES_SEND_0           = 'X'
*         IF_NO_BUFFER_REFRESH               = ' '
*         IF_NO_MES_UPD_PACK                 = ' '
*       IMPORTING
*         EF_ERROR_ANY_0                     =
*         EF_ERROR_IN_ITEM_DELETION_0        =
*         EF_ERROR_IN_POD_UPDATE_0           =
*         EF_ERROR_IN_INTERFACE_0            =
     ef_error_in_goods_issue_0          = lv_error_pgi
*         EF_ERROR_IN_FINAL_CHECK_0          =
   TABLES
*         VBPOK_TAB                          =
     prot                               = lt_prot[]
*         VERKO_TAB                          =
*         VERPO_TAB                          =
*         VBSUPCON_TAB                       =
*         IT_VERPO_SERNR                     =
*         IT_PACKING                         =
*         IT_PACKING_SERNR                   =
*         IT_REPACK                          =
*         IT_HANDLING_UNITS                  =
*         ET_CREATED_HUS                     =
IF NOT lt_prot[] IS INITIAL.
    READ TABLE lt_prot WITH KEY msgty = 'E'.
    IF sy-subrc EQ 0.
****Errors Exist
***      Goods Issue Failed
    ENDIF.
ELSE.
***    Goods Issue posted sucessfully
ENDIF.
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

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.

Overdelivery tolerance- confirm quantity (allocation) not getting updated

Hi All
    I have a strange problem......could this be a gap with the SAP program
I am using over and under delivery tolerance (say 10%) in the customer master - sales - shipping tab. Now i create a order with
Order qty          1100
confirmed qty   1100
delivery qty      1200      (since we have maintained 10 % over delivery tolerance)
Now i want to update the order to 1200 for two reasons
1) to keep the order in sync with delivery
2) to update the allocations (this is because we have Allocation activated and not ATP at schedule line level)
So when i go into the order and update the line to 1200 the following happens
Order qty             1200
confirmed qty      1100   (not updated)
delivery qty         1200
So my confirm qty is not getting updated to 1200 and hence my allocation tables are not getting updated. The same is getting updated when we have ATP at schedule line level. Could this be a gap with SAP that i dosent update allocations in this scenario.
The reason it dosent confirm is that it assumes that the delivery is completed and since we have tolerance maintained it assumed to be a good scenario.
Please help.
Vikas
Edited by: Vikas BhumiReddy on Oct 28, 2009 5:27 PM

I am also facing the same issue. Have you found out any solution regarding this.

Bapi to update delivery date in confirmation tab in purchase order me22n tc

Hi All,
I am writing a BDC to update the data in confirmation tab for puchase orders for enjoy transaction.
Please let me know how to updated delivery date in confirmation tab in purchase order(ME22N) using a bapi.
I tried using BAPI_PO_CHANGE but found no parameter related to confirmations tab. this BAPI has every thing to update like header data, item data, scheduling data..... except confirmation.
So please let me know how to update the data in confirmation.
We need to use only enjoy transaction ME22N not ME22 in BDC thats why we are looking for a BAPI.
Regards,
Venkat

Hi
Check the table parameter POCONFIRMATION in BAPI_PO_CHANGE
U can see the field DELIV_DATE in the structure BAPIEKES.
DELIVERY_DATE in the structure BAPIMEPOSCHEDULE as well.
Regards,
Dwaraka.S
Edited by: Dwarakanath Sankarayogi on Feb 5, 2009 7:57 AM

MIGO - GR Against Purchase Order - Delivery Note # not to Repeat !!

Hi all,
Here is a interesting requirement from the business user!!
Scenario: Currently they are making Goods receipt against Purchase order in Transaction MIGO. Delivery Note # (LFSNR) is entered during Posting.
Problem: Recently they did MIGO for Purchase order, by mistake they did Goods receipt twice for same vendor delivery note # !
Question: Can you please suggest a way to validate the Delivery note # field of MIGO, Such that it is unique. If the number is Repeated for the Same Vendor, system should throw a error message, stating that Delivery note # already exists. So that it avoids posting of GR for same delivery note even by mistake !!
I thought of validating this entry in MSEG Table, but problem is it will delay the posting of document !!
Is there a standard user exit or setting to validate this field during posting!!
Thanks in advance.
Regards,
Thiyagu

Joven,
If you see transaction VL31, Creation of Inbound Delivery, SAP did the validation for EXTERNAL ID in the Input screen of the Transaction. If we try to repeat the External id #, system throws error message as below.
"The external ID of the delivery note is not unique (see inb. dely
0180267952)" Message no. BORGR547
When we make Goods receipt against Inbound Delivery instead Purchase order. We may over come the problem some how. Reason is that during Inbound Delivery creation itself External ID is validated. During GR against Inbound Delivery this External Id gets copied as Delivery Note #, so this is the alternative i thought !!
Thanks,
Thiyagu

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

"Material is not the same for confirmation and delivery"

Hello
If this is not the right forum, my apologies. Direct me to the correct one if it is not ....
Have been doing automated test development (HP's QTP) against SAP systems for over a year. I am not an application expert - very much a newbie when it comes to application knowledge but trying to gain some. I have "googled" the phase "Material is not the same for confirmation and delivery" and have not been able to find any references. What does this mean?
I see this message for an iDoc using WE02. Have looked and looked but don't really know what I'm looking for.
Clues?
Thanks,
DW

DW,
I have never seen that exact message, but I have seen similar ones. Generically, the message probably means that you are attempting to perform a transaction against a document (perhaps a Purchase order?) and the Material number (Part Number) contained in the transaction is not the same as the Material number in the originating document in SAP.
An example might be you have previously created a confirmation against a Purchase order, which now exists in SAP. This Confirmation is for a specific Purchase order, item, and material. Now, when you attempt to create an inbound delivery for the Confirmation, the material number contained in the new IDOC is different from the material number that was contained in the original Confirmation.
I don't know what IDOC Message type you are having the problem with, but generically you can do some troubleshooting. Find the SAP Material number in the IDOC (MATNR probably). Find the appropriate reference document number in the IDOC (confirmation number? Purchase order number? or...?), and then manually review the document in SAP to ensure that the Material numbers are the same.
If you are totally lost, you should really consult with an SAP App expert. I am guessing that this is part of the Materials Management module, so you would be asking for an MM expert.
Or, you can send more details, and we can try to help.
What is the IDOC message type?
What is the Message number of the error message? Functionally, what is this IDOC trying to do, from a business perspective?
Rgds,
DB49

Printing delivery notes upon picking confirmation

We wish to only print delivery notes once picking is confirmed and goods ready to go. We can achieve this in VL02n via amendment to routine 35 in V/27 however generation of output does not appear to apply when picking is confirmed via transaction VL06C rather than in the delivery itself. Any suggestions as to how to generate reliable printing of delivery notes upon confirmation that picking is complete?
Thanks
Birna Rowley

Hi,
In the definition of output scheme, set a new conditional subroutine (define it with VOFM) as 035 (for instance 935), as this coding:
form kobev_935.
* Workarea KOMKBV2 is available
if komkbv2-kostk = 'C'.
sy-subrc = 0.
else.
sy-subrc = 4.
endif.
endform.
form kobed_935.
endform.
Check before with debugging that KOMKBV2-KOSTK has the desired value. After, define the output with VV21 and option inmediatly.
I hope this helps you
Regards,
Eduardo

TS3694 My iPad2 has repeatedly refused to update to iOS7, whether connected to a PC or not. The error message indicates an unknown error has occurred, with error code 6. Does anyone have any idea what the problem might be and how to solve it? Many than

My iPad2 has repeatedly refused to update to iOS7, whether connected to a PC or not. The error message indicates an unknown error has occurred, with error code 6. Does anyone have any idea what the problem might be and how to solve it? Many thanks.

Hi
I followed this guy's instructions and it worked:
http://evsiphone.blogspot.com/2009/05/iphone-iphone-could-not-be-restored.html
I did disable the security (AVG and Zone Alarm) when I tried on my own PC. My wife's laptop which eventually got it working also uses AVG and Zone Alarm but on an XP O/S whereas my PC is Vista - maybe this is why.
Cheers for you help.
Andy
Message was edited by: bigbadandy

Update ship note under Confirmation tab in PO

Hi Expert,
I need help. i have a PO with 3 items. 2 items, able to update the ship note under Confirmation tab in item area. but the other one, when i click on confirmation tab, there's no table to update ship note and i see that indicator 'Acknowl reqd' not flag.Is it because of that? What should i do now?
Thanks

Dear Crystal
You will have to input the confirmation control field value. Only then you could enter the details for the shipping notification.
Confirmation Control Key, Determines which confirmation categories are expected for a PO item (e.g. order acknowledgment, shipping notification).
with kind regards
Sundar

Update qty in delivery note through bapi for migo

hi im using bapi for migo upload
my requiremnt is to update QTY IN DELIVERY NOTE in migo.
i got the folowing error if i dont pass the quantity.
qty and/0r delivery indicator or final issue indicator missing
if i pass the quantity field then it is changing quantity in unity of entity and qty in SKU i dnt want to change this field
here is my code,
gmcode-gm_code = '01'.
    ls_GOODSMVT_HEADER-pstng_date = tdate . "sy-datum.
    ls_GOODSMVT_HEADER-doc_date   = sy-datum.
    ls_GOODSMVT_HEADER-pr_uname   = sy-uname.
loop at itab.
ls_GOODSMVT_HEADER-REF_DOC_NO = itab-LFSNR.
it_goodsmvt-move_type = itab-BWART.
it_goodsmvt-po_number = itab-EBELN.
it_goodsmvt-PO_ITEM = '10'.
it_goodsmvt-STGE_LOC = itab-LGORT.
it_goodsmvt-QUANTITY = itab-LSMNG.
it_goodsmvt-BASE_UOM = 'KG'.
it_goodsmvt-material = 'RC1092'.
it_goodsmvt-entry_qnt = itab-LSMNG.
it_goodsmvt-ENTRY_UOM = 'KG'.
it_goodsmvt-mvt_ind = 'B'.
it_goodsmvt-plant = 'G001'.
it_goodsmvt-NO_MORE_GR = 'X'.
append it_goodsmvt.
clear it_goodsmvt.
CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
EXPORTING
    goodsmvt_header               = ls_GOODSMVT_HEADER
    goodsmvt_code                 = gmcode-gm_code
TESTRUN                       = ' '
GOODSMVT_REF_EWM              =
IMPORTING
GOODSMVT_HEADRET              =
   MATERIALDOCUMENT              = lf_MATERIALDOCUMENT
   MATDOCUMENTYEAR               = lf_MATERIALDOCYEAR
tables
    goodsmvt_item                 = it_goodsmvt
GOODSMVT_SERIALNUMBER         =
    return                        = return
GOODSMVT_SERV_PART_DATA       =
EXTENSIONIN                   =
if return-type ca 'EA'.
      rollback work.
      message id '26' type 'I' number '000'
      with return-message.
    else.
      call function 'BAPI_TRANSACTION_COMMIT'
EXPORTING
WAIT          =
IMPORTING
RETURN        =
      wait up to 5 seconds.
    endif.
select * fROM mseg
      INTO CORRESPONDING FIELDS OF TABLE IT_MSEG
                         where mblnr = lf_MATERIALDOCUMENT and
                                   MJAHR = lf_MATERIALDOCYEAR.
LOOP AT IT_MSEG INTO WA_MSEG.
    IF WA_MSEG-LSMNG IS INITIAL.
      wa_mseg-lsmng = ITab-LSMNG.
      UPDATE MSEG from wa_mseg.
      commit work.
      wait up to 5 seconds.
    ENDIF.
ENDLOOP.
ENDLOOP.

It is been done by implementing one implicit enhancement in FM: MAP2I_B2017_GM_ITEM_TO_IMSEG
I have added the below functionality at the end of the function module.
Just i have maped the ERFMG i.e ent_qnt(Received quanity) with LSMNG i.e qty.in del note
All best for others.
$$-Start: (1)----
$$
ENHANCEMENT 1 Z_EV_IMP_GOODSMOVEMENT.    "active version
Populate the delivery note quantity and UoM
IF IMSEG-ERFMG IS NOT INITIAL.
MOVE IMSEG-ERFMG TO IMSEG-LSMNG.
MOVE IMSEG-ERFME TO IMSEG-LSMEH.
ENDIF.
ENDENHANCEMENT.
Thanks,
Mahesh.Gattu
Edited by: Maheshkumar gattu on Dec 3, 2010 4:35 PM

How to cancel a delivery note when all plant transferts have been confirmed?

Hello,
I need to cancel a delivery note. The good issue has been cancelled but the delivery note remains blocked because the plant transferts have been confirmed. I tryed to cancel them via LT15 transaction but it does not work. There are splitted batches for each plant transfert.
Does anyone have an idea about how to cope with it?

Call apple...
Apple Phone Numbers
btabz

Detla Update Error, Last update is not repeatable. Please Help!

Hi,
I would greatly appreciate any help with this problem.
We have a daily delta update going in from R/3 to SEM Production (bw 3.1 bc 3.3). for business consolidation purposes.
R/3 --- 0FIGL_O07 (ODS) --- ZBW_BCS (Custom Cube).
The delta request failed and became red. Subsequently the following day the same thing happened. There are no error dumps.
The thing that gets me is normally our delta updates have about 200,000 records per update, the 2 that failed have 17 million each!
When I do to the first failed request and check the details section Under Transfer (IDOCS and TRFC) it says data package xxx sent but not arrived.
What is confusing is there is nothing to warrant a jump in no. or recs from 200k to 17mil.
When I try to do an immediate request of detla it says cannot do it as last delta update still running.
Please advise
Regards,
Dominic

Hi all,
Thanks for your advise.
This is exact steps I followed.
1.) There were 2 red requests in the ODS with the error message (given above).
2.) I tried to force the first one green which started a batch job that got cancelled.
3.) I informed Basis as per Dinesh's advice and extended tablespace.
4.) I re-activated the request.
Currently there is another batch job running at the moment.
What I would like to know is, is it unusual for a delta update to contain 600,000 records today and say the update does not run for over a month and then contain 17 mil records ?
I will come back on the completion of the job once done.
Regards,
Dominic

Repeat transportorder confirmation - update delivery notes

Similar Messages

Maybe you are looking for