How SAP Transportation Management (embedded in S/4HANA) connects to SAP S/4HANA
Embedded first-party component
TM runs in the S/4HANA system and creates freight units from sales and stock transfer orders, then plans them into freight orders. No separate integration is needed between ERP and TM.
SAP Business Network for Logistics
Carriers receive tenders and send back status through the network, which is a cloud connection even when S/4HANA is on-prem.
What data moves
| From | To | Data | When |
|---|---|---|---|
| S/4HANA sales and delivery documents | SAP TM | Freight units from orders and deliveries | Order or delivery created |
| SAP TM | Carrier via Business Network | Freight tenders and orders | Planner or rule tenders |
| Carrier | SAP TM | Acceptance, status events | Carrier response |
| SAP TM | S/4HANA finance | Freight settlement documents and costs | Freight order completed |
Setting it up
- 1Confirm licensing and scopeCheck what your S/4HANA license includes for embedded TM and which functions need extra licensing.
- 2Define the transportation networkSet up locations, transportation zones, lanes and means of transport.
- 3Load carrier master and agreementsCreate carriers, freight agreements and rate tables.
- 4Set up planning profilesDefine profiles and strategies for consolidation and carrier selection.
- 5Configure freight unit creationControl which order types become freight units and how.
- 6Enable carrier collaborationConnect to SAP Business Network for Logistics for tendering.
- 7Configure settlementSet calculation sheets and accrual posting with finance.
What usually breaks
- !Incomplete location and zone master data blocks planning.
- !Rate tables with gaps lead to no carrier found for some lanes.
- !Weights and volumes missing on materials give unrealistic plans.
- !Freight settlement differs from carrier invoices without tolerance rules.
- !Standard planning needs tuning for your lane patterns, otherwise planners override constantly.
A private AI layer across both systems
No-carrier-found diagnosis
A private assistant reads freight unit, lane and agreement data and explains why planning found no carrier, drafting the missing rate or zone for approval.
Invoice versus settlement reconciliation
Compare carrier invoices with TM settlement and accruals to flag differences by lane.
Freight questions in plain language
Ask which freight orders are untendered or late, with the query shown and SAP roles respected.
When something else fits better
- Basic shipping with a parcel add-on covers companies without real freight planning needs.
- A specialist TMS outside SAP can fit multi-ERP shippers.
- Standalone SAP TM gives more options if you need it before moving fully to S/4HANA.
Frequently asked questions
Is embedded TM the same as standalone TM?
Embedded TM runs inside S/4HANA with a reduced but practical scope, while standalone runs on a separate system. Check SAP's scope matrix to see which functions your needs require.
Does it work with on-prem S/4HANA?
Embedded TM is part of S/4HANA, but carrier collaboration via SAP Business Network for Logistics is a cloud service. Plan connectivity accordingly.
Does it handle parcels?
It is built for freight planning and tendering. For label printing and parcel rating, a dedicated shipping add-on is usually simpler.
Pairing documented at learning.sap.com/learning-journeys/applying-supply-chain-execution-in-sap-s-4han . SAP Transportation Management (embedded in S/4HANA) is a product of SAP; Netray is independent and not affiliated with either vendor.