Subsequent Changes to Distributed Deliveries (SAP Library - Decentralized Warehouse Management (LE-IDW))

Subsequent Changes to Distributed Deliveries

Purpose

You can make subsequent changes to deliveries after they have been distributed from the centralized to the decentralized system. You can make this kind of change in both the central system and the decentralized WMS. The interface ensures that the following delivery data, which provides a comparison, is the same in both systems even after subsequent changes have been made:

Changes to the Delivery

Header Data	Item Data
Gross weight	Gross weight
Net weight	Net weight
Volume	Volume
Delivery date and time	Shelf life expiration date
Door	Delivery quantity
Delete delivery (only via the interface)	Delete delivery (only via the interface)
External identification

Changes to the Delivery

Header Data	Item Data
Gross weight	Gross weight
Net weight	Net weight
Volume	Volume
Delivery date and time	Delivery quantity
Door	Delete delivery (only via the interface)
Delete delivery (only via the interface)
Incoterms
Route
Shipping conditions
Delivery priority
Unloading point
Pick date and time
Loading date and time
Transportation planning date and time
Goods issue date and time
Delivery block

Note

If you want to change partner data, the system checks in the Customizing of the relevant partner system to see whether this kind of change is allowed.

Outbound Delivery Split in a Decentralized External System

If you execute an outbound delivery split in the decentralized system, you can no longer change the original delivery in the central system. You must ensure that the distribution status of the original delivery is set to E in the central system immediately after the decentralized delivery split.

To do this, you can use the IDoc with the logical message type SHP_OBDLV_CHANGE. Enter the following values in the IDoc:

Field	Value
E1SHP_OBDLV_CHANGE-DELIVERY	Delivery number
E1BPOBDLVHDRCHG-DELIV_NUMB	Delivery number
E1BPOBDLVHDRCTRLCHG-SPLIT_DONE_FLG	E

Prerequisites

All of the items in the distribution-relevant delivery have a common decentrally managed warehouse number.

In the Customizing for Shipping under Deliveries ® Delivery Types ® Distribution Mode, you have defined that the system is to distribute the delivery either automatically following document creation, or in background processing.

You must make sure that a locking concept is in place on the decentralized WMS side, so that you cannot process a delivery in both systems simultaneously. For additional information on cross-system locks, see Basis ® Client/Server Technology ® Cross-System Lock (CSL) in the SAP Library.

Distribution model does not yet exist

You generate a distribution model for inbound and outbound deliveries and activate change management for both inbound and outbound deliveries. For more information, see Logistics Execution ® Decentralized WMS Integration ® Central Processing ® Distribution ® Generate Distribution Model in the Implementation Guide (IMG) for Logistics

Note

Once change management has been set up, you can deactivate it by removing the activation indicator in the central system and the decentralized system. The methods InboundDelivery.DeliveryChange and OutboundDelivery.DeliveryChange can remain in the ALE distribution model even if change management has been deactivated.

You can find additional information in the Implementation Guide (IMG) under Logistics Execution ® Decentralized WMS Integration ® Central Processing ® Application ® Define Interface to Inventory Management and Delivery-Relevant Data ® Controlling Change Management for Deliveries.

Distribution model already exists

Add the following methods to the distribution model in the central system via the ALE Customizing:

InboundDelivery.DeliveryChange

OutboundDelivery.DeliveryChange

Set the filter for receiver determination for these methods:

Receiver determination occurs via the filter warehouse number from the central system to the decentralized system.
If both systems are of at least Release 4.70, you can use the filter logical system for receiver determination from the decentralized system to the central system.

You generate the partner profile for the new methods.

You distribute the distribution model to the connected decentralized WMS.

Process Flow

You make a subsequent change to an inbound or outbound delivery in the central ERP system, after it has been distributed to the decentralized WMS.

If the WMS is an SAP System, the system locks the corresponding delivery for change in the decentralized system, as soon as you call the transaction in the central system.

As soon as you save the changes to the delivery in the central ERP system, the central system sends a synchronous change request to the decentralized WMS (automatic check of the distributed document).

Caution

As a result of the synchronous change request, the two systems are closely linked. This means that you must ensure that both systems are available at all times.

Note

You can check whether the decentralized WMS can adopt your changes even when the delivery is being processed. To do this, choose Change Delivery ® Edit ® Check Distributed Document.

The decentralized WMS checks the change request and accepts or rejects it.

If the decentralized WMS rejects the change request, you cannot execute the change in the central system. The system issues an error message.

If the decentralized WMS accepts the change request, the central system ends the data backup and sends an asynchronous change request to the decentralized system.

The decentralized WMS updates the delivery data on the basis of the asynchronous change request.

This graphic is explained in the accompanying text

Note

In order to be able to execute work steps in one of the systems without affecting the other system, you can change fields in the delivery other than those named above. However, there is no balancing out between the two systems.

This is the case, for example, if you change invoice-relevant data in the central ERP system that is not relevant for processing in the decentralized WMS, or if you change the header text or item texts in the delivery.

Packing in Connection with Change Management

Note that changes in the partner system during packing are not synchronized.