BOMBillOfMaterialsHeaderEntity
Bill of materials headers — one record per BOM header, the standard export for BOM identifiers, names, and approval state
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
Name confirmed via the CDM entity page (backing table BOMTable) and MS Learn integration docs. OData collection name not primary-source verified, so it is omitted.
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 : BOMBillOfMaterialsHeaderEntity
-- Purpose: Rebuild BOMBillOfMaterialsHeaderEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per BOMTable record
-- Tables : BOMTable
-- 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.bomid AS "The BOM identifier — the natural key BOM lines and versions join on",
h.name AS "BOM name"
FROM <catalog>.<schema>.bomtable h
WHERE
h.dataareaid = '<company>'
ORDER BY h.bomid;