WHSWorkTable
worksheet headerWarehouse work header — one row per work order (pick, put, count, replenish) created by wave processing, with status, priority, and the load/shipment it serves
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
WHSWorkTable is the header for its lines in WHSWorkLine.
Fields
17 fields · 1 key
17 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | WorkId | WorkId | The work order number — the natural key work lines join back on | string | ||
| WorkStatus | Work status across its life cycle (open, in process, closed, cancelled) | enum | ||||
| WorkTransType | What kind of order the work serves — sales, transfer, purchase, counting… | enum | ||||
| InventSiteId | InventSiteId | Site the work executes at | string | 10 | ||
| InventLocationId | InventLocationId | Warehouse the work executes in | string | 10 | ||
| LoadId | LoadId | Load the work was created for | string | |||
| ShipmentId | ShipmentId | Shipment the work was created for | string | |||
| OrderNum | OrderNum | Source order number behind the work | string | |||
| WaveId | Wave that generated the work | string | ||||
| WorkPoolId | Work pool the order is grouped into for dispatching | string | ||||
| WorkPriority | Dispatching priority of the work order | int | ||||
| LockedUser | Warehouse worker currently holding the work on a mobile device | string | ||||
| TargetLicensePlateId | License plate the work builds onto | string | ||||
| ContainerId | Container the work is associated with, for containerized picking | string | ||||
| WorkClosedUTCDateTime | When the work order was completed, stored in UTC — the labor-productivity timestamp | datetime | ||||
| WorkInProcessUTCDateTime | When the work was first picked up by a worker, stored in UTC | datetime | ||||
| WorkCancelledUTCDateTime | When the work was cancelled, stored in UTC | datetime |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading WHSWorkTable 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.
5 parameters not filled: <catalog>, <schema>, <company>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : WHSWorkTable Warehouse work header — one row per work order (pick, put, count, replenish) created by wave processing, with status, priority, and the load/shipment it serves
-- Purpose: Column-selected read of WHSWorkTable — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + WorkId
-- 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.workid AS "The work order number — the natural key work lines join back on",
w.workstatus AS "Work status across its life cycle (open, in process, closed, cancelled)", -- enum: decode w.workstatus via GlobalOptionsetMetadata join — see quirks guide #enums
w.worktranstype AS "What kind of order the work serves — sales, transfer, purchase, counting…", -- enum: decode w.worktranstype via GlobalOptionsetMetadata join — see quirks guide #enums
w.inventsiteid AS "Site the work executes at",
w.inventlocationid AS "Warehouse the work executes in",
w.loadid AS "Load the work was created for",
w.shipmentid AS "Shipment the work was created for",
w.ordernum AS "Source order number behind the work",
w.waveid AS "Wave that generated the work",
w.workpoolid AS "Work pool the order is grouped into for dispatching",
w.workpriority AS "Dispatching priority of the work order",
w.lockeduser AS "Warehouse worker currently holding the work on a mobile device",
w.targetlicenseplateid AS "License plate the work builds onto",
w.containerid AS "Container the work is associated with, for containerized picking",
w.workclosedutcdatetime AS "When the work order was completed, stored in UTC — the labor-productivity timestamp", -- stored in UTC
w.workinprocessutcdatetime AS "When the work was first picked up by a worker, stored in UTC", -- stored in UTC
w.workcancelledutcdatetime AS "When the work was cancelled, stored in UTC" -- stored in UTC
FROM <catalog>.<schema>.whsworktable w
WHERE
w.dataareaid = '<company>'
-- AND w.workclosedutcdatetime >= '<DATE_FROM>' -- yyyy-MM-dd (UTC)
-- AND w.workclosedutcdatetime <= '<DATE_TO>' -- yyyy-MM-dd (UTC)
ORDER BY w.workid;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 whsworktable.workid = whsworkline.workid AND whsworktable.dataareaid = whsworkline.dataareaidON whsworktable.loadid = whsloadtable.loadid AND whsworktable.dataareaid = whsloadtable.dataareaidON whsworktable.shipmentid = whsshipmenttable.shipmentid AND whsworktable.dataareaid = whsshipmenttable.dataareaid
Data Entities That Expose This Table
More Warehouse Management tables
- WHSLoadLineWarehouse 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
- 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