TM is not one flat transport document. The source holds the business need; the transportation requirement makes it relevant to TM; freight-unit building creates planning units; freight orders or bookings reserve capacity; settlement represents the carrier cost.
TM OBJECT MAP
From commercial demand to carrier cost
Arrows show usual relationships, not an unconditional sequence. Deployment, planning stage, mode, and configuration determine which objects exist and when they update.
BUSINESS DEMAND
Order, delivery, stock transfer, returnThe source keeps the business promise and logistics reference.
→
Transportation requirementTransport-relevant demand in TM.
PLANNING
Freight unitPlannable demand with dates, locations, quantities, and compatibility.
→
Freight order or bookingCapacity, route, stops, carrier, schedule, and execution plan.
COMMERCIAL PROOF
Charge calculationExpected cost from agreements, rates, and charge types.
→
Freight settlement documentCarrier-cost evidence for purchasing and invoice verification.
DIAGNOSTIC EVIDENCE
Ask the question at the correct layer
Transport problems become recoverable when the team checks the decision, source data, document, and event evidence in that order.
SOURCE & REQUIREMENT
Reference, locations, requested dates, quantities, transport relevance, and update message explain what TM was asked to plan.
FREIGHT UNIT & DOCUMENT
Compatibility, assignment, stops, schedule, carrier, tender, status, events, and exceptions explain the transport decision.
CHARGES & SETTLEMENT
Agreement, calculation basis, expected charges, settlement, purchasing follow-on documents, and invoice state explain the commercial result.
CONTINUE TO DETERMINATIONUnderstand why TM chose that result
Read from the visible transport outcome back to the selecting controls.