WHSLoadLine
worksheet lineWarehouse 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
What the badges mean
- main
- Table group: how F&O categorizes the table's role — main entity, group/header, transaction, worksheet header, worksheet line, reference, parameter, or framework.
- Shared across companies
- The table carries no
DataAreaId— rows aren’t partitioned per company, so a query never needs (and can’t use) a company filter here (see the quirks guide). - Date-effective
- The table carries a
ValidFrom/ValidToeffectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
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
15 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | LoadId | LoadId | Load this line sits on — joins back to its WHSLoadTable header | string | ||
| Key | InventTransId | InventTransId | Lot ID of the source document line the load line fulfills — with LoadId, the practical grain of the table | string | 40 | |
| ShipmentId | ShipmentId | Shipment the line was assigned to when shipments were built | string | |||
| OrderNum | OrderNum | Source order number of the line (sales or transfer order, per direction) | string | |||
| ItemId | ItemId | Item on the line | string | 20 | ||
| InventDimId | InventDimId | Inventory-dimension combination of the line; join to InventDim to resolve site / warehouse / batch | string | 25 | ||
| InventTransType | Type of source document behind the line (sales order, transfer, purchase…) | enum | ||||
| LoadDirection | Whether the line is outbound or inbound | enum | ||||
| Qty | Quantity placed on the load for the line, in the line unit | real | ||||
| PickedQty | Quantity already picked against the line | real | ||||
| WorkCreatedQty | Quantity for which warehouse work has been created | real | ||||
| InventQty | Line quantity expressed in the inventory unit | real | ||||
| UOM | Unit the load-line quantity is expressed in | string | ||||
| LoadClosedUTCDateTime | When the line's load was closed, stored in UTC | datetime | ||||
| RecId | RecId | The 64-bit surrogate key work lines reference via LoadLineRefRecId | int64 |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading WHSLoadLine on 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.
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- 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;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON whsloadtable.loadid = whsloadline.loadid AND whsloadtable.dataareaid = whsloadline.dataareaidON whsloadline.shipmentid = whsshipmenttable.shipmentid AND whsloadline.dataareaid = whsshipmenttable.dataareaidON whsloadline.itemid = inventtable.itemid AND whsloadline.dataareaid = inventtable.dataareaidON whsloadline.inventdimid = inventdim.inventdimid AND whsloadline.dataareaid = inventdim.dataareaidON whsworkline.loadlinerefrecid = whsloadline.recid
Data Entities That Expose This Table
More Warehouse Management tables
- WHSLoadTableWarehouse load header — one row per load (a truck, trailer, or container worth of goods); shipments are grouped onto loads, and ship confirmation happens at this level
- WHSShipmentTableWarehouse shipment header — one row per shipment built from released order lines, carrying its load, status, carrier, and ship-confirm timestamp; the outbound unit customers track
- WHSWorkLineWarehouse work line — the individual pick and put steps of a work order, with item, location, quantities, and the worker who executed them; the grain for labor and travel analysis
- WHSWorkTableWarehouse work header — one row per work order (pick, put, count, replenish) created by wave processing, with status, priority, and the load/shipment it serves