have u seen this
<b>FU BAPI_OUTB_DELIVERY_CONFIRM_DEC</b>____________________________________________________
Short Text
BAPI for Outbound Delivery Verification from a Decentralized System
Functionality
You can use this method to report back outbound deliveries from a WM system to an enterprise resource planning (ERP) system. Essentially, the report consists of:
Header data from the delivery,
that must always be reported
Delivery items,
whereby you only need to report those items that have changed. Non-reported delivery item data is confirmed without changes.
Example
Two examples of how the BAPI is used are shown below:
1. Reporting back the delivery without (quantity) changes of the item data.
2. Reporting back the delivery with changes of the item data.
The following lists show a selection of example fields for the reported segment types.
1. The item data of the delivery is reported back unchanged.
DELIVERY - Document number of outbound delivery
Field DELIV_NUMB - Delivery number
HEADER_DATA - Header data of outbound delivery
Field DELIV_NUMB - Delivery number
HEADER_CONTROL - Header control data
Field DELIV_NUMB - Delivery number
Field POST_GI_FLG - Indicator: Post Automatic Goods Movement
2. The items of the delivery are reported back changed.
DELIVERY - Document number of outbound delivery
Field DELIV_NUMB - Delivery number
HEADER_DATA - Header data of outbound delivery
Field DELIV_NUMB - Delivery number
HEADER_CONTROL - Control data header level
Field DELIV_NUMB - Delivery number
Field POST_GI_FLG - Indicator: Post Automatic Goods Movement
ITEM_DATA - Item data
Field DELIV_NUMB - Delivery number
Field DELIV_ITEM - Delivery item
Field DLV_QTY - Delivery quantity in sales unit of measure
or alternatively
Field DLV_QTY_IMUNIT - Actual delivery quantity in stockkeeping unit
ITEM_CONTROL - Item control data
Field DELIV_NUMB - Delivery number
Field DELIV_ITEM - Delivery item
Field CHG_DELQTY - Change delivery quantity
Material number, plant, quantities in floating values, volumes, weights and their units are copied from the delivery, if not specified.
Error messages are recorded in BAPI return parameter RETURN with the following message types:
E (ERROR)
W (WARNING)
I (INFORMATION)
Further Information
If the BAPI is used as an external interface for an external system, the packing hierarchy should be described as usual by using external identification numbers for packaging materials (HDL_UNIT_EXID_INTO/HDL_UNIT_EXID). The fields can be found in the HANDLING_UNIT_ITEM segment. The handling unit must be copied into the HDL_UNIT_EXID_INTO field when the system reports back to packing.
If batch splits that were created in the ERP are reported back, the
hierarchy fields HIERARITEM and USEHIERITM must not contain information. If you created split items in the Warehouse Management System and reported back, these two hierarchy fields must contain information.
If a non-SAP system was used as a decentralized Warehouse Management System, the IDoc structure must be defined carefully when the return message is constructed. It is very important that the segment sequence must not be altered.
Parameters
HEADER_DATA
HEADER_CONTROL
DELIVERY
TECHN_CONTROL
HEADER_PARTNER
HEADER_PARTNER_ADDR
HEADER_DEADLINES
ITEM_DATA
ITEM_CONTROL
ITEM_SERIAL_NO
SUPPLIER_CONS_DATA
HANDLING_UNIT_HEADER
HANDLING_UNIT_ITEM
HANDLING_UNIT_SERNO
EXTENSION1
EXTENSION2
RETURN
TOKENREFERENCE
Exceptions
Function Group
V50I
Regards
Prabhu
Bluesky
