InventWarehouseEntity
Warehouses — the warehouse master export, one record per warehouse with its site, type, and warehouse-management settings
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
CDM-verified; backing table InventLocation (BackingTable_InventLocationRelationshipId on the CDM page). CDM display name: Warehouses. No version suffix.
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.
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Entity : InventWarehouseEntity
-- Purpose: Rebuild InventWarehouseEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per InventLocation record
-- Tables : InventLocation
-- 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
loc.inventlocationid AS "The warehouse code",
loc.name AS "Warehouse name"
FROM <catalog>.<schema>.inventlocation loc
LEFT JOIN <catalog>.<schema>.inventsite i
ON i.siteid = loc.inventsiteid
AND i.dataareaid = loc.dataareaid
WHERE
loc.dataareaid = '<company>'
ORDER BY loc.inventlocationid;Backing Tables
How these tables connect — join details in the list below.
Join details
ON inventlocation.inventsiteid = inventsite.siteid AND inventlocation.dataareaid = inventsite.dataareaid