Functionality
You can use this method to report back outbound deliveries from a WMsystem 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:
RESET N1
Reporting back the delivery without (quantity) changes in the items
Reporting back the delivery with changes in the item data.
The following lists show a selection of example fields for the reportedsegment types.
RESET N1
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
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, weightsand their units are copied from the delivery, if not specified.
Error messages are recorded in BAPI return parameter RETURN with thefollowing message types:


• E (ERROR)


• W (WARNING)


• I (INFORMATION)

Further information
This part of the text is similar to function module BAPI_INB_DELIVERY_
CONFIRM_DEC
If you use the BAPI as an external interface for an external system, youshould describe the packing hierarchy as usual, by using externalidentification numbers HDL_UNIT_EXID_INTO/HDL_UNIT_EXID of the packagingmaterials. The fields are contained in the HANDLING_UNIT_ITEM segment.You must copy the handling unit into the HDL_UNIT_EXID_INTO field whenreporting back to packing.
If you report back batch splits that were created in the ERP system, theyou cannot fill the hierarchy fields HIERARITEM and USEHIERITM.
If you created split items in the decentralized WM system and reportedback, you must fill these two hierarchy fields.
If you do not use an ERP system as a decentralized Warehouse ManagementSystem, the IDoc structure must be defined carefully when the returnmessage is constructed. In particular, you are not allowed to alter thesegment sequence.

Description
This segment contains the outbound delivery number.

Description
This structure contains the control data for reporting back the headerinformation.

Description
The structure contains control data for changes to the header data ofthe outbound delivery.
This structure contains enhancements for service parts management.

Description
In this structure, the general header data of the outbound delivery arepassed on.

Description
In this structure, you transfer outbound delivery header data.
This structure contains the enhancements for service parts management.

Description
Using this parameter, you can cause a termination in the receivingsystem by setting field DEBUG_FLG to 'X'. After the termination, youcan re-import the IDoc with the corresponding BREAK-POINTs in thereceiving system.

Description
Customer enhancement segment
Unstructured data container that can be used as required.

Value range
Structure BAPIEXTC
Field1 CHAR(250)
Field2 CHAR(250)
Field3 CHAR(250)
Field4 CHAR(250)

Description
Customer enhancement segment
Structured data container that can be used as required.

Value range
Structure BAPIEXT
PARAMETER CHAR(30)
ROW INT (8)
FIELD CHAR(30)
VALUE CHAR(250)
TYPE CHAR(5)
LENGTH INT(4)

Description
The header data of the handling units is passed on to this table.

Description
Header data from handling units, to which multiple deliveries areassigned (cross-delivery HUs), are transferred to this table.

Description
Handling unit identifications are transferred to this table.

Description
The item data of the handling units is passed on to this table.

Description
Additional item data from handling units is transferred to this table.

Description
Enter the serial numbers for a handling unit item.
For materials with a serial number requirement, you enter the serialnumbers of the HU here. The system replaces the serial numbers assignedto the HU with the new serial numbers.

Description
In this table, the header dates are passed on in time stamp format(YYYYMMDDHHMMSS. In field BAPIDLVDEADLN-TIMETYPE the individual datefields are qualified as follows:
- WSHDRLFDAT Delivery date
- WSHDRWADAT Goods issue date (planned)
- WSHDRWADTI Goods issue date (actual)
- WSHDRLDDAT Loading date
- WSHDRTDDAT Transportation planning date
- WSHDRKODAT Picking date

Description
The segment HEADER_PARTNER is used to enter changes to partners.
If business partners are not entered as mandatory partners in thedelivery, you can delete business partners by making an entry in theHEADER_PARTNER table with indicator UPD_MODE_PARTN = D.
You can change data for existing business partners by making an entryin the HEADER_PARTNER table with indicator UPD_MODE_PARTN = U.
If the assigned partner determination procedure permits you to add newbusiness partners, you can add new partners by setting the indicatorUPD_MODE_PARTN = I in the delivery.
You must not delete mandatory partner functions, If you need to deletea mandatory partner, the corresponding partner function must beretained. Where necessary, the system creates an entry in theincompletion log.
You cannot change partners in functions that have been agreed to beunchangeable. The system rejects any requests to make these changes.This is not the same for address data, which must always be changeable.

Description
The parameter HEADER_PARTNER_ADDR is used to enter address changes forthe delivery partner.
To change addresses, set the UPD_MODE_ADR indicator to U.

Description
In this table, the account assignment data is transferred for each item.

Description
This segment contains the control data for confirming the item data.

Description
The general item data is passed on to this table.

Description
Item data is transferred to this table.
This table contains the enhancements for service parts management.

Description
Entry of serial numbers for delivery items.
For materials with a serial number requirement, you must enter theserial numbers here. The system replaces the serial numbers assigned tothe delivery item with the new serial numbers.
If you do not enter any serial numbers for the delivery item, thesystem deletes any serial numbers that had already been assigned.

Exception:
If you do not enter serial numbers for any of the items in thedelivery, the system retains the existing assignment of serial numbers.

Description
The messages are collected and returned to the caller.

Description
Data for vendor consignment is transferred in this table.

Description
The partner system uses this parameter to deliver the token referencefor the CSL. The token is used to issue authorization to changedeliveries across systems. The delivery is blocked in one system if thepartner system opens the delivery in the change transaction, or ifchanges still need to be copied in the partner system in order toachieve a consistent status between the two systems.