Skip to content
EBS Reference

BOM_RESOURCES

Schema: BOMmasterPer inventory org

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

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

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.

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

13 fields · 1 key

13 fields.

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1RESOURCE_IDSurrogate key of the resourceNUMBER
Primary-key field
2RESOURCE_CODEThe resource code users see — unique per org and cost code typeVARCHAR2
3ORGANIZATION_IDInventory organizationNUMBER
4DESCRIPTIONResource descriptionVARCHAR2
5RESOURCE_TYPEMachine, person, and other kinds — numeric, undecodedNUMBER
6UNIT_OF_MEASUREThe resource's UOM — currency-unit resources carry a currency code hereVARCHAR2
7COST_ELEMENT_IDThe cost element the resource charges — also what separates real resources from overhead sub-elements in this tableNUMBER
8DEFAULT_BASIS_TYPEDefault item-vs-lot basisNUMBER
9STANDARD_RATE_FLAGWhether charges use the standard rateNUMBER
10ALLOW_COSTS_FLAGWhether the resource may carry costsNUMBER
11ABSORPTION_ACCOUNTThe absorption account (CCID) charges creditNUMBER
12RATE_VARIANCE_ACCOUNTThe rate variance account (CCID)NUMBER
13DISABLE_DATEWhen the resource was disabled — NULL while activeDATE

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.

Query parameters

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

  • BOM_OPERATION_RESOURCESBOM_RESOURCESforeign key · N:1
    ON BOM_OPERATION_RESOURCES.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID
  • BOM_RESOURCESMTL_PARAMETERSforeign key · N:1
    ON BOM_RESOURCES.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_ID
  • BOM_RESOURCESGL_CODE_COMBINATIONSforeign key · N:1
    ON BOM_RESOURCES.ABSORPTION_ACCOUNT = GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
  • CST_ITEM_COST_DETAILSBOM_RESOURCESforeign key · N:1
    ON CST_ITEM_COST_DETAILS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND CST_ITEM_COST_DETAILS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_ID
  • WIP_TRANSACTIONSBOM_RESOURCESforeign key · N:1
    ON WIP_TRANSACTIONS.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID AND WIP_TRANSACTIONS.ORGANIZATION_ID = BOM_RESOURCES.ORGANIZATION_ID

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.