Show TOC

Process documentationCreation of ERP Deliveries from SAP TM Locate this document in the navigation structure

 

You use this process if you want to create a delivery proposal in SAP Transportation Management (SAP TM) and send the proposal to SAP ERP where the delivery is created. The delivery proposal is based on the results of transportation planning such as consolidation and dates, taking into account transportation-planning-relevant information such as resource availability and transportation durations. SAP TM can also trigger the creation of deliveries prior to transportation planning.

Process

The following figure shows the process for creating delivery proposals in SAP TM and the subsequent creation of deliveries in SAP ERP and is followed by a description of the process:

This graphic is explained in the accompanying text.

The following abbreviations are used for message types in the above figure:

  • ODBCR: Outbound Delivery Bulk Create Request

  • IDCR: InboundDeliveryCreateRequest

  • ODBC: Outbound Delivery Bulk Confirmation

  • IDC: InboundDeliveryConfirmation_V1

  • TRSR: TransportationRequestSUITERequest

The process runs as follows:

  1. Select input (SAP TM)

    The user can start delivery creation by using a background report or interactively. For more information, see Creation of Delivery Proposals.

    SAP TM considers data for delivery creation from the order-based transportation requirements and from the assigned freight units, freight orders, and freight bookings.

  2. Generate delivery proposals (SAP TM)

    Based on the chosen input, SAP TM creates delivery proposals. A proposal consists of groups of freight units that can be delivered together. Depending on the input method used, SAP TM either sends the proposals automatically to SAP ERP to create deliveries, or the user can check the proposals and then send them to SAP ERP.

    If the user specified a delivery profile that requires the planning results to be fixed for planned freight units, freight orders, or freight bookings, the system fixes the planning results during delivery proposal creation. Otherwise, the system does not fix the planning results.

    After the delivery proposals have been created and sent to SAP ERP, the system creates an entry in the application log. The application log entry includes the delivery proposals that were sent to SAP ERP. Furthermore, the freight units for which a delivery proposal is sent to SAP ERP are marked with a send timestamp.

  3. Create deliveries (SAP ERP)

    When SAP ERP receives the request to create deliveries, SAP ERP creates the deliveries. These can be inbound or outbound deliveries. SAP ERP might split the proposed deliveries further, for example, based on additional split criteria. However, SAP ERP will not change the dates that were proposed by SAP TM nor consolidate proposed deliveries. When SAP ERP creates the deliveries, SAP ERP sends a confirmation of delivery creation to SAP TM, and a request to create a delivery-based transportation requirement in SAP TM.

  4. Log delivery confirmations (SAP TM)

    SAP TM creates an entry in the application log. The application log entry includes the system messages that were created in SAP ERP during delivery creation as well as the number and document IDs of deliveries created in SAP ERP. If an error occurred during delivery creation in SAP ERP, then SAP TM generates an alert.

    When a confirmation is received, SAP TM sets a confirmation timestamp in the relevant freight units. The timestamp is used to monitor whether SAP ERP has responded. For more information about monitoring the delivery creation process, see Monitoring of Delivery Creation.

  5. Create delivery-based transportation requirements (SAP TM)

    For more information, see Integration of ERP Deliveries.

  6. Consume order-based transportation requirements (SAP TM)

    For more information, see Consumption of Order-Based Transportation Requirements.