TM 202 · ENTER
How 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.
READ FROM RESULT BACK TO RULE
Prove that TM received the intended transportation demand
Basic TM combines transportation demand, master data, planning decisions, operating proof, and commercial settlement. A visible document status alone rarely explains whether the flow is feasible or recoverable.
ONE BASIC TM STORY
Follow the decision through its evidence
Each hand-off has a different owner and a different proof. Preserve the hand-off rather than repairing a later status in isolation.
- 01OUTBOUNDOutbound delivery demand
The outbound delivery carries ship-from, ship-to, quantity, dates, and transportation relevance into TM.
- 02INBOUNDInbound delivery demand
The inbound delivery carries receipt location, supplier context, quantity, dates, and transportation relevance into TM.
- 03TRANSFERTransportation demand / DTR
The TM demand record preserves source references, locations, dates, quantities, and changes before freight-unit building begins.
BASIC TM ENTRY
Did TM receive the right delivery-based demand?
Use Sales Orders and Purchase Orders as upstream business context. In this Basic TM path, do not teach direct SO/PO transportation planning as the planning source.
Sales Order -> Outbound Delivery -> TM
Confirm the delivery, relevance result, integration profile, and transportation demand created from it.
Purchase Order -> Inbound Delivery -> TM
Confirm the inbound delivery, source status, location and date transfer, and resulting transportation demand.
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.
Check delivery relevance, trigger prerequisites, integration profile, application log, queue or message status, and authorization.
Compare source reference, locations, quantities, dates, and change sequence before rebuilding planning.
Trace the source change, update message, processing result, retries, and the owner of the failed hand-off.
PROJECT MOMENT
The delivery is correct, but no Freight Unit exists
First establish whether TM received transportation demand. If it did not, investigate delivery relevance, integration, processing, or queues. Only investigate freight-unit building after credible demand exists.
- Delivery status is confirmed
- Transportation demand is found or proven absent
- Transferred data is compared with its source
- Reprocessing preserves the incident evidence
Use freight-unit building only after TM has received credible delivery-based demand.