Skip to content
D365 Reference

WHSLoadLine

worksheet line

Warehouse load line — one row per order line placed on a load, linking the load and shipment to the source document line, item, and picked quantities

Module: Warehouse ManagementCompany-partitioned (DataAreaId)Header: WHSLoadTable

Header & line

WHSLoadLine lines join back to their header WHSLoadTable — and the DataAreaId — so a line never fans out across companies.

Fields

15 fields · 2 key

KeyFieldEDTDescriptionTypeLengthFlags
KeyLoadIdLoadIdLoad this line sits on — joins back to its WHSLoadTable headerstring
KeyInventTransIdInventTransIdLot ID of the source document line the load line fulfills — with LoadId, the practical grain of the tablestring40
ShipmentIdShipmentIdShipment the line was assigned to when shipments were builtstring
OrderNumOrderNumSource order number of the line (sales or transfer order, per direction)string
ItemIdItemIdItem on the linestring20
InventDimIdInventDimIdInventory-dimension combination of the line; join to InventDim to resolve site / warehouse / batchstring25
InventTransTypeType of source document behind the line (sales order, transfer, purchase…)enum
LoadDirectionWhether the line is outbound or inboundenum
QtyQuantity placed on the load for the line, in the line unitreal
PickedQtyQuantity already picked against the linereal
WorkCreatedQtyQuantity for which warehouse work has been createdreal
InventQtyLine quantity expressed in the inventory unitreal
UOMUnit the load-line quantity is expressed instring
LoadClosedUTCDateTimeWhen the line's load was closed, stored in UTCdatetime
RecIdRecIdThe 64-bit surrogate key work lines reference via LoadLineRefRecIdint64

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading WHSLoadLineon Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : WHSLoadLine Warehouse load line — one row per order line placed on a load, linking the load and shipment to the source document line, item, and picked quantities
-- Purpose: Column-selected read of WHSLoadLine — auto-generated from field metadata
-- Grain  : One row per company (dataareaid) + LoadId + InventTransId
-- Notes  : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
  w.loadid AS "Load this line sits on — joins back to its WHSLoadTable header",
  w.inventtransid AS "Lot ID of the source document line the load line fulfills — with LoadId, the practical grain of the table",
  w.shipmentid AS "Shipment the line was assigned to when shipments were built",
  w.ordernum AS "Source order number of the line (sales or transfer order, per direction)",
  w.itemid AS "Item on the line",
  w.inventdimid AS "Inventory-dimension combination of the line; join to InventDim to resolve site / warehouse / batch",
  w.inventtranstype AS "Type of source document behind the line (sales order, transfer, purchase…)",  -- enum: decode w.inventtranstype via GlobalOptionsetMetadata join — see quirks guide #enums
  w.loaddirection AS "Whether the line is outbound or inbound",  -- enum: decode w.loaddirection via GlobalOptionsetMetadata join — see quirks guide #enums
  w.qty AS "Quantity placed on the load for the line, in the line unit",
  w.pickedqty AS "Quantity already picked against the line",
  w.workcreatedqty AS "Quantity for which warehouse work has been created",
  w.inventqty AS "Line quantity expressed in the inventory unit",
  w.uom AS "Unit the load-line quantity is expressed in",
  w.loadclosedutcdatetime AS "When the line's load was closed, stored in UTC",  -- stored in UTC
  w.recid AS "The 64-bit surrogate key work lines reference via LoadLineRefRecId"
FROM <catalog>.<schema>.whsloadline w
-- Dimension expansion: uncomment to resolve site / warehouse / location / batch
-- LEFT JOIN <catalog>.<schema>.inventdim id ON id.inventdimid = w.inventdimid AND id.dataareaid = w.dataareaid
WHERE
  w.dataareaid = '<company>'
ORDER BY w.loadid;

3 parameters not filled: <catalog>, <schema>, <company>

Relationships

1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • WHSLoadTableWHSLoadLineheader line · 1:N
    ON whsloadtable.loadid = whsloadline.loadid
  • WHSLoadLineWHSShipmentTableforeign key · N:1
    ON whsloadline.shipmentid = whsshipmenttable.shipmentid
  • WHSLoadLineInventTableforeign key · N:1
    ON whsloadline.itemid = inventtable.itemid
  • WHSLoadLineInventDimInventDim · N:1
    ON whsloadline.inventdimid = inventdim.inventdimid
  • WHSWorkLineWHSLoadLineRecId ref · N:1
    ON whsworkline.loadlinerefrecid = whsloadline.recid

Data Entities That Expose This Table

No standard export entity verified — land the raw table.