Request for Split Delivery 
Use
A split might be required in different business cases, for example, when the planned delivery from the vendor arrives in two different trucks instead of one. In this case, the inbound delivery is split into two: some items remain in the original delivery, and the others are copied to the new delivery. The completely split items (copied with full quantity) are deleted from the original delivery.
Prerequisites
The items to be put in the new delivery must not have reached goods receipt status (partial or complete). If they have this status, the split request does not take place.
Features
The request for a delivery split comes from SAP EWM by means of a remote function call (RFC). SPM dispatches the changed original and the newly created inbound delivery to SAP ICH.
In the split request, data is provided which includes the following:
· The original delivery number
· The number of the newly created delivery
· A set of item details, for example, item numbers, quantities and so on
· An indicator that clarifies whether the items belong to the original or the new delivery
· HU header
· HU items
· HU serial numbers
· Item serial numbers
The header for the new delivery is supplied by SAP EWM. An execution status indicates whether the new delivery has the status In Yard, and the corresponding time stamps are given.
The ERP split interface covers the following two scenarios:
Split Before the First Goods Receipt
This scenario supports the following functions:
- Item split
- Handling units (HUs) transferred using the qRFC interface (in new interface tables) are sent to the split delivery (the subsequent HUs are moved with the top HUs)
- Set the In Yard indicator, depending on RFC interface execution status (both deliveries In Yard or both not In Yard)
- New time stamps for the split delivery are filled by the RFC interface
- New header data for the split delivery is filled by the RFC interface
- EWM, ICH, or ERP can trigger a change to both the original and the split delivery
- Split for On Hold items
The following restrictions apply:
- It is not possible to split HUs; if it were, this could result in the HU being linked to an item in the original delivery and to another item in the split delivery
- It is not possible to delete and repack HUs in the split; you can only delete and repack HUs before the split using the replacement message from EWM
You must use the replacement message from EWM containing the repack information before the split to solve the problem.
Split After the Goods Receipt
This scenario supports the following functions:
- Item split
- GR-posted quantities cannot remain in the original delivery
- Split of On Hold items
- Status In Yard has to be active for the old delivery
- Status In Yard has to be set using the RFC interface for the split delivery
- New time stamps for the split delivery are set using the RFC interface
- New header data for the split delivery is filled by the RFC interface
EWM, ICH, or ERP can trigger a change to the split but not to the original delivery.
The following restrictions apply:
- GR-posted quantities and HUs cannot be split
- The HUs transferred in the RFC interface will be created for the split delivery
- Total quantity per item cannot be changed
- On Hold items can be kept in the original delivery, but because the original delivery cannot be changed, this On Hold item has to be split later
Because of the first GR, all HU information will be deleted in the ERP system. The ERP system needs the latest HU (and serial number) information from EWM.
The following figure provides an overview of the split cases:
The reversal for split is not supported for either of the above scenarios.
Activities
The pre-validation performed here takes place as follows:
1. The systems checks that the header status of the original delivery has not reached Completed (Processed).
2. The system copies the new header data to the new delivery and sets the status In Yard at header and item level, if necessary, and therefore also the corresponding time stamps.