SAP Transportation Management is one of the most customisation-intensive modules in the SAP portfolio. Logistics companies, retailers, and manufacturers have spent years building freight order management processes, carrier integration frameworks, and track-and-trace workflows on SAP TM 9.x — often with thousands of ABAP enhancements, custom condition tables, and MBC (Multi-Backend Connectivity) configurations. SAP knows this. It is precisely why SAP uses TM support renewal as one of its most effective S/4HANA migration levers.
The SAP pitch — "SAP TM 9.x is end of mainstream maintenance; your only strategic path is SAP TM on S/4HANA" — omits the cost of that path. S/4HANA TM migration for a complex logistics estate typically runs £3M–£12M in professional services, 24–42 months of parallel operation, and the near-certain loss of every ABAP-based TM customisation built since go-live. Third-party support (TPS) breaks this coercion: SAP TM 9.x and TM on HANA continue under full supported cover at 60–65% less than SAP Software and Support (SnS) fees, with no migration deadline imposed by your support contract.
Running SAP? See how much you can save before your next renewal. Free analysis, no commitment.
500+ enterprise clients · Est. 2016 · 15-min response · No commitment
SAP Transportation Management on S/4HANA is not a technical upgrade of TM 9.x — it is a functional replacement. SAP S/4HANA TM uses an entirely different freight order model, and custom ABAP enhancements to TM 9.x (freight order determination, carrier selection, capacity management) require complete re-engineering. Customers typically find 60–80% of TM customisations are not migrable without redesign.
SAP's TM Maintenance Timeline — What Is Actually Ending
SAP's maintenance lifecycle communications for Transportation Management are deliberately ambiguous. "End of mainstream maintenance" does not mean the software stops functioning; it means SAP will no longer provide general enhancements, new country versions, or legal change packages for free under standard SnS. The software continues to operate. Third-party support covers the gap — providing incident resolution, security advisory, and critical fixes for TM environments without the S/4HANA migration ultimatum.
The same mechanics that apply to SAP ECC TPS and SAP HANA migration cost analysis apply to TM: SAP's perpetual licence grants you the right to use the software indefinitely. The maintenance contract is separate from the licence. You can cancel maintenance and engage third-party support without affecting your right to use SAP TM.
SAP TM Version Matrix — TPS Eligibility
| SAP TM Version | Platform | SAP Mainstream Maintenance | SAP Status | TPS Available |
|---|---|---|---|---|
| SAP TM 9.6 | SAP ECC / NetWeaver | Ended Dec 2027 (extended) | Extended Maintenance | ✓ Full TPS |
| SAP TM 9.5 | SAP ECC / NetWeaver | Ended Dec 2025 | Customer-specific maintenance | ✓ Full TPS |
| SAP TM 9.4 | SAP ECC / NetWeaver | Ended Dec 2022 | End of Mainstream | ✓ Full TPS |
| SAP TM 9.3 | SAP ECC / NetWeaver | Ended Dec 2021 | End of Mainstream | ✓ Full TPS |
| SAP TM on S/4HANA 2021/2022 | SAP HANA | 2026 (planned) | Current SAP support | ✓ TPS available |
| SAP TM on HANA (standalone) | SAP HANA | Aligned to HANA lifecycle | HANA lifecycle | ✓ Full TPS |
| SAP Extended Warehouse Management (EWM) — integrated | ECC / S/4HANA | Aligned to TM lifecycle | Bundled lifecycle | ✓ TPS (with TM) |
What TPS Covers for SAP Transportation Management
SAP TM has an unusually deep customisation footprint. TPS providers with genuine SAP TM experience cover the full stack — not just the standard application layer:
Freight Order Management
- Freight order (FO) and freight booking (FB) lifecycle management — creation, planning, execution, settlement
- Freight order determination (FOD) rule engine — ABAP-based custom determination and route optimisation logic
- Carrier selection and tendering process — automated and manual workflows, capacity management
- Dangerous goods (DG) handling and ADR/IMDG/IATA compliance logic
- Subcontracting and forwarding order management
Planning and Optimisation
- Optimizer integration — SAP Vehicle Scheduling and Routing (VSR) optimizer, Planning Service
- Load planning and packing logic — capacity utilisation models, ULD management
- Multi-modal transport chain planning (road, rail, ocean, air)
- Continuous move and backhaul optimisation logic
Track and Trace / Visibility
- Event management integration (SAP EM) and expected/unexpected event logic
- Track-and-trace reporting and delay notification workflows
- Third-party visibility platform integration (custom RFC/API layers)
Integration Layer
- SAP TM–ECC ERP integration (OTR, SD, MM, WM, FI interface)
- EDI message handling — EDIFACT, X12, custom IDoc extensions for carrier communication
- Multi-Backend Connectivity (MBC) configuration and troubleshooting
- Customs and trade compliance integration (SAP GTS or third-party customs systems)
Freight Settlement and Finance
- Freight charge calculation — condition technique, charge management, carrier invoice verification
- Automatic accruals and service agent freight settlement
- Cost distribution to cost objects (FI-CO integration)
Sector-Specific SAP TM Considerations
Logistics and 3PL Providers
Third-party logistics (3PL) providers and logistics operators represent the highest-concentration SAP TM user base. Their TM estates are typically characterised by extremely high ABAP customisation density — carrier onboarding logic, spot tendering workflows, customer-specific reporting, and track-and-trace visibility portals built as Z-code on top of standard SAP TM. These customisations represent years of operational knowledge that cannot be migrated to SAP TM on S/4HANA without a complete redesign engagement. TPS preserves this investment. See the case studies for logistics sector TPS saving examples.
Retailers with Complex Inbound Supply Chains
Large retailers using SAP TM for inbound logistics from Asia-Pacific manufacturing supply chains — ocean container management, port handling, deconsolidation at regional DCs — have built highly specific SAP TM configurations around their supply chain footprint. These configurations are in the critical path for inventory replenishment. The risk profile for S/4HANA TM migration is extremely high. TPS provides continuity of the existing operational platform while strategic planning decisions are made without a vendor-imposed deadline. See the retail sector TPS page for more.
Manufacturers with Outbound Distribution Networks
Discrete and process manufacturers using SAP TM to manage outbound finished goods distribution — truck loading, carrier selection, proof of delivery, freight cost accrual — typically have SAP TM tightly integrated with SAP WM/EWM and SAP SD. The integration density makes S/4HANA migration particularly complex. For manufacturing sector TPS analysis, see the manufacturing industry page.
SAP TM and EWM Combined Estates
Many SAP TM customers run SAP Extended Warehouse Management (EWM) as the warehouse management layer alongside TM for transportation. Both modules can be placed on third-party support simultaneously, providing a unified support envelope across the full warehouse-to-transport stack. The SAP EWM TPS page covers the EWM-specific considerations.
Four-Profile Cost Model — SAP TM TPS Saving
SAP SnS is calculated at 22% of current licence value. TPS is typically 8% of current licence value, producing a 60–65% net saving.
Moving SAP TM to Third-Party Support
The SAP TM TPS transition follows the same structure as any SAP ECC TPS engagement. Critical path items:
- TM customisation inventory — Document Z-code enhancements, user exits, BADIs, and custom condition tables. This inventory forms the TPS provider's coverage baseline.
- Integration documentation — Capture MBC configurations, EDI message mappings, and third-party system interfaces. TPS provider needs this to establish full support scope.
- SAP SnS cancellation — 90-day notice (SAP Enterprise Agreement terms) or contract-specific terms. Confirm cancellation mechanics with your SAP contract.
- TPS onboarding — TPS provider performs environment discovery, installs monitoring, ingests support history. Typically 15–25 working days for a complex TM estate.
- SAP indirect access assessment — Confirm no indirect access exposure from carrier portal or visibility platform integrations. See the SAP Audit Defence Playbook for indirect access analysis.
SAP Enterprise Agreement customers must provide 90 days' notice to cancel SnS on any product. Non-EA customers may have different contractual terms. Review your SAP contract before initiating cancellation. The cancellation right is unambiguous — SAP cannot prevent you from cancelling maintenance on perpetually licensed software.
Frequently Asked Questions
Can TPS cover SAP TM optimizer integration (VSR)?
Yes. SAP Transportation Management optimizer integration — including the VSR optimizer and Planning Service — is within TPS scope. TPS providers maintain expertise across the full TM planning and optimisation stack.
What happens to EDI carrier integrations under TPS?
EDI message processing, EDIFACT/X12 carrier interfaces, and custom IDoc extensions remain fully operational under TPS. Any carrier-side format changes are handled as incident requests within your TPS SLA.
Does TPS cover SAP TM alongside SAP ECC support?
Yes. TPS can cover SAP TM and SAP ECC simultaneously under a single support engagement. This is the most common configuration for customers with TM integrated into their ECC landscape. See the SAP ECC TPS guide for ECC-specific coverage details.
Can we run SAP TM on TPS without migrating to S/4HANA?
Yes. Your SAP TM licence is perpetual. S/4HANA migration is a SAP commercial preference, not a legal requirement. TPS customers routinely run SAP TM 9.x for 7–10 additional years beyond SAP's maintenance horizon while strategic platform decisions are made without vendor pressure.