D365 Reference
WHSOutboundLoadHeaderEntity
Outbound load headers — load-level export with carrier, equipment, and seal detail for outbound transportation
Tables vs entities
This entity is an export-shaped view over the tables below. When you land raw F&O tables instead of the entity, the SQL further down rebuilds it — joining the backing tables on their keys and DataAreaId. When to land tables vs entities
Notes
CDM-verified; display name "Outbound load header"; introduced 10.0.13. Backing table WHSLoadTable per the CDM BackingTable relationship.
Rebuild-from-tables SQL
Databricks SQLStarting point for reconstructing this entity from landed tables — the backing tables joined on their keys and DataAreaId. Set your Unity Catalog location, company, and filter values below.
Query parameters
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Entity : WHSOutboundLoadHeaderEntity
-- Purpose: Rebuild WHSOutboundLoadHeaderEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per WHSLoadTable record
-- Tables : WHSLoadTable
-- 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. Company-partitioned tables are joined on DataAreaId to prevent cross-company fan-out. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
h.loadid AS "The load number — the natural key shipments and load lines join on"
FROM <catalog>.<schema>.whsloadtable h
WHERE
h.dataareaid = '<company>'
ORDER BY h.loadid;