What determines a transport result?

A Freight Unit, Freight Order, route, status, or charge is an outcome, not an explanation. Basic TM determines it from delivery relevance, FUBR, master data, planning profiles, dates, resources, equipment, execution evidence, and commercial rules.

DETERMINATION MAP

From visible outcome to the controls to inspect

These are connected layers rather than an app or configuration recipe. Available settings depend on release, deployment, and activated scope.

VISIBLE OUTCOMEDemand not created

Delivery exists but transportation demand or DTR is missing.

InspectTransportation relevance, trigger prerequisites, integration profile, source status, application log, queue, and authorization.

VISIBLE OUTCOMEFreight Unit split

One source demand becomes one or several planning units.

InspectFUBR, source attributes, conditions, compatibility, product, handling data, dates, and quantities.

VISIBLE OUTCOMEPlan or assignment

Freight is grouped, excluded, or assigned to a Freight Order.

InspectPlanning profile, horizon, route, dates, capacity, resource, equipment, stop sequence, and incompatibilities.

VISIBLE OUTCOMEExecution status

A transport appears ready, loaded, departed, arrived, delayed, or cancelled.

InspectFreight Order and stop status, source event, warehouse and delivery evidence, event mapping, message processing, and recovery owner.

VISIBLE OUTCOMEExpected charge

Freight cost is calculated or missing.

InspectAgreement, calculation sheet, rate table, scale, units, distance, currency, validity, charge type, and accessorial input.

VISIBLE OUTCOMESettlement failure

FSD, PO, SES, invoice, or FI evidence is missing or blocked.

InspectSettlement relevance, carrier purchasing data, service entry, account assignment, tax, period, match status, and posting logs.

PROJECT MOMENT

A Freight Unit cannot be planned

Do not jump to commercial or carrier workflow explanations. Check the planning profile, route, schedule, resource, capacity, equipment, constraints, and planned dates before changing the Freight Order by hand.

Start with the visible object and status
Identify the relevant decision layer
Compare source data and validity
Make the recovery decision explicit

CONTINUE TO TM 202Turn demand into plannable freight

Use FUBR to trace Freight Unit creation and changes.

Open demand and Freight Units

Official SAP referencesSAP Help - Creation and Editing of Freight Units SAP Help - Freight Settlement Document