Skip to content
EBS Reference

BOM_INVENTORY_COMPONENTS

Schema: BOMviewView

The compatibility view legacy queries know BOM components by — an APPS-schema access layer over the physical components table

Identity
Module: BOM & CostingNot org-partitioned
Fusion equivalents (2)
Notes

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with ORGANIZATION_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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

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.
In field listings, the Key chip marks a primary-key field.

Fields

9 fields · 1 key

9 fields.

Table fields: position, field name, description, data type, and flags. 9 fields.
#FieldDescriptionTypeFlags
1COMPONENT_SEQUENCE_IDThe component row id — identical to the base table's keyNUMBER
Primary-key field
2BILL_SEQUENCE_IDThe bill the component belongs toNUMBER
3COMPONENT_ITEM_IDThe component itemNUMBER
4OPERATION_SEQ_NUMThe consuming routing operationNUMBER
5COMPONENT_QUANTITYUsage quantity per assemblyNUMBER
6EFFECTIVITY_DATEEffectivity startDATE
The table's primary analysis date — a real DATE column, no conversion needed
7DISABLE_DATEEffectivity end — NULL while activeDATE
8IMPLEMENTATION_DATENULL on unimplemented ECO rowsDATE
9WIP_SUPPLY_TYPESupply method — numeric, undecodedNUMBER

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.

Query parameters

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

  • BOM_INVENTORY_COMPONENTSBOM_COMPONENTS_Bforeign key · 1:1
    ON BOM_INVENTORY_COMPONENTS.COMPONENT_SEQUENCE_ID = BOM_COMPONENTS_B.COMPONENT_SEQUENCE_ID
Extraction note

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.

Browse more BOM & Costing tables

More BOM & Costing tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.