🌐 NL · Last reviewed: 27 May 2026
Transport planning and request lifecycle
Transport requests arise automatically from released sales or purchase flows. Transport Planning is the UI where planners group requests by type, customer, due date, vendor — and compile them into transport orders.
The request lifecycle
-
Request appears (auto on shipment/receipt release, or manually) → status To Plan.
-
Planner filters and selects requests in Transport Planning.
-
Compile Transport Order bundles selected requests into one transport order.
-
The order moves through its lifecycle (Open → Released → Posted).
-
Request status auto-updates: Partly Planned, Planned, Shipped, Received.
-
The Update Transport Request Status report keeps request status in sync with the transport order status.
Key screens
|
Page |
Purpose |
|---|---|
|
Transport Planning |
Main planner page. |
|
Transport Request Lines |
Per-request detail. |
|
Compile Transport Order |
Wizard to merge requests. |
|
Transport Line Planning |
Worklist per vehicle/route. |
|
Transport Request Address Factbox |
Stop address details. |
|
Transport External Processing |
For outbound to external carriers. |
Best practices
Schedule Update Transport Request Status as a daily job. Keeps request statuses fresh without manual intervention.
Use the To Plan filter in Transport Planning to surface only unfinished requests. Reduces visual clutter for planners.
[Screenshot: Transport Planning with multiple requests grouped per route]