Show TOC

Process documentationIntegration of ERP Deliveries Locate this document in the navigation structure

 

You use this process if a customer creates a delivery in SAP ERP and sends it to SAP Transportation Management (SAP TM). In this process, a delivery-based transportation requirement is created in SAP TM based on the delivery from SAP ERP. If the corresponding order was also sent to SAP TM, the transportation demand of the order-based transportation requirements is consumed.

Process

Integration of ERP Deliveries Without Sending ERP Order to SAP TM

The following figure shows the process flow for a delivery that is created in the SAP ERP system and sent to SAP TM, where a corresponding order-based transportation requirement has not been created in SAP TM:

This graphic is explained in the accompanying text.

Integration of ERP Deliveries Without Sending ERP Order to SAP TM

In the above figure, the abbreviation TRSR means TransportationRequestSUITERequest.

The process runs as follows:

  1. Create order (SAP ERP)

    An order is created in SAP ERP, but is not sent to SAP TM.

  2. Create deliveries (SAP ERP)

    Deliveries for the order are created in SAP ERP. SAP ERP sends the deliveries to SAP TM.

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

    When SAP TM receives the deliveries, SAP TM creates delivery-based transportation requirements for these deliveries.

  4. Create freight units (SAP TM)

    Since no corresponding order-based transportation requirements exist for the delivery-based transportation requirement, SAP TM creates new freight units for the delivery-based transportation requirement, according to the freight unit building rule specified.

  5. Perform transportation planning (SAP TM)

  6. Execute transportation (SAP TM)

Integration of ERP Deliveries With Order Integration

The following figure shows the process flow for a delivery that is created in the SAP ERP system and sent to SAP TM where a corresponding order-based transportation requirement exists in SAP TM. There are two alternative processes that can precede this process:

  • An order has been sent to SAP TM and SAP TM has sent a delivery proposal to SAP ERP (see Creation of ERP Deliveries from SAP TM).

  • An order has been sent to SAP TM, but SAP TM has not sent a delivery proposal to SAP ERP.

This graphic is explained in the accompanying text.

Integration of ERP Deliveries With Order Integration

In the above figure, the abbreviation TRSR means TransportationRequestSUITERequest.

The process runs as follows:

  1. Create deliveries (SAP ERP)

    Deliveries are created in SAP ERP. SAP ERP sends the deliveries to SAP TM.

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

    When SAP TM receives the deliveries, SAP TM creates delivery-based transportation requirements for these deliveries.

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

    Since one or more corresponding order-based transportation requirements exist in SAP TM, the delivery-based transportation requirements consume the transportation demand of the order-based transportation requirement.

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

  4. Adapt transportation planning (SAP TM)

    Depending on change controller setting, SAP TM can adjust the transportation planning that had previously been performed for the order-based transportation requirement. For more information about the change controller, see Change Controller.

  5. Execute transportation planning (SAP TM)

    Note Note

    You can display individual overviews of delivery-based freight orders, delivery-based air freight bookings, and delivery-based ocean freight bookings in SAP NetWeaver Business Client by choosing   ERP Logistics Integration   Worklist   Overview Freight Orders and Freight Bookings  .

    End of the note.