BOM_COMPONENTS_B
Schema: BOMmasterSingle-level bill components — one row per component per operation per effectivity window, with usage quantity, yield, supply type, and the supply subinventory shop-floor issues pull from
Rows are date-effective — the same component reappears per revision window; filter EFFECTIVITY_DATE/DISABLE_DATE around an as-of date (and IMPLEMENTATION_DATE IS NOT NULL) or explosions double-count
No org column — the organization resolves through the bill header. The legacy BOM_INVENTORY_COMPONENTS view over this table is FILTERED (it hides PLM-object and overlapping-change rows); replicate its OBJ_NAME-is-null discipline for classic BOM analytics on the base table.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Header & line
BOM_COMPONENTS_B lines join back to their header BOM_STRUCTURES_B — and the org column — so a line never fans out.
Fields
18 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COMPONENT_SEQUENCE_ID | Surrogate key of the component row | NUMBER | Key |
| 2 | BILL_SEQUENCE_ID | The bill the component belongs to — also where the organization resolves from | NUMBER | |
| 3 | COMPONENT_ITEM_ID | The component item | NUMBER | |
| 4 | OPERATION_SEQ_NUM | The routing operation that consumes the component — 1 when no routing; a value match, not a foreign key | NUMBER | |
| 5 | ITEM_NUM | Sort/display sequence on the bill | NUMBER | |
| 6 | COMPONENT_QUANTITY | Usage quantity per assembly | NUMBER | |
| 7 | COMPONENT_YIELD_FACTOR | Yield factor applied to usage | NUMBER | |
| 8 | EFFECTIVITY_DATE | When the component row becomes effective — the as-of filter column | DATE | Filter date |
| 9 | DISABLE_DATE | When the row stops being effective — NULL while active | DATE | |
| 10 | IMPLEMENTATION_DATE | NULL on unimplemented ECO rows — filter it out for the as-built view | DATE | |
| 11 | PLANNING_FACTOR | Planning percentage for option/model components | NUMBER | |
| 12 | QUANTITY_RELATED | Whether the component quantity is tied to the option quantity | NUMBER | |
| 13 | WIP_SUPPLY_TYPE | Supply method — push, pull, phantom, bulk, supplier; numeric, decode from your instance's manufacturing lookups | NUMBER | |
| 14 | SUPPLY_SUBINVENTORY | Default supply subinventory for issues | VARCHAR2 | |
| 15 | SUPPLY_LOCATOR_ID | Default supply locator | NUMBER | |
| 16 | OPTIONAL | Whether the component is optional on a model bill | NUMBER | |
| 17 | BOM_ITEM_TYPE | Component's BOM item type — standard, model, option class…; numeric, undecoded | NUMBER | |
| 18 | BASIS_TYPE | Item vs lot basis for the usage quantity | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_COMPONENTS_Bon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : BOM_COMPONENTS_B — Single-level bill components — one row per component per operation per effectivity window, with usage quantity, yield, supply type, and the supply subinventory shop-floor issues pull from
-- Purpose: Column-selected read of BOM_COMPONENTS_B — auto-generated from field metadata
-- Grain : One row per COMPONENT_SEQUENCE_ID
-- Caution: Rows are date-effective — the same component reappears per revision window; filter EFFECTIVITY_DATE/DISABLE_DATE around an as-of date (and IMPLEMENTATION_DATE IS NOT NULL) or explosions double-count
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.COMPONENT_SEQUENCE_ID AS "Surrogate key of the component row",
t.BILL_SEQUENCE_ID AS "The bill the component belongs to — also where the organization resolves from",
t.COMPONENT_ITEM_ID AS "The component item",
t.OPERATION_SEQ_NUM AS "The routing operation that consumes the component — 1 when no routing; a value match, not a foreign key",
t.ITEM_NUM AS "Sort/display sequence on the bill",
t.COMPONENT_QUANTITY AS "Usage quantity per assembly",
t.COMPONENT_YIELD_FACTOR AS "Yield factor applied to usage",
t.EFFECTIVITY_DATE AS "When the component row becomes effective — the as-of filter column",
t.DISABLE_DATE AS "When the row stops being effective — NULL while active",
t.IMPLEMENTATION_DATE AS "NULL on unimplemented ECO rows — filter it out for the as-built view",
t.PLANNING_FACTOR AS "Planning percentage for option/model components",
t.QUANTITY_RELATED AS "Whether the component quantity is tied to the option quantity",
t.WIP_SUPPLY_TYPE AS "Supply method — push, pull, phantom, bulk, supplier; numeric, decode from your instance's manufacturing lookups",
t.SUPPLY_SUBINVENTORY AS "Default supply subinventory for issues",
t.SUPPLY_LOCATOR_ID AS "Default supply locator",
t.OPTIONAL AS "Whether the component is optional on a model bill",
t.BOM_ITEM_TYPE AS "Component's BOM item type — standard, model, option class…; numeric, undecoded",
t.BASIS_TYPE AS "Item vs lot basis for the usage quantity"
FROM <catalog>.<schema>.BOM_COMPONENTS_B t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.COMPONENT_SEQUENCE_ID = <COMPONENT_SEQUENCE_ID>
-- AND t.EFFECTIVITY_DATE >= DATE '<DATE_FROM>'
-- AND t.EFFECTIVITY_DATE <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.COMPONENT_SEQUENCE_ID;6 parameters not filled: <catalog>, <schema>, <COMPONENT_SEQUENCE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON BOM_STRUCTURES_B.BILL_SEQUENCE_ID = BOM_COMPONENTS_B.BILL_SEQUENCE_IDON BOM_COMPONENTS_B.COMPONENT_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_IDON BOM_INVENTORY_COMPONENTS.COMPONENT_SEQUENCE_ID = BOM_COMPONENTS_B.COMPONENT_SEQUENCE_ID