BOM_RESOURCES
Schema: BOMmasterPer inventory orgThe 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
Not everything here is a schedulable resource — overhead and material-overhead sub-elements live in the same table; check COST_ELEMENT_ID before treating rows as capacity.
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
13 fields · 1 key
13 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | RESOURCE_ID | Surrogate key of the resource | NUMBER | Primary-key field |
| 2 | RESOURCE_CODE | The resource code users see — unique per org and cost code type | VARCHAR2 | |
| 3 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 4 | DESCRIPTION | Resource description | VARCHAR2 | |
| 5 | RESOURCE_TYPE | Machine, person, and other kinds — numeric, undecoded | NUMBER | |
| 6 | UNIT_OF_MEASURE | The resource's UOM — currency-unit resources carry a currency code here | VARCHAR2 | |
| 7 | COST_ELEMENT_ID | The cost element the resource charges — also what separates real resources from overhead sub-elements in this table | NUMBER | |
| 8 | DEFAULT_BASIS_TYPE | Default item-vs-lot basis | NUMBER | |
| 9 | STANDARD_RATE_FLAG | Whether charges use the standard rate | NUMBER | |
| 10 | ALLOW_COSTS_FLAG | Whether the resource may carry costs | NUMBER | |
| 11 | ABSORPTION_ACCOUNT | The absorption account (CCID) charges credit | NUMBER | |
| 12 | RATE_VARIANCE_ACCOUNT | The rate variance account (CCID) | NUMBER | |
| 13 | DISABLE_DATE | When the resource was disabled — NULL while active | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading BOM_RESOURCES 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.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <RESOURCE_ID>, <watermark>
-- ============================================================
-- Table : BOM_RESOURCES — The 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
-- Purpose: Column-selected read of BOM_RESOURCES — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + RESOURCE_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.
-- ============================================================
SELECT
t.RESOURCE_ID AS "Surrogate key of the resource",
t.RESOURCE_CODE AS "The resource code users see — unique per org and cost code type",
t.ORGANIZATION_ID AS "Inventory organization",
t.DESCRIPTION AS "Resource description",
t.RESOURCE_TYPE AS "Machine, person, and other kinds — numeric, undecoded",
t.UNIT_OF_MEASURE AS "The resource's UOM — currency-unit resources carry a currency code here",
t.COST_ELEMENT_ID AS "The cost element the resource charges — also what separates real resources from overhead sub-elements in this table",
t.DEFAULT_BASIS_TYPE AS "Default item-vs-lot basis",
t.STANDARD_RATE_FLAG AS "Whether charges use the standard rate",
t.ALLOW_COSTS_FLAG AS "Whether the resource may carry costs",
t.ABSORPTION_ACCOUNT AS "The absorption account (CCID) charges credit",
t.RATE_VARIANCE_ACCOUNT AS "The rate variance account (CCID)",
t.DISABLE_DATE AS "When the resource was disabled — NULL while active"
FROM <catalog>.<schema>.BOM_RESOURCES t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.RESOURCE_ID = <RESOURCE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.RESOURCE_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_OPERATION_RESOURCES.RESOURCE_ID = BOM_RESOURCES.RESOURCE_IDON BOM_RESOURCES.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_IDON BOM_RESOURCES.ABSORPTION_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_IDON CST_ITEM_COST_DETAILS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_IDON WIP_TRANSACTIONS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_ID
More BOM & Costing tables
- 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
- CST_ITEM_COST_DETAILSThe cost-element breakdown under each item cost — one row per element, level, and department/operation/resource contribution; where a rolled-up cost's ingredients live
- CST_ITEM_COSTSThe item cost header — one row per item, organization, and cost type, carrying the total unit cost and its five cost-element buckets plus this-level/previous-level splits
- BOM_BILL_OF_MATERIALSThe compatibility view legacy queries know BOM headers by — a window onto the structures table under the familiar 11i name
- BOM_COMPONENTS_BSingle-level bill components — one row per component per operation per effectivity window, with usage quantity, yield, supply type, and the supply subinventory shop-floor issues pull from