Kontakt

Ansicht
Dokumentation

/SPE/INB_DELIVERY_CONFIRM_DEC - BAPI for Inbound Delivery Confirmation from a Decentralized System

/SPE/INB_DELIVERY_CONFIRM_DEC - BAPI for Inbound Delivery Confirmation from a Decentralized System

BAL_S_LOG - Application Log: Log header data   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You can use this method to report back inbound deliveries from a WM system to an Enterprise Resource Planning (ERP) system. Essentially, such as report would include:

  • Header data from the delivery,
that must always be reported back.
  • Delivery items,
whereby you only need to report those items that have changed.
  • Packaging data,
which you do not have to report if the delivery does not contain any packaging data. However, if delivery items have been packed, then you must always report back the complete packing hierarchy. Any packaging data you do not report back is deleted.

Example

Three examples of how to use the BAPI are explained below:

  1. Reporting back of an unpacked inbound delivery without changes
  2. Reporting back of an unpacked inbound delivery with changes
  3. Reporting back of an packed inbound delivery without changes

For each of the segment types reported back, there follows a list of particular example fields.

  1. The item data of the delivery is reported back unchanged, and the delivery contains no packaging data.
DELIVERY - Document number of the inbound delivery
  • Field DELIV_NUMB - Delivery number

HEADER_DATA - Header data of the inbound delivery
  • Field DELIV_NUMB - Delivery number

HEADER_CONTROL - Header control data
  • Field DELIV_NUMB - Delivery number

  • Feld POST_GI_FLG - Indicator: Post automatic goods movement

  1. The item data of the delivery is reported back changed, and the delivery does not contain any packaging data.
DELIVERY - Document number of inbound delivery
  • Field DELIV_NUMB - Delivery number

HEADER_DATA - Header data of the 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

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

  1. The item data in the delivery document is confirmed unchanged and the delivery does not contain any packaging data.
DELIVERY - Document number of the inbound delivery
  • Field DELIV_NUMB - Delivery number

HEADER_DATA - Header data of the inbound 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

HANLDING_UNIT_HEADER - Handling unit header data
  • Field DELIV_NUMB - Delivery number

  • Field HDL_UNIT - Internal handling unit number

  • Field HDL_UNIT_EXID - External handling unit number

HANDLING_UNIT_ITEM - Handling unit item
  • Field DELIV_NUMB - Delivery number

  • Field HDL_UNIT_INTO - Handling unit into which will be packed

  • Field HDL_UNIT_EXID_INTO - Number of the handling unit into which will be packed

If the delivery contains packaging data, then as well as the above- listed header data (DELIVERY, HEADER_DATA, and HEADER_CONTROL) and delivery item data (ITEM_DATA and ITEM_CONTROL), you must also report back the current packing hierarchy.
To do this, fill the segments of type HANDLING_UNIT_HEADER and HANDLING_UNIT_ITEM. If you want to report an empty handling unit, then you should only fill the segement of type HANDLING_UNIT_HEADER. Note, that handling units created in the central system for the inbound delivery are deleted if you do not report them back.

Material number, plant, quantities in floating values, volumes, weights and their units are copied from the delivery document, if not specified.

Error messages are recorded in the 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 the packaging materials HDL_UNIT_EXID_INTO/HDL_UNIT_EXID. The fields can be found in the HANDLING_UNIT_ITEM segment. You must copy the handling unit into the HDL_UNIT_EXID_INTO field when you report bakc to packing.

If you report back batch splits that were created in the ERP, the hierarchy fields HIERARITEM and USEHIERITM must not contain information.

If you created split items in the Warehouse Management System and have reported back, these two hierarchy fields must contain information.

If you are not using an SAP system as your 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

CWM_HU_ITEM
CWM_ITEM_DATA
DELIVERY
EXTENSION1
EXTENSION2
HANDLING_UNIT_HEADER
HANDLING_UNIT_HEADER_CROSS
HANDLING_UNIT_HEADER_EPC
HANDLING_UNIT_IDENTIFIERS
HANDLING_UNIT_ITEM
HANDLING_UNIT_ITEMS_EPC
HANDLING_UNIT_ITEM_SPL
HANDLING_UNIT_SERNO
HEADER_CONTROL
HEADER_CONTROL_SPL
HEADER_DATA
HEADER_DATA_SPL
HEADER_DEADLINES
HEADER_PARTNER
HEADER_PARTNER_ADDR
ITEM_CONTROL
ITEM_DATA
ITEM_DATA_DOCU_BATCH
ITEM_DATA_SPL
ITEM_SERIAL_NO
IV_SERVICE_CALL
KANBAN_ITEM_DATA
RETURN
TECHN_CONTROL
TEXT_HEADER
TEXT_LINES
TOKENREFERENCE

Exceptions

Function Group

/SAPLINB_DELIVERY

PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 9714 Date: 20240426 Time: 052514     sap01-206 ( 170 ms )