If your transportation processes still run on LE-TRA, you already know this conversation is coming. Maybe your S/4HANA program has raised it. Maybe your auditors have. Maybe a planner asked why the shipment screen looks like it did fifteen years ago.
The good news is that you have time. The bad news is that most teams use that time badly. They wait, then rush, then discover halfway through testing that freight costs don’t match and nobody can explain why.
This article walks through what an LE-TRA to SAP TM migration actually involves. What changes, what breaks, how to approach it, and how to tell whether it worked.
-
Why Companies Migrate
There are two reasons, and both matter.
The first is the deadline. SAP announced back in 2014 that LE-TRA is not the target architecture in S/4HANA, and that position hasn’t moved since. Most S/4HANA compatibility scope usage rights expired on 31 December 2025. LE-TRA is one of three exceptions, along with Customer Service and selected PP-PI items, with usage rights extended to 31 December 2030.
After that date you no longer have the contractual right to use it under compatibility scope. Not the ability, the right. SAP has also reserved the right to make compatibility scope functionality technically unavailable in future releases, though it hasn’t said it will. Either way, “we’ll deal with it later” has a date attached to it.
Four years sounds comfortable. It isn’t. A transportation move touches order to cash, warehouse execution, finance, EDI, and every carrier you work with. In our experience these programmes run anywhere from a few months to well over a year, depending on custom code volume, how many integration points you have, and whether this sits inside a wider S/4HANA conversion. Whatever the number turns out to be for you, budgeting, design, testing, training and a quiet cutover window all sit on top of it.
The second reason is that LE-TRA has run out of room. It was built for a simpler kind of shipping. Plan a load, assign a carrier, calculate a cost, print the paperwork. That still works, but it doesn’t stretch.
Companies move because they want things LE-TRA was never designed for:
- Multi-leg and multi-modal journeys treated as one plan
- Automatic carrier selection and tendering, instead of a planner calling round
- Optimisation across loads rather than one shipment at a time
- Carrier collaboration, so the carrier updates the status instead of your team chasing it
- Freight charges that reflect real rate agreements, including accessorials and fuel
If your planners live in spreadsheets alongside SAP, that’s the gap talking.
Check note 2269324 for the compatibility scope matrix and 2270199 for the LE-TRA simplification item. Both are worth reading before you build a business case for SAP LE-TRA migration or LE-TRA replacement.
-
What Changes After Migration
The physical work doesn’t change. Trucks still arrive, goods still move, carriers still invoice you. What changes is how SAP thinks about all of it.
The documents change. In LE-TRA you have a shipment document and a shipment cost document. In TM you have freight units, freight orders, and a freight settlement document that flows into a service entry sheet and then to invoice verification. It is a different chain, and your finance team needs to understand it before go-live.
Costing changes the most. LE-TRA calculates freight cost with pricing condition records, the same technique as sales pricing. TM uses charge management: rate tables, calculation sheets, and freight agreements tied to the carrier. It is a stronger model, and it is genuinely better at handling real contracts. It also does not map across one for one. This is the single biggest source of surprise on these projects, and section 5 deals with it properly.
Planning changes. Instead of building shipments one at a time, planners work in the transportation cockpit, where they can see demand, build loads, and let the system propose options. For teams used to VT01N this is a real shift in daily habit.
Master data moves around. Carriers move to the SAP Business Partner model with transportation roles, which is not a record-for-record conversion of your old service agents. Transportation zones and lanes get rebuilt in TM’s own structures. Routes are an interesting case, because LE-TRA routes were pulled out of compatibility scope and can still be used for scheduling in sales orders, deliveries and stock transport orders after 2030.
What stays the same. You move the same goods, through the same carriers, along the same lanes. Nobody is rebuilding your supply chain. What changes is how SAP represents and connects it all, and that part changes more than people expect. Historical LE-TRA documents are normally kept where they are for reporting and audit rather than converted into TM documents.
For companies evaluating LE-TRA vs SAP TM, the important point is that this is not simply a technical replacement. It changes transportation planning, freight costing, settlement, master data and execution processes.
-
What Can Go Wrong During Migration?
Here is what actually causes trouble, based on where these projects tend to slip.
Freight costs don’t match. You run the same lane in TM and get a different number than LE-TRA gave you. Sometimes TM is right and the old condition records were quietly wrong for years. Either way, finance sees a variance and confidence drops fast. There is a way to get ahead of this, and it’s the parallel charge comparison described in section 5. Teams that run it during design do fine. Teams that meet the problem for the first time in UAT lose weeks.
Custom code nobody owns. Most LE-TRA installations have Z-programs sitting on the shipment tables, plus user exits, custom output, and reports built for one manager who left in 2019. None of it moves. Somebody has to go through it, decide what is still needed, and rebuild or retire the rest. Run the ATC check using the piece list in the simplification note early, so you know the size of this before you commit to a date. This is a key part of LE-TRA migration consulting and migration readiness.
Assuming open shipments can be lifted and shifted. Don’t count on it. In most migration scenarios, open transportation business needs a deliberate cutover strategy rather than a straightforward document conversion. That’s a design decision to make early, not a technical detail to hand to the build team.
Master data gets underestimated. Carriers, lanes, zones, rate agreements, equipment types. It is not glamorous work, and it is almost always bigger than the first estimate. Strong LE-TRA migration services should identify these requirements early.
EDI and output break quietly. Carrier messages, labels, transport documents, ASNs. Different documents mean different output determination. This tends to surface late and annoy carriers.
Integration points get missed. If you run EWM, yard logistics, or handling unit management, those touchpoints need testing in their own right.
People don’t come with you. Planners who have used the same transaction for a decade will not enjoy the transportation cockpit in week one. Skip training and your go-live looks like a system failure when it’s actually an adoption problem.
Teams try to rebuild LE-TRA inside TM. This is the quiet killer. It’s tempting to make the new system behave exactly like the old one. You end up paying for TM and getting LE-TRA back, with more complexity.
-
How Should the Migration Be Approached?
Decide the shape first
Two questions come before everything else.
Is this part of a wider S/4HANA move, or a standalone functional project? Bundling it into a bigger conversion saves cutover effort but adds risk to an already large programme. Doing it on its own is cleaner but means a second cutover.
Do you need embedded TM basic, or the advanced version? Basic covers many of the core transportation processes you handled in LE-TRA. Advanced brings optimisation, tendering, carrier collaboration and complex charge scenarios. Confirm the available scope and the licensing position against your own S/4HANA deployment and contract before you design around either, because this varies by customer. Then answer the functional question honestly against your real process rather than your wish list.
This decision should form part of your SAP TM migration strategy and LE-TRA migration roadmap, rather than being left until the implementation phase.
Then decide scope: what moves and what stays
This is the part most plans skim, and it’s where budgets are won or lost.
Migrate:
- Carrier master data, cleaned up first
- Lanes, zones and the geography you actually use
- Rate agreements and charge structures, rebuilt in TM’s model rather than copied
- Custom logic that supports a live business rule you can name
- Open transportation business as of your cutover date, handled as described below
Leave behind:
- Closed shipments and settled costs. Keep them readable in the old tables for reporting and audit. Do not try to convert history.
- Condition records for lanes and carriers you stopped using years ago
- Custom reports nobody has run in eighteen months. Check the usage statistics before anyone argues.
- Workarounds that existed only because LE-TRA couldn’t do something TM does natively
- Route definitions used purely for transportation planning, once TM takes that over
The rule of thumb: if you can’t name the person who needs it, it doesn’t move.
Sequence the work
A structure that holds up in practice:
- Assess. Custom code scan, process inventory, data volumes, integration map. Output is a scope you can price. A formal LE-TRA migration assessment can make this first stage much clearer.
- Design. Target process, org structure, charge model, integration design. Get finance in the room for the charge model.
- Build and configure. Iteratively, with business users seeing it early.
- Test. Covered in the next section, because it deserves its own.
- Cut over. Pick a low-volume window. Close open shipments in LE-TRA where you can, and let the tail run out under the old process. New business starts in TM from a defined date and time. Keep LE-TRA available read-only for reporting.
- Hypercare. Four to six weeks with planners supported daily and a defined route for problems.
Write the rollback plan even though you expect not to use it. Know what “we stop and go back” means, who decides, and by when. On a transportation cutover that decision window is short, usually a matter of hours.
-
How Do You Know the Migration Actually Works?
“It worked in testing” is not the same as “it works.”
Run a parallel charge comparison
If you take one thing from this article, take this. It is the test that decides whether finance trusts the new system, and it is the test most often left until too late.
Take a meaningful set of historical shipments across your main lanes, carriers and modes. Run them through TM charge management. Compare the result against what LE-TRA actually charged. Then explain every difference.
Agree the tolerance before you start, and agree who signs it off. Some differences will be TM being correct where the old condition records were wrong. Those are wins for you, but only if you can prove which is which before anyone panics about a variance.
Do this during design, not at UAT. Run early, it shapes your charge model while there is still time to change it. Run late, it becomes a defect list with a go-live date bearing down on it. The difference between those two projects is enormous, and it comes down to when somebody decided to run this comparison.
For an SAP TM migration assessment, this type of freight cost validation can also help identify problems before implementation costs escalate.
Test end to end, not module by module. Sales order to delivery to freight unit to freight order to settlement to service entry sheet to invoice. Include a return, a partial delivery, a cancellation, and a shipment where the carrier changes after planning. The awkward cases are where the gaps live.
Regression test what you didn’t touch. Order to cash, warehouse processes, ATP, billing. Transportation sits in the middle of a lot of things.
Test volume. Run a realistic day of demand through planning. Optimiser runtime on twelve test loads tells you nothing about month-end.
Test the outside world. Real carrier EDI, real transport documents, real labels. Involve at least one carrier before go-live.
Let planners test it. Not consultants clicking through a script. Give your own planners a normal day’s work and watch where they hesitate. Their hesitation is your training plan.
Measure after go-live. Agree the numbers in advance: freight cost variance against baseline, planning time per load, settlement blocks, on-time delivery, invoice matching rate. Check them at thirty and ninety days. If nobody defined success upfront, everyone will judge the project on the loudest complaint.
-
When Do You Need Migration Expertise?
Not every company needs outside help, and it’s worth being straight about that.
You can probably handle it internally if your LE-TRA setup is close to standard, custom code is limited and documented, your charge structures are simple, you have TM skills on the team already, and you have people who can be freed up rather than squeezed in around their day job.
You should bring in an LE-TRA migration consultant if any of these are true:
- Nobody currently on staff can explain what the custom code does
- Your freight charges involve complex agreements, accessorials, multiple modes or cross-border rules
- Transportation is tied into EWM, yard logistics or a third-party TMS
- You’ve never run embedded TM before, only classic transportation
- This sits inside a wider S/4HANA programme that already has a fixed date
- Your team can do it, but only by dropping something else that matters
What to ask any partner
These questions apply to every SAP TM migration partner you talk to, including us. If a partner is uncomfortable with them, that tells you something.
- Have you done embedded TM in S/4HANA specifically, or only standalone TM? They are not the same project.
- How do you approach charge calculation validation? Ask for the actual method, not a reassurance.
- Who owns custom code remediation, and how is it priced? Vague answers here become change requests later.
- What does your cutover plan look like, and what triggers a rollback?
- How do you handle planner training and adoption?
- Tell me about a migration that went badly. What happened, and what did you change afterwards? Anyone who has done enough of these has one. Anyone who says otherwise hasn’t.
- What will you need from my team, and how many hours a week?
The last one gets skipped most often, and it’s the one that breaks timelines.
-
SCM Champs: Helping You Plan, Execute and Validate the Migration
We’re an SAP supply chain consultancy, and LE-TRA to SAP TM migration transitions are a core part of what we do.
Assess. We start by finding out what you actually have. Custom code scan against the LE-TRA piece list, a map of your real transportation processes as opposed to the documented ones, charge structure review, integration inventory, and data volumes. You get a scope and a realistic estimate. If the honest answer is that your setup is simple enough to handle in-house, we’ll say so.
Plan. Target design, basic versus advanced TM recommendation with the reasoning shown, scope decisions on what moves and what stays, cutover approach, and a phased timeline that works around your business calendar rather than ignoring it.
Execute. Configuration, custom code remediation, master data build, integration work, and output and EDI setup. Your team stays involved throughout, because a system nobody internal understands is a problem you inherit on day one.
Validate. The parallel charge comparison described above, run against your own historical shipments with every variance explained line by line, and run during design rather than at the end. Alongside that: end-to-end and regression testing, volume testing, planner-led UAT, cutover support and hypercare.
As an LE-TRA migration consulting company, we’d rather tell you the difficult thing early than discover it in testing. Most of the trouble on these projects comes from decisions made in the first month, not the last.
Start with an assessment
If 2030 is on your risk register and you don’t yet have a plan, the most useful next step is an LE-TRA migration assessment. We look at your custom code, your charge structures and your integration points, and give you a clear picture of the effort involved. Where the data allows, we run a sample charge comparison as part of it, so you see the freight cost question early instead of meeting it in testing.
No obligation to continue with us afterwards. Some companies take the assessment and run the project themselves, and that’s a fine outcome. What matters is that you go into it knowing what you’re dealing with.
Talk to SCM Champs about our LE-TRA migration services and assessment. As an LE-TRA migration services company working across SAP supply chain, we can tell you within a few weeks what your migration really looks like, and how long you’ve realistically got.
Deadlines and compatibility scope details are current as of publication. Check SAP notes 2269324 and 2270199 for the latest position on your release.