Kontakt

Ansicht
Dokumentation

BAPI_OUTB_DELIVERY_CHANGE - BAPI for Change to Outbound Delivery

BAPI_OUTB_DELIVERY_CHANGE - BAPI for Change to Outbound Delivery

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

You can use this method to change outbound deliveries in both the Enterprise Resource Planning system (ERP system) and the decentralized Warehouse Management System (WMS), according to their respective distribution to the decentralized WMS. You can make these changes in the central ERP system and in the decentralized WMS. The interface ensures that outbound delivery data planned for a comparison is identical in both systems, even after subsequent changes.

Changing Header Data:

  • Weight (gross weight and net weight)
  • Volume
  • Door
  • Delivery date
  • Delivery priority
  • Route
  • Incoterms
  • Unloading point
  • Delete delivery
You can only delete deliveries in the decentralized system and copy this deletion to the central SAP ERP system, if the decentralized WMS is an external system. For this, set the DLV_DEL indicator in the HeaderControl parameter.

Changing Item Data:

  • Quantity
  • Weight (gross weight and net weight)
  • Volume
  • Expiration date
  • Delete item

Changing Partner Data:

  • Change or delete partner for a partner function
  • Change a partner's address
If you want to change partner data, the system checks the Customizing settings of the other system, to see whether this type of change is permitted.

Change Process Flow

  1. You subsequently change an outbound delivery in the central ERP system or the decentralized WMS, after the delivery was distributed to the decentralized WMS.
  2. If the decentralized WMS is an SAP system, the system blocks the relevant outbound delivery in the partner system as soon as you call the change transaction.
  3. When you save the changes to the outbound delivery, the system sends a synchronous change request to the connected partner system.
  4. The partner system uses the synchronous change request to simulate the change, then either accepts or rejects the change request.
  5. If the partner system rejects the change request, you cannot make the change. The system cancels processing and displays a relevant error message.
  6. If the partner system accepts the change request, the system saves the changes to the outbound delivery in the system in which you have made the changes. It then sends an asynchronous change request to the partner system.
  7. This asynchrounous change request causes the partner system to update the outbound delivery data.
  8. The system removes the cross-system lock for the changed outbound delivery.

Example

If you want to change the quantity for a distributed quantity, then following entries are required for the transfer to the connected system:

  • In the header data of outbound delivery parameter (HEADER_DATA)
  • The delivery number (DELIV_NUMB)

  • In parameter item data of outbound delivery (ITEM_DATA)
  • The delivery number (DELIV_NUMB)

  • The delivery item (DELIV_ITEM)

  • The delivery quantity in sales unit (DLV_QTY)

  • The actual delivery quantity in base UoM (DLV_QTY_IMUNIT)

  • The sales unit (SALES_UNIT)

  • The ISO code for the sales unit (SALES_UNIT_ISO)

  • The base unit of measure (BASE_UOM)

  • The ISO code for the base unit of measure (BASE_UOM_ISO)

  • In the control of the outbound delivery at item level parameter (ITEM_CONTROL)
  • The delivery number (DELIV_NUMB)

  • The delivery item (DELIV_ITEM)

  • The Change Delivery Quantity indicator(CHG_DELQTY)

If you do not make any further entries, the system copies the material number, plant, quantities as floating point numbers, volumes, weights, and their units from the original outbound delivery document.

Further information

Notes

Changes to the packing data are not synchronized in the central ERP system.

For subsequent changes to a distributed inbound delivery, the following prerequisites must be fulfilled:

  • All items in the distribution-relevant inbound delivery have the same decentrally-managed warehouse number.
  • You have generated a distribution model for inbound deliveries. For more information, see the implementation guide (IMG) under Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution -> Generate Distribution Model.
  • In Customizing for Shipping under Deliveries -> Define Delivery Types -> Distribution Mode, you have specified whether the system should distribute the delivery automatically after document creation, or whether distribution should be suppressed so that you can trigger distribution yourself using the delivery monitor.
  • If you use an external system as the decentralized WMS, you must ensure that there is a blocking system for the decentralized system, which prevents a delivery from being processed in both systems at the same time. For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server Technology -> Cross-System Lock (CSL).

If you use the asynchronous interface for the actual transfer of the outbound delivery changes (IDoc category SHP_OBDLV_CHANGE), you must make sure that the structure definition of the IDoc is correct as you construct the IDoc. You should take particular care not to switch the segment sequence.

Batch Split in the Decentralized WMS

  • If you change a batch subitem from a distributed outbound delivery in the decentralized WMS, then this batch subitem already exists in the central ERP system.
The fields HIERARITEM and USEHIERITM are empty. The system copies the batch subitem in the DELIV_ITEM field.
  • If you change the quantity of a batch main item from a distributed outbound delivery in the decentralized WMS, then this batch main item already exists in the central ERP system.
The fields HIERARITEM and USEHIERITM are empty. The system copies the batch subitem into the DELIV_ITEM field.
  • If you perform a batch split for a distributed outbound delivery in the decentralized WMS, only the batch main item exists at that time in the central ERP system.
If, for example, you create two batch subitems, three item segments ItemData are generated for transmission to the central ERP system:
  • The item segment for the batch main item HIERARITEM is empty.

The delivery quantity and base quantity are empty.
  • For each subitem, the system generates an item segment with the following fields:

DELIV_ITEM contains the number of the batch subitem.
HIERARITEM contains the number of the batch main item.
USEHIERITM with value 1 shows that the subitem is used as a batch subitem.
The quantity fields match the quantities in the batch subitems.
The central ERP system performs the batch split subsequently for the distributed outbound delivery.

Further information





Parameters

CHANGE_DECENTRAL
COLLECTIVE_CHANGE_ITEMS
CWM_ITEM_DATA
DELIVERY
EXTENSION1
EXTENSION2
HANDLING_UNIT_HEADER
HANDLING_UNIT_ITEM
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
ITEM_STATUS_SPL
NEW_ITEM_DATA
NEW_ITEM_DATA_SPL
NEW_ITEM_ORG
RETURN
SENDER_SYSTEM
SUPPLIER_CONS_DATA
TECHN_CONTROL
TEXT_HEADER
TEXT_LINES
TOKENREFERENCE

Exceptions

Function Group

V50I

General Material Data   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 11917 Date: 20240523 Time: 174841     sap01-206 ( 139 ms )