WHSLoadTable
worksheet headerWarehouse 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
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
WHSLoadTable is the header for its lines in WHSLoadLine.
Fields
17 fields · 1 key
17 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | LoadId | LoadId | The load number — the natural key shipments and load lines join on | string | ||
| LoadStatus | Load status across its life cycle (open, in process, shipped…) | enum | ||||
| LoadDirection | Whether the load is outbound or inbound | enum | ||||
| InventSiteId | InventSiteId | Site the load ships from or arrives at | string | 10 | ||
| InventLocationId | InventLocationId | Warehouse the load ships from or arrives at | string | 10 | ||
| CarrierCode | Carrier assigned to the load | string | ||||
| CarrierServiceCode | Carrier service level for the load | string | ||||
| ModeCode | Transportation mode of the load | string | ||||
| LoadTemplateId | Load template (equipment type / capacity profile) the load was built with | string | ||||
| TrailerNumber | Trailer assigned to the load | string | ||||
| LoadWeight | Total weight on the load | real | ||||
| LoadShipConfirmUTCDateTime | When the load was ship-confirmed, stored in UTC — the outbound completion timestamp | datetime | ||||
| LoadSchedShipUTCDateTime | Scheduled ship datetime for the load, stored in UTC — compare to the confirm timestamp for schedule adherence | datetime | ||||
| LoadArrivalUTCDateTime | Planned arrival datetime of the load, stored in UTC | datetime | ||||
| AccountNum | Customer or vendor account behind a single-order load, depending on direction | string | 20 | |||
| OrderNum | OrderNum | Source order number for a single-order load | string | |||
| BillOfLadingId | Master bill of lading for the load | string |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading WHSLoadTable 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 : WHSLoadTable Warehouse 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
-- Purpose: Column-selected read of WHSLoadTable — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + LoadId
-- 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 "The load number — the natural key shipments and load lines join on",
w.loadstatus AS "Load status across its life cycle (open, in process, shipped…)", -- enum: decode w.loadstatus via GlobalOptionsetMetadata join — see quirks guide #enums
w.loaddirection AS "Whether the load is outbound or inbound", -- enum: decode w.loaddirection via GlobalOptionsetMetadata join — see quirks guide #enums
w.inventsiteid AS "Site the load ships from or arrives at",
w.inventlocationid AS "Warehouse the load ships from or arrives at",
w.carriercode AS "Carrier assigned to the load",
w.carrierservicecode AS "Carrier service level for the load",
w.modecode AS "Transportation mode of the load",
w.loadtemplateid AS "Load template (equipment type / capacity profile) the load was built with",
w.trailernumber AS "Trailer assigned to the load",
w.loadweight AS "Total weight on the load",
w.loadshipconfirmutcdatetime AS "When the load was ship-confirmed, stored in UTC — the outbound completion timestamp", -- stored in UTC
w.loadschedshiputcdatetime AS "Scheduled ship datetime for the load, stored in UTC — compare to the confirm timestamp for schedule adherence", -- stored in UTC
w.loadarrivalutcdatetime AS "Planned arrival datetime of the load, stored in UTC", -- stored in UTC
w.accountnum AS "Customer or vendor account behind a single-order load, depending on direction",
w.ordernum AS "Source order number for a single-order load",
w.billofladingid AS "Master bill of lading for the load"
FROM <catalog>.<schema>.whsloadtable w
WHERE
w.dataareaid = '<company>'
-- AND w.loadshipconfirmutcdatetime >= '<DATE_FROM>' -- yyyy-MM-dd (UTC)
-- AND w.loadshipconfirmutcdatetime <= '<DATE_TO>' -- yyyy-MM-dd (UTC)
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 whsshipmenttable.loadid = whsloadtable.loadid AND whsshipmenttable.dataareaid = whsloadtable.dataareaidON whsworktable.loadid = whsloadtable.loadid AND whsworktable.dataareaid = whsloadtable.dataareaid
Data Entities That Expose This Table
More Warehouse Management tables
- 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
- 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