TM 303A · OUTBOUND CASE DEPTH
How does Basic TM work outbound?
Follow Sales Order context into Outbound Delivery, then through the shared Basic TM model without teaching direct Sales Order transportation planning as the course spine.
OUTBOUND HAND-OFFS
Follow the records and their owners
Use the shared 303 map for orientation, then read this branch as a business and operating narrative.
- 01SALES CONTEXTCreate upstream demand
A Sales Order defines the customer promise, but this Basic TM path plans the outbound delivery-based transportation demand.
- 02OUTBOUND DELIVERYCreate transportation-relevant delivery demand
The delivery defines goods, quantity, ship-from, ship-to, requested dates, and transportation relevance.
- 03TM DEMANDCreate DTR / transportation demand
The configured delivery trigger supplies transportation demand and preserves the source reference.
- 04FUBR / FREIGHT UNITBuild planning units
FUBR creates durable Freight Units with quantities, locations, dates, compatibility, and source references.
- 05BASIC PLANNINGCreate the Freight Order
Assign route, equipment, schedule, capacity, stops, resource, and carrier field where applicable.
- 06EXECUTIONPick, pack, load, and post goods issue
Warehouse execution proves readiness and inventory departure while TM tracks planned and actual milestones.
- 07FREIGHT COSTCalculate and settle freight
Create expected charges and the Freight Settlement Document.
- 08MM / FI / APVerify the supplier invoice
Reconcile FSD, PO/SES evidence, supplier invoice, accrual, and FI/AP posting.
See how delivery-triggered relevance joins the common Basic TM design.