SAP's ECC End of Life Forces a 2027 TMS Decision
SAP's ECC and TM 9.6 support ends 31 Dec 2027. What European shippers running SAP transport modules must decide, and by when.
SAP has confirmed, again, that mainstream maintenance for SAP ECC 6.0 and the legacy standalone transport stack built on it ends 31 December 2027. That includes LE-TRA, the shipping module embedded in thousands of European ECC installations, and standalone SAP TM 9.6 running on NetWeaver. Leogistics, which has tracked the LE-TRA transition for years, confirmed SAP announced the end of support for LE-TRA for the 31st of December 2027, the exact same date as ECC itself. If your freight planning, tendering, and settlement still run through one of these tools, this is no longer a distant IT roadmap item. It's a dated, confirmed deadline with a transport-specific decision attached to it.
This isn't just an ERP story
If you're running EHP 0 to 5, you're already past the first cliff: Enhancement Packages 0 through 5 already lost mainstream maintenance at the end of 2025. For the larger group on EHP 6 to 8, the clock runs to the end of 2027. After that, mainstream maintenance stops covering security patches and legal updates, the kind of updates that keep your transport module current with things like CBAM reporting, ETS2 fuel surcharge rules, or eCMR formats. You can buy your way into extended maintenance, but SAP has been blunt about where that leads: as Incorta puts it, SAP leadership has repeatedly said the 2025 and 2027 end of mainstream maintenance dates for ECC 6 are not changing.
The dates that actually matter
| Date | What happens |
|---|---|
| 31 Dec 2025 | ECC EHP 0–5 mainstream maintenance already ended |
| 31 Dec 2027 | ECC EHP 6–8 and standalone SAP TM 9.6 / LE-TRA mainstream maintenance ends |
| 2028–2030 | Extended maintenance available at added cost, no new transport features |
| Through 2033 | Limited RISE-only transition option for some customers |
Extended maintenance isn't a reprieve, it's a surcharge. Incorta notes that companies can buy optional extended maintenance through the end of 2030, which adds three years of support at two percentage points on top of the existing maintenance fee, and a limited RISE-only path stretches to 2033. Every one of these roads still ends at S/4HANA.
Why "we'll deal with it later" stopped working
Here's the part that catches transport teams off guard: ERP migrations are slow, and transport is rarely first in the queue. SAVIC's own migration data shows a typical ECC to S/4HANA migration takes 12–24 months for mid-complexity landscapes and 18–36 months for large enterprises with significant custom code. If your SI hasn't scoped transport yet, you're looking at a program that might not touch LE-TRA or TM until 2028 or later, well past the deadline. And the resourcing isn't getting easier. SAVIC also flags that the market capacity for qualified SAP S/4HANA migration resources is finite, which means the companies that wait aren't just racing a date, they're racing each other for the same consultants.
Replatform inside S/4HANA, or decouple transport now
This is the actual decision, and it has two honest paths.
- Replatform. Move transport into S/4HANA TM, either Basic Shipping (the direct LE-TRA replacement) or Advanced/Professional TM for optimizer-driven planning. This keeps you inside SAP's roadmap but ties your transport go-live to the entire ERP program's timeline, phasing, and budget fights.
- Decouple. Move transport execution onto a standalone TMS that connects to ECC today and to S/4HANA later, independent of when finance, MM, or SD go live. This gives transport its own go-live date instead of waiting in line.
European shippers evaluating that second path typically shortlist from a similar pool: MercuryGate, Descartes, Blue Yonder, Oracle TM, Manhattan Active, and Alpega. Cargoson sits in that same category as a carrier-connectivity-first TMS designed to sit on top of SAP regardless of where you are in the ECC-to-S/4 timeline, which matters if your ERP program is phased over two or three years. For smaller-volume sites inside a larger network, multi-carrier parcel platforms like Sendcloud or nShift sometimes fill the gap, but they're a different conversation from core freight tendering and settlement.
What to do this quarter
- Map exactly where LE-TRA or standalone TM 9.6 sits in your transport stack, and on which EHP you're running.
- Get your SI to confirm in writing whether transport is in wave one of the S/4HANA program, or pushed to a later phase.
- Price extended maintenance through 2030 as a bridge, not a plan.
- Decide, independently of the ERP timeline, whether carrier connectivity and compliance reporting can afford to wait for a multi-year program.
The 2027 date isn't moving. The decision about where your transport operations live when it arrives is still yours to make, this quarter gives you the most options. Wait until next year and the choice gets made for you, by whichever consultants and vendor slots are still open.