BOM_BILL_OF_MATERIALS
Schema: BOMviewPer inventory orgViewThe compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i name
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
6 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | BILL_SEQUENCE_ID | The bill id — identical to the base table's key | NUMBER | Key |
| 2 | ASSEMBLY_ITEM_ID | The assembly item | NUMBER | |
| 3 | ORGANIZATION_ID | Owning inventory organization | NUMBER | |
| 4 | ALTERNATE_BOM_DESIGNATOR | NULL for the primary bill | VARCHAR2 | |
| 5 | ASSEMBLY_TYPE | Manufacturing vs engineering bill | NUMBER | |
| 6 | COMMON_BILL_SEQUENCE_ID | The shared bill pointer | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_BILL_OF_MATERIALSon 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_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;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <BILL_SEQUENCE_ID>, <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_BILL_OF_MATERIALS.BILL_SEQUENCE_ID = BOM_STRUCTURES_B.BILL_SEQUENCE_ID AND BOM_BILL_OF_MATERIALS.ORGANIZATION_ID = BOM_STRUCTURES_B.ORGANIZATION_ID
BOM_BILL_OF_MATERIALSis 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.