Consolidated planned loading orders¶

Consolidated planned loading orders record how many vehicle trips a Supply Plan allocated to each origin-destination lane, fleet, vehicle type, and dispatch period.

This is a calculated planning output. It is not a vehicle-trip document and cannot be uploaded or edited under Data Operations. Supply Planning replaces the complete result for the selected scenario when a new constrained solution is persisted.

The dataset is different from historical Vehicle Loading Orders. The historical dataset describes scheduled or executed trips and can be linked to deliveries. This page describes the future number of trips proposed by a Supply Plan.

This output is currently part of the Enterprise planning surface. The Community does not publish this versioned interface as a Community contract.

Path in the platform¶

Data > Data Operations > Planning Data > SNP - Supply Network Planning > Purchase/Distribution Plan > Consolidated Loading Orders / Vehicle Type

Select the supplyPlanId before downloading the result.

Grain and key¶

One row represents the planned number of trips for:

supplyPlanId × originLocationId × destinationLocationId × fleetId × vehicleTypeId × referenceExpeditionDate

numberOfTrips is the measure associated with that key.

When the result is downloaded as a file, the selected supplyPlanId is the context of the complete extract and is not repeated in every row. It remains part of the logical identity of the data.

Required fields¶

Optional fields¶

There are no optional fields in this output. Every dimension and numberOfTrips must be present, so this dataset has no default-value column.

A value of 0 in numberOfTrips is an explicit calculated result, not a fallback for an empty field. A missing value is invalid.

Scenario meaning¶

This output belongs to the constrained Supply Plan. Fleet and vehicle allocation are not copied from an unconstrained plan and there is no separate unconstrained or working value inside the same row.

referenceExpeditionDate positions the result in the planning calendar. The distribution quantity for the same lane and period remains in the distribution plan; consolidated loading orders state how many trips and which fleet and vehicle type support that movement.

Dependencies¶

• an executed and persisted Supply Plan;
• Locations for origin and destination;
• fleets, vehicle types, their capacities, and compatible units in the transportation network;
• an active origin-destination lane in the network version selected by the plan;
• the Supply Planning calendar used to position referenceExpeditionDate;
• the constrained distribution result for the same lane and period;
• logistics costs when the planned trips must be valued economically.

Used by¶

• the Supply Plan as its consolidated vehicle-allocation output;
• the Supply Planning data model;
• Logistics Overview, which shows planned trips and allocates the constrained transferred quantity across fleet and vehicle combinations;
• DRP, Deployment, and Load Building to review future load requirements by lane and period;
• Cost-to-Serve and P&L, which multiplies trip cost by numberOfTrips and allocates that cost to the distributed materials on the same lane and period;
• plan comparison by lane, fleet, vehicle, period, and trip count;
• export and reconciliation of the restricted fleet-allocation result.

Validations¶

• the selected supplyPlanId exists;
• all six key dimensions are filled and the combined key is unique within the plan;
• origin and destination exist and belong to the network context of the plan;
• fleet and vehicle type exist and form a valid planning combination;
• referenceExpeditionDate belongs to the Supply Planning calendar;
• numberOfTrips is present, integer, and non-negative;
• the row belongs to the same Supply Plan selected for the extract;
• the result remains read-only and is replaced only by Supply Planning execution.