Skip to content
D365 Reference

WHSLoadTable

worksheet header

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

Module: Warehouse ManagementCompany-partitioned (DataAreaId)
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/ValidTo effectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
In field listings, K marks a key field.
Used in the library
KPI definitions
Dashboard patterns

Header & line

WHSLoadTable is the header for its lines in WHSLoadLine.

Fields

17 fields · 1 key

17 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 17 fields.
KeyFieldEDTDescriptionTypeLengthFlags
KeyLoadIdLoadIdThe load number — the natural key shipments and load lines join onstring
LoadStatusLoad status across its life cycle (open, in process, shipped…)enum
LoadDirectionWhether the load is outbound or inboundenum
InventSiteIdInventSiteIdSite the load ships from or arrives atstring10
InventLocationIdInventLocationIdWarehouse the load ships from or arrives atstring10
CarrierCodeCarrier assigned to the loadstring
CarrierServiceCodeCarrier service level for the loadstring
ModeCodeTransportation mode of the loadstring
LoadTemplateIdLoad template (equipment type / capacity profile) the load was built withstring
TrailerNumberTrailer assigned to the loadstring
LoadWeightTotal weight on the loadreal
LoadShipConfirmUTCDateTimeWhen the load was ship-confirmed, stored in UTC — the outbound completion timestampdatetime
LoadSchedShipUTCDateTimeScheduled ship datetime for the load, stored in UTC — compare to the confirm timestamp for schedule adherencedatetime
LoadArrivalUTCDateTimePlanned arrival datetime of the load, stored in UTCdatetime
AccountNumCustomer or vendor account behind a single-order load, depending on directionstring20
OrderNumOrderNumSource order number for a single-order loadstring
BillOfLadingIdMaster bill of lading for the loadstring

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.

Query parameters

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

  • WHSLoadTableWHSLoadLineheader line · 1:N
    ON whsloadtable.loadid = whsloadline.loadid AND whsloadtable.dataareaid = whsloadline.dataareaid
  • WHSShipmentTableWHSLoadTableforeign key · N:1
    ON whsshipmenttable.loadid = whsloadtable.loadid AND whsshipmenttable.dataareaid = whsloadtable.dataareaid
  • WHSWorkTableWHSLoadTableforeign key · N:1
    ON whsworktable.loadid = whsloadtable.loadid AND whsworktable.dataareaid = whsloadtable.dataareaid

Data Entities That Expose This Table

More Warehouse Management tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Microsoft. Microsoft, Dynamics 365, and Microsoft Fabric are trademarks of the Microsoft group of companies.