Vehicle loading orders¶
A vehicle loading order records the historical or operational header of one load or trip. It may identify the fleet and vehicle type, the main origin and destination, planned and actual dates, transported weight or volume, travelled distance, and freight cost.
Deliveries can reference this header through loadingOrderId. The loading
order therefore groups execution records without repeating each material and
order line in this dataset.
This dataset is different from consolidated planned loading orders, which are calculated outputs of a Supply Plan and documented in Consolidated Planned Loading Orders. Historical loading orders describe what was scheduled or executed; planned loading orders describe a future consolidation proposed by the scenario.
This dataset is currently part of the Enterprise data-upload surface. The Community does not publish this versioned interface as a Community contract.
Path in the platform¶
Data > Data Operations > Transactional Data > Orders > Vehicle Loading Orders > Loading Orders
Grain and key¶
One row represents one historical vehicle load or trip header. Its unique key is:
id
The identifier must remain stable while the same load is updated. A different identifier represents another physical trip or loading document.
Required fields¶
| Field | Meaning |
|---|---|
id |
Unique identifier of the vehicle loading order |
Optional fields¶
| Field | Meaning | Default Value When Not Provided |
|---|---|---|
fleetId |
Fleet used by the load | No fleet linked |
vehicleTypeId |
Vehicle type used by the load | No vehicle type linked |
mainOriginLocationId |
Main location from which the load is dispatched | No origin location linked |
mainDestinationLocationId |
Main location at which the load is received | No main destination location linked |
originCountry |
Country of the main origin | No origin country assigned |
originState |
State or region of the main origin | No origin state or region assigned |
originCity |
City of the main origin | No origin city assigned |
destinationCountry |
Country of the main destination | No destination country assigned |
destinationState |
State or region of the main destination | No destination state or region assigned |
destinationCity |
City of the main destination | No destination city assigned |
plannedExpeditionDate |
Planned dispatch date and time | No planned dispatch date assigned |
expeditionDate |
Actual dispatch date and time | No actual dispatch date assigned |
deliveryDate |
Actual delivery date and time | No actual delivery date assigned |
distanceTraveledInKm |
Distance travelled by the load, in kilometers | Sum of the associated drop-off distances; if unavailable, route distance; otherwise 0 |
loadWeightUom |
Unit used by loadWeight |
Default logistics weight unit in Global Planning Parameters; if empty, the default Supply Planning unit and then UN |
loadWeight |
Total weight stated in the loading-order header | Total from associated drop-offs or delivery lines; if none is available, 0 in weight calculations |
loadVolumeUom |
Unit used by loadVolume |
Default logistics volume unit in Global Planning Parameters; if empty, the default Supply Planning unit and then UN |
loadVolume |
Total volume stated in the loading-order header | Total from associated drop-offs or delivery lines; if none is available, 0 in volume calculations |
freightCost |
Freight cost assigned to the load | No freight cost assigned; absence is not treated as zero |
Country, state, and city fields allow a historical load to retain geographic context even when the corresponding location is not registered. When a location and geographic fields are both provided, they should describe the same origin or destination.
Quantity and distance resolution¶
The loading-order header is the first source for weight, volume, and distance. When the header quantity is absent, calculations can use associated drop-offs and then linked delivery lines. A missing quantity therefore does not create transported volume by itself.
Distance follows a similar precedence: the value recorded in the header,
associated drop-offs, and then a linked route. When none of these sources
provides distance, the historical projection uses 0.
Freight cost follows a stricter economic rule. An empty freightCost means
that no cost was assigned to the load; it is not silently converted to zero.
Dependencies¶
- Fleets and vehicle types when
fleetIdorvehicleTypeIdis provided; - Locations when either location field is provided;
- Units of Measure for explicit or default weight and volume units and their conversions;
- Global Planning Parameters for default logistics and Supply Planning units;
- coherent route or drop-off information when distance must be derived rather than recorded in the header.
Used by¶
- Deliveries, which can use
loadingOrderIdto group order execution lines into the same vehicle load; - historical analysis by fleet, vehicle type, origin, destination, dispatch period, and receiving period;
- dispatched and received quantity reconciliation using header, drop-off, and delivery-line detail;
- logistics cost-curve calibration from utilization, distance, and freight observations;
- DRP, Deployment, and Load Building as execution history and a benchmark for future load consolidation;
- Consolidated Planned Loading Orders as the future trip result that can be compared with historical execution;
- planned-versus-actual dispatch and delivery analysis;
- logistics utilization, occupancy, distance, and freight diagnostics.
Validations¶
idis filled and unique;- every provided fleet, vehicle type, location, and unit exists;
distanceTraveledInKm,loadWeight,loadVolume, andfreightCost, when provided, are finite and non-negative;- explicit weight and volume units are convertible to the units used by the analysis;
- origin and destination geography is consistent with the linked locations when both forms of identification are provided;
- a missing freight cost is treated as incomplete cost information, not as a zero-cost trip;
- deliveries reference an existing loading order before using its
id.