TM 303B · INBOUND CASE DEPTH
How does Basic TM work inbound?
Follow Purchase Order context into Inbound Delivery, then through the shared Basic TM planning and settlement engine without teaching direct Purchase Order transportation planning as the course spine.
INBOUND 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.
- 01PURCHASING CONTEXTCreate upstream supply need
A Purchase Order defines the supply need, and an ASN may help inform receipt processing. This Basic TM path plans inbound delivery-based transportation demand.
- 02INBOUND DELIVERYCreate transportation-relevant inbound demand
The inbound delivery defines receipt location, supplier context, quantity, dates, and transportation relevance.
- 03TM DEMANDCreate DTR / transportation demand
The configured delivery trigger supplies transportation demand and preserves source references.
- 04FUBR / FREIGHT UNITBuild planning units
FUBR creates durable Freight Units with origin, destination, dates, quantity, and constraints.
- 05BASIC PLANNINGCreate the Freight Order
Assign route, equipment, schedule, capacity, stops, resource, and carrier field where applicable.
- 06EXECUTIONArrive, unload, post goods receipt, and put away
Warehouse and inventory evidence confirms physical receipt while TM reconciles transport 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.