Deliveries¶

A delivery records the execution of an order line: what has been separated, put in transit, or delivered. It does not repeat material, location, or unit data. Those attributes come from the linked order item, keeping the delivery and the commercial or replenishment commitment reconciled.

Two datasets share the same delivery-line model:

Sell-Out Deliveries link execution to sell-out orders;
Sell-In / Purchase / Transfer Deliveries link execution to orders with an identified destination and may provide an expected delivery date.

These datasets are currently part of the Enterprise data-upload surface. The Community does not publish these versioned interfaces as Community contracts.

Path in the platform¶

Data > Data Operations > Transactional Data > Orders > Sell-Out Orders > Sell-Out Deliveries
Data > Data Operations > Transactional Data > Orders > Sell-In / Purchase / Transfer Orders > Sell-In / Purchase / Transfer Deliveries

Grain and key¶

One row represents one delivery line applied to one order item. Its unique key combines:

deliveryId × orderId × orderItemId × deliveryLineId

The same delivery may contain several lines. Reusing one of these four-part keys would overwrite the identity of an existing delivery line.

Required fields¶

Field	Meaning
`deliveryId`	Identifier of the delivery document
`orderId`	Identifier of the linked order
`orderItemId`	Identifier of the item inside that order
`deliveryLineId`	Identifier of the line inside the delivery

Optional fields shared by both datasets¶

Field	Meaning	Default Value When Not Provided
`loadingOrderId`	Vehicle loading order that groups the delivery	No loading order linked
`creationDate`	Date and time when the delivery was created	Current application date and time
`quantity`	Quantity separated, in transit, or delivered	`0`
`status`	Current delivery-line status	`Not Separated`

status accepts only the values documented in Delivery Status.

Additional optional field for Sell-In / Purchase / Transfer Deliveries¶

Field	Meaning	Default Value When Not Provided
`expectedDeliveryDate`	Expected date when the quantity becomes available at the destination	Expected date registered for the delivery; if unavailable, the linked order-item date

The Sell-Out Deliveries file does not contain expectedDeliveryDate.

Data inherited from the order item¶

The delivery file does not ask again for:

material;
origin and destination locations;
unit of measure;
requested or confirmed order dates.

These values are resolved through orderId and orderItemId in Open Orders. The delivery quantity therefore uses the unit of the linked order line.

Dependencies¶

an existing open-order item identified by orderId and orderItemId;
the materials, locations, and unit of measure already resolved by that order item;
a vehicle loading order when loadingOrderId is provided;
Delivery Status;
the transportation network when the linked order represents a transfer.

Used by¶

reconciliation of ordered, delivered, and remaining open quantities;
effective open-order projection used by the Supply Planning data model;
positioning of receipts at the destination by expected date;
treatment of quantities in picking, transit, or already delivered;
historical vehicle-loading analysis through Vehicle Loading Orders when loadingOrderId is present;
DRP, Deployment, and Load Building;
service and last-delivery-date analysis on the linked order item.

Validations¶

all four key fields are provided and the combined key is unique;
orderId and orderItemId resolve to the same existing order item;
loadingOrderId, when provided, resolves to an existing loading order;
quantity is finite and non-negative;
the status uses the exact accepted payload value;
delivery quantity and order quantity are reconciled in the same unit;
a delivery is not counted twice as both open quantity and completed receipt;
creation and expected dates are filled when chronological filtering and destination availability must be auditable.