IDoc SHP_OBDLV_CHANGE01 / BAPI_OUTB_DELIVERY_CHANGE

Advertisement

IDoc SHP_OBDLV_CHANGE01 / BAPI_OUTB_DELIVERY_CHANGE
I want to make a batch split on an outbound delivery.
I can't find documentation on IDoc SHP_OBDLV_CHANGE01 or BAPI_OUTB_DELIVERY_CHANGE on which fields to fill.
I have a delivery with 1 item - posnr 10. On this item I wan't to update the quantity and make a batch spilt.
When I try the quantity on the main position is updated but the batch spilt item is not beeing added and I get an errormessage : Text  ID  language  not found
Repaly
FYI
BAPI_OUTB_DELIVERY_CHANGE
You can BAPI to the extradition change functionality with this method both in the Enterprise-Resource-Planning-system (ERP-system) and in the decentralized Warehouse-management-system (World Cup) extradition after its distribution at the decentralized World Cup change. They can such a change both in the central ERP-system and in the decentralized World Cup carry out. The interface places adjust identically are certainly, that that for one planned extradition data also after a retroactive change in both systems. Change of head data: You delete can delete weight (gross weight and net weight) volume gate delivery appointment delivery priority route Incoterms Abladestelle delivery deliveries only then in the decentralized system and transmit this cancellation at the central SAP-ERP-system if the decentralized World
Cup is a strange system. Set in addition the mark DLV_DEL in the parameter HeaderControl. Change of position data: Quantity of weight (gross weight and net weight) volume decay date position delete change of partner data: Partners to a partner roll change or delete change address of a partner if you would like to change partner data, tests the system in the customizing of the respectively other system whether such a change is permitted. Change flow 1. they change retroactively an extradition in the central ERP-system or in the decentralized World Cup after it was distributed at the decentralized World Cup. 2. If it concerns in the decentralized World Cup a SAP-system, the system blocks the corresponding extradition in the partner system as soon as you call the change transaction. 3. If you secure the change
of the extradition, the system sends a synchronic change request at the connected partner system.
4. The partner system the change simulates based on the synchronic change request and accepts the change request or leans it off. 5. If the partner system rejects the change request, you cannot carry out the change. The system interrupts the preparation and brings a corresponding error message. 6. If the partner system accepts the change request, the system secures the extradition change in the system, in which you carried out the change, and an Asynchronous change request sends at the partner system. 7. Based On the Asynchronous change request, the partner system updates the extradition data. 8. The system the systemübergreifende barrier cancels for the changed extradition. Example if you would like to change for a distributed extradition the quantity, are the following statements for the transmission at the connected system necessary:
in the parameter head data of the extradition (HEADER_DATES) the delivery number (DELIV_NUMB) in the parameter position data of the extradition (ITEM_DATES) the delivery number (DELIV_NUMB) the delivery position (DELIV_ITEM) the delivery quantity in sale quantities unit (DLV_QTY) the Lieferistmenge in basis quantities unit (DLV_QTY_IMUNIT)
the sale quantities unit (SALES_UNIT) the ISO-code of the sale quantities unit (SALES_UNIT_ISO) the basis quantities unit (BASE_UOM) that Make, receives the system the material number, the work, the quantities statement as a floating decimal number, the volumes, the weights and its units out of the underlying extradition record.
References changes of the pack data are not synchronized in the central ERP-system.
In the retroactive change of a distributed delivery, the following prerequisites must be fulfilled:
All positions of the distribution relevant delivery have a joint decentralized administered warehouse number. They generate a distribution model for deliveries. You find generate further information in the introduction (IMG) under Logistics Execution -> integration decentralized World Cup -> headquarters settlement -> distribution -> distribution model. They have define determined in the customizing of the delivery under deliveries -> delivery type -> distribution mode whether the system should distribute the delivery either automatically after record creation or whether the distribution is supposed to be held back, so that you can activate the distribution over the delivery monitor. If you use a strange system as decentralized World Cup, must be guaranteed on sides of the decentralized World Cup over a barrier draft that you cannot process a delivery simultaneously in both systems. You find further information to the systemübergreifenden barrier in the SAP-library under basis -> client-server-technology -> Cross-system curl (CSL). If you use the Asynchronous interface for the actual transmission of the extradition change, (IDoc-type SHP_OBDLV_CHANGE), you note the correct IDoc-Strukturdefinition in the construction of the change-IDocs. Eighth you above all on that to exchange the segment sequence not.
Chargensplit in the decentralized World Cup if you change an appointment lower position of a distributed extradition in the decentralized World Cup, is this appointment lower position in the central ERP-system already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you change the quantity of an appointments head position of a distributed extradition in the decentralized World Cup, this appointments head position in the central ERP-system is already available. The fields HIERARITEM and USEHIERITM are empty. The system receives the appointment lower position into the field DELIV_ITEM. If you carry out in the decentralized World Cup a Chargensplit for a distributed extradition, only the appointments head position is at this time available in the central ERP-system. If you design for example two appointment lower positions, emerge for the transmission at the central ERP-system three
Position segment ItemData: The position segment for the appointments head position HIERARITEM is empty. The delivery quantity and the basis quantity are empty. Per appointment lower position, a position segment with the following fields emerges: DELIV_ITEM contains the number of the appointment lower position. HIERARITEM contains the number of the appointments head position. USEHIERITM indicates the use of the lower position with the value 1 as an appointment lower position. The quantities fields correspond to the quantities in the appointment lower positions. The central ERP-system carries out corresponding to the Chargensplit retroactively for the distributed extradition.
Parameter HEADER_DATES HEADER_CONTROL DELIVERY TECHN_CONTROL HEADER_PARTNER HEADER_PARTNER_HEADER
HEADER_DEADLINES ITEM_DATES ITEM_CONTROL ITEM_SERIAL_ITEM SUPPLIER_CONS_DATES EXTENSION1 EXTENSION2 RETURN
TOKENREFERENCE Exceptions function group V50I
Hope this’ll give you idea!!
Pl... award the points.
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"
Read More: The other 3 answers