Shipment-Based Tendering

You use this process to tender transportation activities in SAP Transportation Management (SAP TM) that are based on shipments transferred from SAP ERP.

Prerequisites

To connect the SAP ERP system to the SAP TM system, you have set up a configuration scenario for the TM_ERPShipmentIntegration_In inbound integration scenario in SAP NetWeaver Process Integration (SAP NetWeaver PI).
In the SAP TM system, you have defined which freight order types the system uses to create freight orders based on ERP shipments. You have the following options:
- You can assign freight order types to ERP shipment types in Customizing for Transportation Management under Integration ERP Logistics Integration Shipment Integration Assign Freight Order Types to ERP Shipment Types .
- You can specify a default freight order type that the system uses if it cannot find an entry for an ERP shipment type in the Customizing activity Assign Freight Order Types to ERP Shipment Types.
  To specify the default freight order type, select the Default Type for ERP Shipment Integration checkbox in the relevant freight order type in Customizing for Transportation Management under Freight Order Management Freight Order Define Freight Order Types .
You have made the following settings for the relevant freight order type in the Customizing activity Define Freight Order Types:
- You have assigned a suitable output profile to the freight order type.
- You have specified that the freight order type is relevant for subcontracting.
- If you want the freight order to have the same ID as the ERP shipment, you have assigned an external number range interval to the freight order type.
  You define number range intervals in Customizing for Transportation Management under Freight Order Management Freight Order Define Number Range Intervals for Freight Order Management . To ensure that the ERP shipment ID has not already been used in SAP TM for a different freight order, the external number range interval from SAP ERP must not fall within the internal number range interval in SAP TM.
In the SAP TM system, you have enabled PPF output agent /SCMTMS/TOR_TENDERING, which is used to send the tendering result to SAP ERP.
You do this in Customizing for Cross-Application Components under Processes and Tools for Enterprise Applications Reusable Objects and Functions for BOPF Environment PPF Adapter for Output Management Maintain Output Management Adapter Settings . You have to enable the following entry:
- Output Agent: /SCMTMS/TOR_TENDERING
- Business Object: /SCMTMS/TOR
- Node: TENDERING
- Agent Class for BO Node: /SCMTMS/CL_PPF_SERV_TOR_TEND
In the SAP ERP system, you have done the following:
- Set up message control for shipments and made the settings for inbound and outbound processing using IDocs
- Made the settings and implementations in SAP ERP that are described in SAP Note 1527545
- Created shipments that contain stages and assigned deliveries to the shipments
- Assigned all deliveries to stages

Caution Caution

The following restrictions apply to the inbound integration of ERP shipments:

SAP TM can create only one freight order based on an ERP shipment. SAP does not support scenarios in which more than one freight order has to be created in SAP TM to reflect an ERP shipment. As a result, when you create stages in SAP ERP, you can only use those methods that enable stages to be mapped to one freight order in SAP TM.
SAP Note 1527545 contains checks that prevent the creation of shipments that cannot be accepted by SAP TM.
SAP does not support the use of order and delivery integration in conjunction with inbound integration of ERP shipments. The system allows you to transfer shipments and their related deliveries from SAP ERP to SAP TM even if you have already transferred these deliveries (and their related orders) using the order and delivery integration functions.
If you intend to use order and delivery integration in conjunction with inbound integration of shipments in the same SAP ERP client, you must make the required configuration and organizational settings that ensure that the SAP TM system cannot create duplicate transportation requirements.
The inbound integration scenario does not support the processing of delivery item hierarchies in ERP shipments (ERP shipments can contain item hierarchies such as bills of material or item substitution). When SAP TM creates a freight order based on an ERP shipment that contains item hierarchies, the freight order does not reflect the item hierarchies.
Deliveries can contain items that are not relevant for transportation, but that have quantities and weights (main items or subitems in item hierarchies and also other item types). As a result, SAP TM cannot always determine which items are relevant for transportation, and the freight order may contain items that are not necessarily required. You may therefore need to carry out additional filtering of the inbound message received from SAP ERP.
In the inbound integration scenario, SAP ERP does not transfer text items to SAP TM.

End of the caution.

Process

You initiate tendering for a shipment in SAP ERP by setting the tendering status to New Offer from Shipper (for example, using transaction VT02N).
The SAP ERP system automatically sends the shipment to SAP TM using IDoc SHPMNT05.
The SAP TM system creates a freight order based on the shipment data received from SAP ERP.
The inbound enterprise service Maintain Transportation Order (TransportationOrderSCMRequest_In) in SAP TM creates the freight order based on the data sent by IDoc SHPMNT05. Note that this enterprise service and all SAP TM enterprise services mentioned below are in the Transportation Order Processing process component.
You initiate a tendering step in SAP TM for the shipment-based freight order.
For more information about tendering in SAP TM, see Freight Tendering.
When the tendering step has been completed, you transfer the tendering result to SAP ERP.
The outbound enterprise service Notify of Transportation Order Tendering Result (TransportationOrderSCMTenderingResultNotification_Out) in SAP TM sends the tendering result to SAP ERP.

If you have found and accepted a carrier, the enterprise service sends the following data:
- Carrier
- Price
- Confirmed dates and times
- Tendering status
If you have not found a carrier, the enterprise service sends the corresponding tendering status.
SAP ERP receives the tendering result using IDoc SHPMNT05 and updates the shipment accordingly.
You can carry out further steps in SAP ERP.

Result

You can display an overview of shipment-based freight orders in SAP NetWeaver Business Client by choosing ERP Logistics Integration Worklist Overview Freight Orders All Created from ERP Shipment . From the overview, you can branch to the freight order and the ERP shipment.

If you subsequently change delivery quantities or cancel tendering in SAP ERP, the SAP ERP system sends an update to SAP TM as follows:

If you change delivery quantities, SAP ERP automatically sends the updated quantities to SAP TM using IDoc SHPMNT05. The inbound enterprise service Maintain Transportation Order (TransportationOrderSCMRequest_In) in SAP TM receives the information and updates the relevant freight order.
If you cancel tendering in SAP ERP and you delete the ERP shipment, IDoc TPSSHT01 automatically requests the cancellation of the corresponding freight order in SAP TM. The inbound enterprise service Cancel Transportation Order (TransportationOrderSCMCancellationRequest_In) in SAP TM receives the cancellation request and cancels the freight order. Depending on how you have set up the freight order type, the system either deletes the freight order or changes the freight order status to Canceled. The prerequisite for canceling freight orders from SAP ERP is the implementation of SAP Note 1527545.
Note that if you cancel tendering in SAP ERP without deleting the ERP shipment, but you still want to delete the corresponding freight order, you can use IDoc SHPMNT05 to request the cancellation of the freight order in SAP TM.