Skip to content
EBS Reference

BOM_BILL_OF_MATERIALS

Schema: BOMviewPer inventory orgView

The compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i name

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

APPS-schema view over BOM_STRUCTURES_B — land the base table for extraction; this entry exists so the familiar name resolves.

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

6 fields · 1 key

6 fields.

Table fields: position, field name, description, data type, and flags. 6 fields.
#FieldDescriptionTypeFlags
1BILL_SEQUENCE_IDThe bill id — identical to the base table's keyNUMBER
Primary-key field
2ASSEMBLY_ITEM_IDThe assembly itemNUMBER
3ORGANIZATION_IDOwning inventory organizationNUMBER
4ALTERNATE_BOM_DESIGNATORNULL for the primary billVARCHAR2
5ASSEMBLY_TYPEManufacturing vs engineering billNUMBER
6COMMON_BILL_SEQUENCE_IDThe shared bill pointerNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading BOM_BILL_OF_MATERIALS 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

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <BILL_SEQUENCE_ID>, <watermark>

-- ============================================================
-- Table  : BOM_BILL_OF_MATERIALS — The compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i name
-- Purpose: Column-selected read of BOM_BILL_OF_MATERIALS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + BILL_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.BILL_SEQUENCE_ID AS "The bill id — identical to the base table's key",
  t.ASSEMBLY_ITEM_ID AS "The assembly item",
  t.ORGANIZATION_ID AS "Owning inventory organization",
  t.ALTERNATE_BOM_DESIGNATOR AS "NULL for the primary bill",
  t.ASSEMBLY_TYPE AS "Manufacturing vs engineering bill",
  t.COMMON_BILL_SEQUENCE_ID AS "The shared bill pointer"
FROM <catalog>.<schema>.BOM_BILL_OF_MATERIALS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.BILL_SEQUENCE_ID = <BILL_SEQUENCE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.BILL_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_BILL_OF_MATERIALSBOM_STRUCTURES_Bforeign key · 1:1
    ON BOM_BILL_OF_MATERIALS.BILL_SEQUENCE_ID = BOM_STRUCTURES_B.BILL_SEQUENCE_ID AND BOM_BILL_OF_MATERIALS.ORGANIZATION_ID = BOM_STRUCTURES_B.ORGANIZATION_ID
Extraction note

BOM_BILL_OF_MATERIALS 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.