TM 606 · PRODUCTION SUPPORT
How do you support Basic TM in production?
Do not collapse transportation demand, a valid plan, physical movement, and freight cost into one status. Start with the last transportation object you trust, then find the first broken hand-off.
TM EVIDENCE SPINE
Trace demand through execution and settlement
Keep source demand, TM planning, physical movement, and carrier-cost evidence distinct while following the first broken hand-off.
- 01Delivery demandReference
- 02Transportation demand / DTRRequirement
- 03Freight UnitPlanning unit
- 04Freight OrderPlan
- 05Physical executionMovement
- 06Commercial settlementCharges and AP
TM EVIDENCE CHAIN
Trace the first broken boundary
Outbound and inbound have different upstream contexts but converge on one Basic TM planning, execution, costing, and settlement engine.
- 01BUSINESS CONTEXTSales Order or Purchase Order context plus delivery demand
Confirm the expected quantity, locations, dates, delivery status, and transportation relevance.
- 02TRANSPORTATION DEMANDDTR / requirement enters TM
Check the expected demand and its source references before investigating later documents.
- 03PLANNING UNITFreight Unit
Confirm FUBR, split, grouping, quantity, dates, locations, and compatibility.
- 04TRANSPORT PLANFreight Order
Check route, stops, schedule, resource, capacity, equipment, assigned carrier field, and planned dates.
- 05PHYSICAL EXECUTIONWarehouse, loading, departure, arrival, PGI, or GR
Compare delivery and warehouse evidence with execution events and TM status.
- 06COMMERCIAL SETTLEMENTCharges, FSD, PO / SES, supplier invoice, and FI
Trace charge calculation through settlement and downstream purchasing, invoice, and finance evidence.
TRIAGE THE INCIDENT
Classify before changing configuration
Identify the affected evidence layer. Correct from the owning object outward; do not repair a later status to hide an upstream failure.
Check transportation relevance, integration trigger, source status, locations, quantities, dates, and queues.
Check FUBR, handling data, incompatibilities, locations, and planning dates.
Check planning profile, route, schedule, resource/capacity, equipment, constraints, and planned dates.
Check delivery relationship, warehouse hand-off, events, PGI or GR, and message processing.
Check agreement, rate, charge basis, validity, settlement relevance, and FSD status.
Check PO or SES, supplier, Invoice Verification, match or variance, and posting treatment.
PROJECT MOMENT
A Freight Order is complete, but the carrier invoice cannot be posted
Do not change the transport plan. Confirm charge calculation and the FSD, then trace PO and SES where applicable, followed by invoice match and AP/FI posting.
- Keep planning, execution, and settlement separate
- Find the first missing or implausible object
- Correct from the owning object outward
- Reconcile the chain before closure
CLOSE AND PREVENT
Prove the whole transport story agrees again
Close only when delivery demand, transportation demand, Freight Unit, Freight Order, physical execution, charges, settlement, purchasing evidence, supplier invoice, and FI tell the same story. Monitor ageing Freight Units, unplanned demand, missing events, completed transports without settlement, FSDs without PO or SES, and recurring invoice variance.
Follow outbound and inbound through the same planning, execution, settlement, and finance chain.