The SAP Transportation Management organizational model describes which organizational units perform transportation planning, purchasing and charge-related responsibilities. Company organizations, purchasing organizations and groups, and—in relevant TM scenarios—planning-and-execution units help determine responsibility; their availability and setup depend on the S/4HANA edition and business model.
Why transportation needs its own responsibility model
A factory may own the product but contract a third-party haulier for delivery. One department plans routes, another negotiates freight contracts, warehouse staff load the vehicle, and finance checks the invoice. The TM organizational model helps connect documents and responsibilities to these operating teams.
It should not be confused with the physical transport network. A transportation zone or location describes where goods travel, not which organization is responsible for buying the freight service. Nor are TM organizational units necessarily identical to their same-named counterparts in Materials Management.
Company and purchasing responsibilities
In SAP S/4HANA Cloud Public Edition TM, SAP Learning describes company organization, purchasing organization and purchasing group. The company organization relates to the ERP company code for invoicing and charging. The purchasing organization is responsible for negotiating freight agreements and is assigned for freight-charge calculation and settlement.
The purchasing group works under the purchasing organization. Cross-company purchasing requires explicit attention to the company code selected for charge processing. Therefore a shared transport procurement team does not automatically mean one legal entity owns every freight expense.
Planning and execution: distinguish the scenario
SAP's broader Transportation Management organizational documentation also includes planning and execution organizations and groups, particularly relevant to logistics service providers. Those structures provide organizational ownership for planning and executing transport services and can support task assignment.
Do not copy a diagram from one TM deployment type into another without checking the release and edition. A shipper using embedded TM in Public Cloud may not need or expose the entire logistics-service-provider model described for a different deployment.
Example and design questions
Imagine two plants shipping through a central transport desk. Procurement secures a carrier agreement. The planning team consolidates shipments; warehouse staff execute loading; accounting attributes charges to the correct company. The project team must document which organization owns each freight agreement, freight order, carrier invoice and exception.
Ask which legal company incurs the charge, which team negotiates carrier rates, who plans and approves freight, and which roles can change a document. The answer determines organizational mappings, authorizations and reconciliation tests.
Related Knowledge
Road freight basics · Ocean freight basics · TM and EWM integration. Return to SAP TM.