SAP S/4HANA Transportation Management (TM): Freight Order Execution & Clean Core Carrier Collaboration

1. The End of LE-TRA (Shipments): Why Migration is Mandatory

In classic SAP ECC, transportation execution was driven by module LE-TRA (transactions VT01N, VT02N, tables VTTK, VTTP, VF01 for shipment costing). Like LE-WM, LE-TRA belongs to the S/4HANA Compatibility Pack, which reaches official end-of-use rights by end of 2025/2026.

Continuing to rely on VTTK/VTTP creates enormous upgrade obstacles. SAP S/4HANA Transportation Management (TM) is the strategic, clean core replacement, integrating seamlessly with Extended Warehouse Management (EWM) and the Universal Journal (ACDOCA).

2. Architectural Comparison: LE-TRA vs. S/4HANA TM

Capability	Legacy LE-TRA (Compatibility Pack)	SAP S/4HANA TM (Clean Core)
Core Business Object	Shipment Document (Table `VTTK`)	Freight Order (`/SCMTMS/TOR`) & Freight Unit (`FU`)
Planning Foundation	Manual grouping based on Outbound Deliveries	Automated optimization engine (Vehicle Routing / Scheduling)
Carrier Collaboration	Point-to-point IDocs (`SHPMNT`)	CloudEvents 1.0, REST APIs & SAP Business Network for Logistics
Freight Costing	Shipment Cost Document (`VFKP`) -> Purchase Order	Freight Settlement Document (`FSD`) -> Service PO -> `ACDOCA`
Extensibility Model	Classic User Exits (`V56K0001`) & BAdI `BADI_LE_SHIPMENT`	Clean Core Released BAdI `/SCMTMS/EX_TOR_SUBMIT`

3. Automated Freight Cost Settlement to Universal Journal (ACDOCA)

In Clean Core S/4HANA TM, freight cost accounting is automated from contract execution through financial settlement:

Freight Agreement & Rate Calculation: The Transportation Charge Calculation engine determines expected freight costs based on contracted carrier rate sheets.
Freight Settlement Document (FSD): When the freight order status reaches Execution or Proof of Delivery (POD), an FSD is automatically created.
Universal Journal Commit: The FSD creates an automatic Service Purchase Order and triggers Service Entry Sheet (SES) posting, directly debiting freight expense and crediting freight clearing in ACDOCA with zero manual intervention.

Clean Core Transportation Rule

Never write direct database updates to legacy tables VTTK or VTTP in S/4HANA. All transportation extensions must target the released Business Object /SCMTMS/TOR and consume released CDS entities like /SCMTMS/I_FreightOrder.

4. Interactive Architecture Generator

Design your S/4HANA TM landscape, evaluate Basic vs Advanced TM sizing, and generate clean core BAdI code with Tool #104:

🚢 Launch Tool #104: S/4HANA TM Clean Core Architect →

5. S/4HANA TM Migration Checklist from LE-TRA

Audit Existing Shipments: Scan custom code using ATC with variant ABAP_CLOUD_READINESS to identify direct reads/writes to VTTK, VTTP, and VFKP.
Map Shipment Types to Freight Order Types: Define equivalent 4-character Freight Order types (e.g. 6100 for Road Transport).
Migrate Carrier Interfaces: Replace point-to-point IDocs with modern REST webhooks conforming to CloudEvents 1.0 or connect to SAP Business Network for Logistics.
Decommission V56K User Exits: Move business validation and carrier determination logic into released Clean Core BAdI /SCMTMS/EX_TOR_SUBMIT.

SAP S/4HANA Transportation Management Architecture

Sunset LE-TRA & Upgrade Your Freight Operations