Show TOC

Function documentationMonitoring of Delivery Creation Locate this document in the navigation structure

 

When you send a delivery proposal to SAP ERP, the SAP TM system sets a send timestamp in the freight units to which the delivery proposal relates. When SAP ERP sends a confirmation of delivery creation, the SAP TM system sets a confirmation timestamp in these freight units. If delivery creation is successful, SAP ERP also sends a request to create a delivery-based transportation requirement (DTR), and the SAP TM system reassigns the freight units from the order-based transportation requirement (OTR) to the DTR.

To monitor the delivery creation process, SAP TM checks whether freight units contain a confirmation timestamp and whether they have been reassigned from an OTR to a DTR.

Note Note

The above process also applies to directly created freight orders, which have similar characteristics to freight units. For more information about directly created freight orders, see Direct Creation of Freight Orders.

End of the note.

Features

SAP TM provides the following worklists for monitoring the delivery creation process:

  • Order-Based FUs with Incomplete Delivery Creation (for freight units) and Order-Based FOs with Incomplete Delivery Creation (for directly created freight orders)

    These worklists contain all freight units or directly created freight orders with the following attributes:

    • They contain a send timestamp.

    • They do not contain a confirmation timestamp, that is, SAP ERP has not responded yet.

    • They are still related to an order-based transportation requirement.

    Since SAP ERP has not responded yet, you cannot repeat the delivery proposal process for these freight units or directly created freight orders.

    In this case, the messages used to exchange information between SAP TM and SAP ERP might still be in a message queue. You can use transaction SXMB_MONI to check the status of the messages and, if necessary, retrigger them.

  • Order-Based FUs with Failed Delivery Creation (for freight units) and Order-Based FOs with Failed Delivery Creation (for directly created freight orders)

    These worklists contain all freight units or directly created freight orders with the following attributes:

    • They contain a send timestamp.

    • They contain a confirmation timestamp, that is, SAP ERP has already responded.

    • They are still related to an order-based transportation requirement, that is, the system has not reassigned the freight units or directly created freight orders from an OTR to a DTR.

    In this case, SAP ERP was unable to create the deliveries and, as a result, did not request the creation of a DTR.

    To find out why delivery creation failed, you can branch from the worklist to the business application log entries for a freight unit or a directly created freight order. If there were problems during delivery creation, SAP ERP sends a log item that contains the reason why particular deliveries could not be created, for example. After checking why delivery creation failed, you can repeat the delivery proposal process directly from the worklist.

Activities

To call up the worklists in SAP NetWeaver Business Client, choose   ERP Logistics Integration   Worklist   Overview Transportation Requirements (Not Finalized)  .