BOM_INVENTORY_COMPONENTS
Schema: BOMviewViewThe compatibility view legacy queries know BOM components by — an APPS-schema access layer over the physical components table
APPS-schema view over BOM_COMPONENTS_B. Land the base table for extraction, and verify the view definition in your own instance before reproducing its row set; the public dictionary does not expose a predicate precise enough to prescribe one here.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
9 fields · 1 key
9 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COMPONENT_SEQUENCE_ID | The component row id — identical to the base table's key | NUMBER | Primary-key field |
| 2 | BILL_SEQUENCE_ID | The bill the component belongs to | NUMBER | |
| 3 | COMPONENT_ITEM_ID | The component item | NUMBER | |
| 4 | OPERATION_SEQ_NUM | The consuming routing operation | NUMBER | |
| 5 | COMPONENT_QUANTITY | Usage quantity per assembly | NUMBER | |
| 6 | EFFECTIVITY_DATE | Effectivity start | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 7 | DISABLE_DATE | Effectivity end — NULL while active | DATE | |
| 8 | IMPLEMENTATION_DATE | NULL on unimplemented ECO rows | DATE | |
| 9 | WIP_SUPPLY_TYPE | Supply method — numeric, undecoded | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_INVENTORY_COMPONENTS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
6 parameters not filled: <catalog>, <schema>, <COMPONENT_SEQUENCE_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- Table : BOM_INVENTORY_COMPONENTS — The compatibility view legacy queries know BOM components by — an APPS-schema access layer over the physical components table
-- Purpose: Column-selected read of BOM_INVENTORY_COMPONENTS — auto-generated from field metadata
-- Grain : One row per COMPONENT_SEQUENCE_ID
-- 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. APPS-schema view — land its base tables for extraction; see the table notes.
-- ============================================================
SELECT
t.COMPONENT_SEQUENCE_ID AS "The component row id — identical to the base table's key",
t.BILL_SEQUENCE_ID AS "The bill the component belongs to",
t.COMPONENT_ITEM_ID AS "The component item",
t.OPERATION_SEQ_NUM AS "The consuming routing operation",
t.COMPONENT_QUANTITY AS "Usage quantity per assembly",
t.EFFECTIVITY_DATE AS "Effectivity start",
t.DISABLE_DATE AS "Effectivity end — NULL while active",
t.IMPLEMENTATION_DATE AS "NULL on unimplemented ECO rows",
t.WIP_SUPPLY_TYPE AS "Supply method — numeric, undecoded"
FROM <catalog>.<schema>.BOM_INVENTORY_COMPONENTS 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;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON BOM_INVENTORY_COMPONENTS.COMPONENT_SEQUENCE_ID = BOM_COMPONENTS_B.COMPONENT_SEQUENCE_ID
BOM_INVENTORY_COMPONENTS is an APPS-schema convenience view. Land the base tables it joins instead of extracting from the view directly — views can be slow at scale and aren’t guaranteed stable across patches.
More BOM & Costing tables
- BOM_OPERATION_RESOURCESResources required per routing operation — usage rate, assigned units, and the basis and charge types that drive costing, capacity, and scheduling
- BOM_OPERATION_SEQUENCESRouting operations — one row per operation per routing per effectivity window, department-assigned, with the count-point and backflush controls that decide where work is recorded
- BOM_OPERATIONAL_ROUTINGSThe routing header — one routing per assembly item, organization, and alternate designator, with the common-routing pointer and the completion subinventory finished assemblies land in
- BOM_RESOURCESThe resource master — machines, labor, and outside processing, plus overhead and material sub-elements sharing the table (the cost element discriminates), each with its UOM, charge behavior, and absorption account
- BOM_STRUCTURES_BThe bill-of-material header — one bill per assembly item, organization, and alternate designator (manufacturing or engineering), with the common-bill pointer that lets organizations share one structure
- CST_COST_TYPESThe cost type master — the seeded Frozen, Average, and Pending types plus user-defined types for rollups and simulations, with the fallback pointer rollups use for missing costs