LE-TRA is going away. Your freight processes don’t have to.
If your transportation processes still run on LE-TRA, you already know the clock is ticking. SAP has closed the book on shipment-era logistics: LE-TRA is not the strategic solution in S/4HANA, and every upgrade conversation eventually lands on the same question. What happens to our shipments, our carrier communication, and our freight costing when we move?
The honest answer: they don’t move by themselves. LE-TRA’s shipment documents, output-based carrier messaging, and CO-based freight costing all have successors in SAP Transportation Management, but they are not one-to-one copies. Shipments become Freight Orders. Tendering becomes a subcontracting process with its own master data. Freight costing becomes charge calculation against agreements, settled through Freight Settlement Documents.
That redesign is where migrations succeed or stall. Teams that treat it as a technical lift-and-shift discover mid-project that their rate structures don’t fit the new charge model, or that a carrier EDI flow nobody documented is quietly holding the network together.
What we recommend to every shipper still on LE-TRA: first, inventory what you actually use. Most LE-TRA installations use a fraction of what was configured in 2008. Second, map each active process to its TM equivalent before anyone opens a project plan, and let the gaps size the project. Third, migrate master data early, because rates, lanes, and carrier data take longer to clean than anyone budgets for. And finally, run the settlement chain end to end in testing with real invoices, not sample data.
We have done this conversion enough times to know where it bites. If you want a second set of eyes on your LE-TRA exit plan, or you need one built from scratch, that is exactly the kind of scoped, fixed engagement we run.
