Delivery Splits and Updates Triggered by SAP TM

You can split an outbound delivery in SAP ERP based on planning changes in SAP TM. You can also update the goods issue date, loading date, transportation start date, and delivery date in the outbound delivery based on changed dates in SAP TM.

When SAP ERP receives a request for a split or update, it makes the necessary changes in outbound delivery processing and sends the delivery data back to SAP TM. SAP TM can then make the required changes to the delivery-based transportation requirements (DTRs).

Note that SAP TM can trigger the split or update of outbound deliveries only. It cannot trigger the split or update of inbound deliveries.

Prerequisites

You have created a delivery-based transportation requirement (DTR) in SAP TM based on an SAP ERP outbound delivery.
The outbound delivery in SAP ERP does not have one of the following statuses:
- Distribution status: Distributed
- Goods movement status: Partially Completed or Completed
If the delivery has one of the above statuses, SAP TM does not request the split or update. In the delivery split/update type, you can define whether the system is to display an error or warning message if relevant changes are made when the delivery has one of the above statuses.
You have defined a delivery split/update type in Customizing for Transportation Management under Integration ERP Logistics Integration Delivery-Based Transportation Requirement Define Delivery Split/Update Types .
You define the following in the split/update type:
- You define whether SAP TM sends a delivery split or update to SAP ERP if relevant changes have been made in SAP TM.
- You define whether a system message is to be displayed if a delivery split or update is required in SAP ERP, but the SAP ERP delivery can no longer be changed because it has one of the statuses mentioned above. If no message or a warning message is displayed, SAP TM saves the planning changes even though they are not sent to SAP ERP. If an error message is displayed, SAP TM does not save the planning changes.
- You can enter a delivery split reason that enables SAP ERP to determine the required split profile.
For more information, see the documentation of the Customizing activity.
You have assigned the delivery split/update type to the delivery-based transportation requirement type in Customizing for Transportation Management under Integration ERP Logistics Integration Delivery-Based Transportation Requirement Define Delivery-Based Transportation Requirement Types .

Process

Outbound Delivery Split

Perform transportation planning (SAP TM)
You perform planning or change the existing planning of freight units that belong to a DTR that is based on an outbound delivery. When you save the planning results, the system determines that a delivery split is required. For example, freight units that belong to the DTR have been assigned to different freight orders, or only some of the FUs that belong to a DTR have been assigned to freight orders and the other FUs have not been assigned. Note that the split is required only if the first stage or the last stage of the transportation chain is affected.

SAP TM determines whether the SAP ERP delivery can still be changed by checking the delivery status. If the delivery can be changed, SAP TM sends the required delivery split to SAP ERP. SAP TM sends the details of the items that are to be split from the original delivery (that is, IDs of the items in the original delivery, split quantity, unit of measure, and the required dates for the new delivery).

SAP TM sends the split request using the Request Outbound Delivery Split V1 (OutboundDeliveryERPSplitRequest_Out_V1) enterprise service in the Transportation Request Processing process component. Note that if a delivery is to be split into several deliveries, each delivery is sent to SAP ERP in a separate message.
Split outbound delivery (SAP ERP)
Based on a split request received from SAP TM, SAP ERP creates a new outbound delivery and changes the original outbound delivery (that is, it removes the relevant items from the original delivery and creates a new delivery for these items). If you specified a split reason in the delivery split/update type, SAP ERP splits the delivery according to the settings in the corresponding split profile.

SAP ERP informs SAP TM about whether the delivery split was successful. The confirmation is received in SAP TM by the Change Transportation Request Based on Outbound Delivery Split Confirmation V1 (OutboundDeliveryERPSplitConfirmation_In_V1) enterprise service in the Transportation Request Processing process component.

SAP ERP sends the following information in separate messages:
- The new delivery that has been created for the items split from the original delivery. The data sent includes a reference to the original delivery and the triggering application SAP TM.
- The changed original delivery. The data sent includes a reference to the new delivery.
Create new DTR and update original DTR (SAP TM)
SAP TM creates the new DTR first by reassigning the freight units from the original DTR to the new DTR. It then updates the original DTR.

SAP TM receives a new or updated delivery using the Maintain Transportation Request (IntracompanyTransportationRequestRequest_In) enterprise service in the Transportation Request Processing process component.

Outbound Delivery Update

Perform transportation planning (SAP TM)
You perform planning or change the existing planning of freight units that belong to a DTR that is based on an outbound delivery. Dates are changed during planning. Alternatively, you change the dates of the relevant freight order. When you save the planning results or the changed freight order, SAP TM determines that the dates in the freight order no longer match the dates in the DTR and the original SAP ERP delivery.

SAP TM determines whether the SAP ERP delivery can still be changed by checking the delivery status. If the delivery can be changed, SAP TM sends the changed dates to SAP ERP and requests the update of the outbound delivery.

SAP TM sends the update request using the Request Outbound Delivery Update (OutboundDeliveryUpdateRequest_Out) enterprise service in the Transportation Request Processing process component.
Update outbound delivery (SAP ERP)
Based on the request received from SAP TM, SAP ERP updates the relevant dates.

SAP ERP informs SAP TM about whether the delivery update was successful. The confirmation is received in SAP TM by the Change Transportation Request Based on Outbound Delivery Update Confirmation (OutboundDeliveryConfirmation_In_V1) enterprise service in the Transportation Request Processing process component.

SAP ERP sends the updated outbound delivery to SAP TM. In SAP TM, the delivery is received by the Maintain Transportation Request (IntracompanyTransportationRequestRequest_In) enterprise service in the Transportation Request Processing process component.
Update DTR (SAP TM)

Result

The planning data in SAP TM and the SAP ERP delivery data is aligned.

Note the following:

The triggering application is included in the message sent by SAP ERP. This enables SAP TM to distinguish between a split that is triggered by SAP TM (planning is correct) and a split triggered by SAP ERP or SAP EWM (planning is no longer correct and must be updated).
If SAP TM triggers a delivery split and a delivery update for the same delivery at the same time, the split and update is sent in the same message using the Request Outbound Delivery Split V1 (OutboundDeliveryERPSplitRequest_Out_V1) enterprise service.

You can use a worklist to monitor DTRs for which a delivery split or update has not been completed yet. In SAP NetWeaver Business Client choose ERP Logistics Integration Worklist Overview Transportation Requirements (Not Finalized) DTRs with Incomplete Delivery Splits/Updates .