- ERP Factory
- /Offers
- /LE-TRA to SAP TM Migration
LE-TRA to SAP TM Migration
From legacy shipment management to modern transportation execution — a structured migration path from classic LE-TRA to SAP TM, scoped to your actual shipment volume, carrier network and integration landscape.
Who this is for
Your transportation processes still run on classic LE-TRA shipment cost documents
Your S/4HANA transformation programme needs a decision on the transportation execution target architecture
Custom LE-TRA developments (user exits, Z-programs) have accumulated and their fate in a TM world is unclear
Your carrier interfaces (EDI, IDocs, APIs) will need to be re-pointed or redesigned for SAP TM
You lack transportation visibility across planning, tendering and execution today
Shipment cost calculation and settlement in LE-TRA no longer reflect your actual carrier agreements
Questions we help answer
- What in our current LE-TRA setup has no direct equivalent in SAP TM, and what does that mean for our custom code?
- Should we run SAP TM embedded in S/4HANA or as a decentralized deployment for our landscape?
- Which shipment cost documents and carrier agreements need to be redesigned rather than migrated as-is?
- How do we keep transportation running during the cutover from LE-TRA to TM?
- What does SAP TM's integration with our existing SAP EWM and S/4HANA logistics execution actually require?
- What's a realistic sequencing for assessment, design, build and cutover given our transportation volume?
What we assess
The assessment is scoped to your landscape — not every area below applies to every engagement.
- Current LE-TRA shipment types, shipment cost documents and custom logic
- Custom developments: Z-programs, user exits, BAdIs
- Interfaces: IDocs, EDI messages, carrier APIs and third-party connections
- Target SAP TM process model: freight units, freight orders, planning and execution
- Integration with SD, MM and SAP EWM
- Master data, organizational structures and business partners
- Open transactional data and cutover dependencies
- Parallel-run and regression testing feasibility
Our 8-step migration methodology
A sequence we adapt to your landscape, not a fixed template applied regardless of scope.
Assessment
Inventory of the existing LE-TRA scope, dependencies and risks.
Process Mapping
Map shipments, stages and shipment costs to target SAP TM concepts.
Custom Code & Interfaces
Analyze Z programs, exits, BAdIs, IDocs, EDI, APIs and third-party connections.
Target TM Architecture
Embedded vs. decentralized deployment where applicable, freight units, freight orders, planning, execution, settlement and SD/MM/EWM integration.
Data & Migration
Master data, organizational structures, business partners, locations, relevant conditions and open transactional data.
Parallel Run & Testing
SIT, UAT, regression testing, reconciliations and parallel operations where feasible.
Cutover
Deployment sequencing, dependencies, rollback planning and operational readiness.
Hypercare
Stabilization, defect resolution, operational support and knowledge transfer.
Ready to scope this for your landscape?
Request a Migration Readiness AssessmentTypical deliverables
Deliverables are scoped per engagement — not every migration includes every item below.
LE-TRA Landscape & Dependency Assessment
Target SAP TM Architecture Blueprint
Functional Gap Analysis
Custom Code & Integration Inventory
Migration Roadmap & Effort Estimation
Cutover & Hypercare Strategy
Why ERP Factory
- We specialise in SAP TM and SAP EWM — transportation and warehouse execution are our core field, not a generalist SAP practice
- Senior architects who have worked on LE-TRA to TM migrations lead the assessment and design, not a templated questionnaire
- We assess the integration boundary with SAP EWM and S/4HANA logistics execution as part of the same engagement, not as an afterthought
- The target architecture is scoped to your actual shipment volume and carrier network, not a maximal reference architecture by default
Frequently asked questions
Is migration from LE-TRA to SAP TM mandatory?
Whether — and when — a move away from LE-TRA applies to you depends on your SAP release, maintenance strategy and licensing agreement. We help clarify what applies to your specific landscape rather than assume a universal deadline.
What is the difference between LE-TRA and SAP TM?
LE-TRA is the classic ERP shipment cost module; SAP TM is a separate, more capable transportation management application built around freight units, freight orders, tendering and a dedicated charge calculation engine. The two are not functionally equivalent, so moving between them is a process redesign, not a technical upgrade.
How long does a migration take?
Duration depends on shipment volume, carrier and interface complexity, and the scope of custom development in your current LE-TRA setup. We size this during the assessment phase rather than quote a fixed timeline upfront.
Can existing interfaces and custom code be reused?
Some can be adapted, but LE-TRA's extension points don't map directly onto SAP TM's. Each interface and custom development needs to be assessed individually to decide what's rebuilt, retired or redesigned.
How does SAP TM integrate with SAP EWM?
SAP TM integrates with SAP EWM for dock- and yard-driven loading and execution scenarios, and with S/4HANA logistics execution for delivery- or order-driven processes. The right pattern depends on how your warehouse and transportation operations are structured today.
Should we choose embedded or decentralized SAP TM?
This depends on your system landscape, transaction volume and how independently transportation needs to operate from your ERP release cycle. We help evaluate both options against your actual constraints rather than default to one.
Related expertise
Related insights
LE-TRA to SAP TM Migration
From legacy shipment management to modern transportation execution — a structured migration path from classic LE-TRA to SAP TM, scoped to your actual shipment volume, carrier network and integration landscape.