303
PRACTITIONERTrace execution across SAP boundaries

TM 303 · PRACTITIONER PROCESS MAP

How does a TM practitioner run the transport day?

Protect the delivery promise by working the first broken commitment. Demand release, planning, carrier acceptance, warehouse readiness, execution, and settlement each need different evidence and a named recovery owner.

OPERATING RHYTHM

Work the earliest broken hand-off

Do not start with the last red status. The earlier decision that lost feasibility is usually cheaper and safer to recover.

  1. 01
    RELEASEDemand ready?

    Review new, changed, cancelled, and failed freight-unit demand.

  2. 02
    PLANCapacity feasible?

    Work unplanned freight, constraint exceptions, and service risks.

  3. 03
    COMMITCarrier accountable?

    Manage tender response, rejection, timeout, and alternate capacity.

  4. 04
    MOVEPhysical and event proof aligned?

    Reconcile warehouse readiness, loading, departure, arrival, and changes.

  5. 05
    CLOSECost reconciled?

    Resolve charge, settlement, purchasing, and invoice exceptions.

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.

SERVICE

Requested versus planned versus committed versus actual dates, quantities, and stops.

CAPACITY

Unplanned freight, utilization, rejected tenders, late readiness, and missed milestones.

COST

Expected charges, settlement status, invoice variance, accrual, and unresolved accessorials.

CONTINUE TO TM 404Turn operating evidence into a proven solution

Design the data, rules, documents, integrations, controls, and recovery evidence.

Open solution workbench
Official SAP referencesSAP Help — Creation and Editing of Freight Units SAP Help — Carrier Selection SAP Help — Freight Settlement Document SAP Help — Advanced Shipping and Receiving