BOM_INVENTORY_COMPONENTS
Schema: BOMviewViewThe compatibility view legacy queries know BOM components by — a filtered window onto the components table that hides PLM-object and unimplemented-change rows
APPS-schema view over BOM_COMPONENTS_B — and a FILTERED one, so counts differ from the base table by design. Land BOM_COMPONENTS_B for extraction and apply the classic-row filter yourself.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
9 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | COMPONENT_SEQUENCE_ID | The component row id — identical to the base table's key | NUMBER | Key |
| 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 | Filter date |
| 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_COMPONENTSon 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_INVENTORY_COMPONENTS — The compatibility view legacy queries know BOM components by — a filtered window onto the components table that hides PLM-object and unimplemented-change rows
-- 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;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_INVENTORY_COMPONENTS.COMPONENT_SEQUENCE_ID = BOM_COMPONENTS_B.COMPONENT_SEQUENCE_ID
BOM_INVENTORY_COMPONENTSis 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.