TRANSPORTATION EXECUTION
Transportation Management
Learn how Basic TM turns delivery-based transportation demand into Freight Units, Freight Orders, execution evidence, controlled freight cost, settlement, and invoice/FI evidence.
TM LEARNING PATH
Build from transport understanding to supportable operations
Follow six connected levels across one Basic TM story: Demand, Plan, Execute, Cost, and Settle.
How does Transportation Management work?
Understand the Basic TM lifecycle: demand becomes a plan, the plan becomes execution evidence, and execution becomes freight cost and settlement.
Start with the transportation modelTM 202 · OBJECT MODELHow do TM transport objects fit together?
Separate delivery-based demand, DTR, FUBR, Freight Units, Freight Orders, execution events, FSD, PO/SES, supplier invoice, and FI evidence.
Open object anatomyHow does business demand enter Basic TM?
Basic TM can only plan what the business process has made transportation-relevant. Sales Orders and Purchase Orders remain upstream context; the Basic TM spine begins when delivery-based or transportation demand reaches TM with complete, traceable data.
Open topicTM 202 · QUALIFYHow does demand become plannable freight?
Basic TM represents transportation-relevant demand and applies freight-unit-building rules to create planning units. FUBR stays here as the rule that turns demand into Freight Units.
Open topicTM 202 · ENABLEWhat master data makes a Basic TM plan possible?
A planning profile cannot repair incomplete master data. Basic TM needs trustworthy locations, zones, time, distance, resources, equipment, carriers, freight agreements, and rates before it can make a feasible plan.
Open topicTM 202 · PLANHow does Basic TM create a feasible transportation plan?
Planning assigns compatible Freight Units to Freight Orders. A good Basic TM result makes route, schedule, resource, equipment, capacity, stops, and assigned freight visible and explainable.
Open topicTM 202 · MOVEHow do transport and warehouse execution stay aligned?
TM owns the transportation plan and Freight Order execution view. Delivery and warehouse processes own picking, packing, staging, loading, receipt, and inventory execution. Integration must preserve one operational story across those responsibilities.
Open topicTM 202 · SETTLEHow does freight cost reach finance?
Basic TM calculates expected transportation charges from freight agreements and rates. A Freight Settlement Document represents carrier cost and supports purchasing, service entry, accrual, invoice verification, and FI integration.
Open topicHow does the complete Basic TM process hang together?
See outbound and inbound delivery-based demand converge into one planning, execution, costing, and freight-settlement model.
Open the shared mapHow does Basic TM work outbound?
Follow Sales Order context through outbound delivery, DTR, Freight Unit, Freight Order, PGI, FSD, PO/SES, supplier invoice, and FI.
Open outbound caseTM 303B · INBOUND DEPTHHow does Basic TM work inbound?
Follow Purchase Order context through inbound delivery, DTR, Freight Unit, Freight Order, GR, FSD, PO/SES, supplier invoice, and FI.
Open inbound caseHow do you design and prove Basic TM?
Configure delivery relevance, FUBR, master data, planning profiles, Freight Orders, execution status, charges, FSD, and MM/FI integration.
Open solution workbenchTM 505 · LIVE PROJECTHow does a Basic TM implementation unfold?
Prove delivery-based scope through design, build, testing, cutover, go-live, and stabilization.
Enter the projectTM 606 · PRODUCTION SUPPORTHow do you support Basic TM in production?
Find where demand, planning, Freight Order execution, costing, settlement, purchasing, or invoice/FI evidence first diverged.
Open support method