SAP Transportation Management plans and manages transportation demand, freight orders and carrier execution; SAP Extended Warehouse Management coordinates warehouse processes such as staging, loading and unloading. In an integrated S/4HANA landscape, logistics documents and execution statuses connect the two areas, but configuration and deployment choices determine the exact handoffs.
Where the systems meet
A sales or stock-transfer process may create an outbound delivery and corresponding transport demand. Transportation planners group demand into suitable freight units and freight orders, select capacity and plan stops. Warehouse teams need relevant transport information to stage, pick, pack and load the goods against delivery execution.
The integration is not simply one application sending a completed order to another. A truck's planned arrival, warehouse readiness and confirmed loading can change independently. The business must decide which event, document and system is authoritative for each status.
Illustrative outbound shipment
A manufacturer has two customer deliveries leaving one distribution center on the same vehicle. SAP TM may combine transportation demand under one freight order. EWM organizes warehouse tasks and loading at the warehouse. A shipping or receiving process coordinates delivery and freight-order information so that physical execution matches the plan.
If the truck arrives but the second order is not packed, transport has a capacity and timing problem, while the warehouse has an execution exception. The response requires both teams; updating a transport status without an actual loading confirmation is not sufficient evidence of a shipped quantity.
Integration boundaries and product variants
SAP Learning describes Advanced Shipping and Receiving as an integration option for freight, warehouse and inventory-managed processes. It supports coordination of loading and unloading, including scenarios with multiple stops and mixed warehouse processes. The exact features, objects and integration mode differ with S/4HANA release, embedded or decentralized EWM, and process setup.
Avoid claiming that every SAP TM landscape uses one universal document flow. In design workshops ask which delivery, freight order, warehouse task, transportation unit and event is in scope, where they are maintained, and how exceptions are synchronized.
Controls consultants should test
Test partial loading, short picks, carrier reassignment, late arrivals, cancellation, failed status exchange and proof of departure. Confirm the agreed ownership of a quantity correction, a delivery change and a freight-order update before go-live.
Operational reconciliation should answer: What was planned to move? What was physically loaded? Which freight document represents the truck? What was confirmed to the customer and carrier? The integration is successful when these answers agree, not merely when technical messages complete.
Related Knowledge
Road freight basics · Air freight basics · EWM warehouse tasks · EWM warehouse orders. Return to SAP TM.