D365 Reference
BOMTable
mainBill of materials header — one row per BOM identifier, with its name, approval state, and production site; versions in BOMVersion decide which items use it and when
Module: Production ControlCompany-partitioned (DataAreaId)
Header & line
BOMTable is the header for its lines in BOM.
Fields
8 fields · 1 key
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | BOMId | BOMId | The BOM identifier — the natural key BOM lines and versions join on | string | 20 | |
| Name | BOM name | string | 60 | |||
| ItemGroupId | Item group used to filter and organize BOMs | string | ||||
| SiteId | InventSiteId | Production site the BOM applies to; blank means site-independent | string | 10 | ||
| Approved | Whether the BOM header is approved for use | enum | ||||
| Approver | RecId | RecId of the worker who approved the BOM | int64 | |||
| CheckBOM | Whether circular-reference checking is enforced for this BOM | enum | ||||
| PmfBOMFormula | Whether the record is a discrete BOM or a process-manufacturing formula | enum |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading BOMTableon 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
-- ============================================================
-- Table : BOMTable Bill of materials header — one row per BOM identifier, with its name, approval state, and production site; versions in BOMVersion decide which items use it and when
-- Purpose: Column-selected read of BOMTable — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + BOMId
-- 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
b.bomid AS "The BOM identifier — the natural key BOM lines and versions join on",
b.name AS "BOM name",
b.itemgroupid AS "Item group used to filter and organize BOMs",
b.siteid AS "Production site the BOM applies to; blank means site-independent",
b.approved AS "Whether the BOM header is approved for use", -- enum: decode b.approved via GlobalOptionsetMetadata join — see quirks guide #enums
b.approver AS "RecId of the worker who approved the BOM",
b.checkbom AS "Whether circular-reference checking is enforced for this BOM", -- enum: decode b.checkbom via GlobalOptionsetMetadata join — see quirks guide #enums
b.pmfbomformula AS "Whether the record is a discrete BOM or a process-manufacturing formula" -- enum: decode b.pmfbomformula via GlobalOptionsetMetadata join — see quirks guide #enums
FROM <catalog>.<schema>.bomtable b
WHERE
b.dataareaid = '<company>'
ORDER BY b.bomid;3 parameters not filled: <catalog>, <schema>, <company>
Relationships
1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON bomtable.bomid = bom.bomidON prodtable.bomid = bomtable.bomidON bomversion.bomid = bomtable.bomid