Warehouse Receipts
GETTable: Warehouse Receipt Header
The inbound mirror of warehouse shipments, receive purchase orders through a warehouse, or carry a van's pickup run, then post the receipt.
createWarehouseReceipt action on a purchase order, or createPickupLoad on a sales return order.How a receipt is created
Release the purchase order, then call the action. The order's location must have Require Receive enabled, or the call errors:
POST /purchaseOrders(<id>)/Microsoft.NAV.release
POST /purchaseOrders(<id>)/Microsoft.NAV.createWarehouseReceiptThe response redirects to the new warehouseReceipt. GET it and $expand=warehouseReceiptLines to see what is expected.
A receipt is also the inbound vehicle load
In the own-fleet route model a vehicle's load is a warehouse document: a warehouse shipment when the van delivers, and a warehouse receipt when it picks up. createPickupLoad on a sales return order assembles several released return orders into one receipt and stamps the route onto it, so a pickup run needs no separate run or trip entity.
$expand=routeStops for the ordered collections on the run. See Route Stops.
Fields the route model needs, and where they come from
Business Central gives the warehouse shipment header a shipping agent, a shipping agent service, and a shipment date. The receipt header has none of them (its posting date is a general-ledger date, not a date of handling) so eOne adds the equivalents:
| Column | What it carries |
|---|---|
integrationId | the planner's route or trip id for this load |
shippingAgentCode / shippingAgentServiceCode | the vehicle collecting the load |
receiptDate | the route date the load is collected on |
totalWeight / totalVolume | rollups of the receipt lines, for vehicle capacity |
totalWeight and totalVolume are in the company's mass and volume units. Business Central carries no unit on the value, so map them to whatever unit the planner expects.
createPickupLoad; a warehouse user sees them on the native Warehouse Receipt page, together with the route stops, but does not edit them. Route data is integration-owned.Bound actions
Invoke with POST /warehouseReceipts(<id>)/Microsoft.NAV.<action>:
post: receives the whole document. Returns204rather than redirecting, because one receipt can post several source documents.
POST /warehouseReceipts(<id>)/Microsoft.NAV.post$expand=warehouseReceiptLines to see the expected lines and trace each back to its source order. See Warehouse Receipt Lines.