SAP Transportation Management

Order integration
Order integration

SAP TM can integrate the following SD and MM documents

• Sales orders (SOs)

• Purchase orders (POs)

• Stock transfer orders (STOs)

• Inbound deliveries

• Outbound deliveries

• Scheduling agreements
Business functions

These business functions are necessary for the integration with the SAP TM function ality within the same SAP

S/4HANA system

• LOG_TM_ORD_INT

• LOG_TM_ORD_INT_II

• LOG_TM_ORD_INT_III

• LOG_TM_ORD_INT_IV

• LOG_TM_IV_INT

• SD_01

• OPS_ADVRETURNS_1
Control keys & logistics integration profile

• Activation of the sales document is done via a control key, which defines which
document types should be integrated.

• Here we can select the internal TM component or an external SAP TM system.

• The logistics integration profile consolidates all configuration that is required to

trigger the transportation management process, such as the freight unit
building rule (FUBR) or the decision regarding whether to plan on requested or
confirmed quantities.
Logistics integration profile

• We can define freight unit building rule that is used when freight units are created for business

documents.

• BRF+ Condition for FUBR selection

• Incoterm location is the location where the ownership for the goods change.

• Incoterm Loc. Stage Bldng field defines how many stages will be built for freight units if the incoterm

location is used for stage building.

• Usually the freight unit created out of the order or delivery would only contain one stage, from the

source to destination
 Logistics integration profile

• Here we define whether the stage the shipper isn't responsible for should be created at all. If it should be
created, it will be created as a statistical stage, meaning it has no influence on the freight unit and therefore
on the planning process steps.

Prerequisites

• Incoterm should have LOC flag set if it is used for stage building

• Assign location to incoterms location in /SCMTMS/INCLOC_MAP

Two Active Stages

• Two planning-relevant stages are created

Source Location to Incoterm Location - Type 1

• One stage from the source to the incoterm location is created.

Logistics integration profile

Source Location to Incoterm Location - Type 2

• An active stage from the source location to the incoterm location

• An inactive stage from the Incoterm location to the destination location which is not relevant for planning

Incoterm Location to Destination - Type 1

• One stage from the incoterm location to the destination.

Incoterm Location to Destination - Type 2

• An active stage from the Incoterm location to the destination location

• An inactive stage which is not relevant for planning from the source location to the Incoterm location
 Stage profile

• In stage profile we specify which stage types are to be created for freight units

• Stage profile generally used for FWO or FWQ

SPRO → TM → FWO management → Define stage profile

• Stage type

• Stage type occurrence – Stage type is mandatory or not. If mandatory then stage proposal check box should

be selected

• Stage proposal checkbox – Determines if stage should be generated automatically

• Determination Rule for Non-Planning-Relevant Stages - Determine whether a stage is relevant for planning.

• Set rule – Define minimum execution status of stage in FWO for internal settlement
Order integration

• Sales org + Distribution channel + Division + Shipping condition + Sales document type will

be assigned to Control key & Integration profile

• Purchasing document type + Purchasing organization + Purchasing group will be assigned

to Control key & Integration profile

• Shipping point + Delivery type + Shipping condition will be assigned to Control key &

Integration profile

• Report to create deliveries - /SCMTMS/DLV_BATCH