Show TOC

Process documentationShipment Integration Based on Freight Bookings Locate this document in the navigation structure

 

You use this process to book transportation activities in SAP Transportation Management (SAP TM) that are based on deliveries received from SAP ERP.You can then carry out transportation execution in SAP ERP for the freight bookings. This process is similar to delivery-based planning (see Shipment Integration Based on Freight Orders), but it takes into consideration the booking of transportation activities, for example, with a shipping company or an airline.

Note the following:

  • SAP TM creates a delivery-based transportation requirement (DTR) for each delivery received from SAP ERP. There is always a one-to-one relationship between an ERP delivery and a DTR.

  • SAP ERP creates an ERP shipment for each freight booking received from SAP TM. There is an n-to-one relationship between DTRs and a freight booking; and, therefore, between the ERP deliveries that were originally sent to SAP TM and the ERP shipment that SAP ERP creates based on a freight booking.

Prerequisites

  • You have set up a configuration scenario for the TM_ERPShipmentIntegration_Out outbound integration scenario in SAP NetWeaver Process Integration (SAP NetWeaver PI).

  • You have created deliveries in SAP ERP and transferred them to SAP TM. SAP TM has created one DTR for each delivery. Each DTR contains all items from the corresponding delivery.

  • You have made sure that the relationships between the relevant business documents meet the following requirements:

    • The freight booking (FB) is related only to DTRs (for example, SAP TM cannot send the FB if it is related to an order-based transportation requirement (OTR), or to an OTR and a DTR).

    • The FB contains all freight units (FUs) from each related DTR (that is, the FB, and therefore the ERP shipment, must contain complete deliveries). This is because we do not perform a subsequent delivery split in SAP ERP.

    • The FB must contain FUs that are derived from either exclusively inbound deliveries or exclusively outbound deliveries. The creation of combined inbound and outbound shipments from ERP deliveries is not supported.

    • The FB contains FUs that are related to deliveries from the same ERP system. SAP TM cannot send the FB to SAP ERP if the FB contains deliveries from different ERP systems.

  • You have made sure that the FB meets the following requirements:

    • You have assigned an output profile to the required FB types, and you have defined that the FB types are relevant for shipment creation. For more information, see Customizing for Transportation Management under   Freight Order Management   Freight Booking   Define Freight Booking Types  .

    • The FB is in process and does not have one of the following statuses:

      • Blocked for execution

      • Blocked for planning

      • Marked for deletion

    Process

    1. You send ERP deliveries to SAP TM, and the SAP TM system creates delivery-based transportation requirements (DTRs) for the deliveries.

      For more information, see ERP Logistics Integration.

    2. You plan your transportation process in SAP TM based on the DTRs.

      For more information, see Planning.

      Note that if the ERP deliveries were originally derived from order-based transportation requirements, the system reassigns the freight units from the OTRs to the DTRs without carrying out planning again.

    3. You create a freight booking manually in SAP TM and assign the DTRs to the freight booking.

      For more information, see Creation and Editing of Freight Bookings.

    4. You send the freight booking to the carrier, for example, a shipping company or an airline, and the carrier confirms the freight booking.

    5. You send the freight booking to SAP ERP to carry out transportation execution.

      To send a freight booking to ERP, choose   Follow-Up   Create ERP Shipment   on the freight booking UI. You can also use background report /SCMTMS/TOR_FO_PROC_BATCH. For more information, see Background Processing: Mass Processing of Freight Bookings (FBs)

      SAP TM sends a freight booking to SAP ERP using the enterprise service Request Transportation Order Execution (TransportationOrderSCMExecutionRequest_Out). Note that this enterprise service and all SAP TM enterprise services mentioned below are in the Transportation Order Processing process component.

    6. SAP ERP creates a shipment for each freight booking.

      The freight booking ID and the TM system ID are displayed in the shipment header. After setting the status of the shipment, SAP ERP sends a status update to SAP TM. The execution status of the corresponding freight booking is changed to In Execution. As soon as this status is set, no further changes are allowed to the freight booking in SAP TM.

      SAP ERP creates a shipment using IDoc SHPMNT05. It uses the same IDoc to send a confirmation of shipment creation and to send the status update. SAP TM receives the confirmation using the enterprise service Change Transportation Order based on Transportation Order Execution Confirmation (TransportationOrderSCMExecutionConfirmation_In). SAP TM receives the status update using the enterprise service Change Transportation Order based on Transportation Order Execution Status Notification (TransportationOrderSCMExecutionStatusNotification_In).

    7. You carry out transportation execution in SAP ERP for the shipments.

    Result

    If you cancel a freight booking that has already been sent to SAP ERP, SAP TM sends a cancellation request using the enterprise service Request Transportation Order Execution Cancellation (TransportationOrderSCMExecutionCancellationRequest_Out). The cancellation request is received by IDoc TPSSHT01 in SAP ERP.

    If you cancel an ERP shipment that was created from a freight booking, SAP ERP sends a cancellation request using IDoc TPSSHT01. SAP TM receives the cancellation using the enterprise service Cancel Transportation Order (TransportationOrderSCMCancellationRequest_In).