BOM_OPERATION_RESOURCES
Schema: BOMmasterResources required per routing operation — usage rate, assigned units, and the basis and charge types that drive costing, capacity, and scheduling
No single-column key: the working key is the operation plus the resource sequence number (the physical unique index adds the change-type and basis columns). No org column — it resolves through the routing.
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
12 fields · 2 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | OPERATION_SEQUENCE_ID | The routing operation the resource is assigned to — working key with the resource sequence | NUMBER | Primary-key field |
| 2 | RESOURCE_SEQ_NUM | Resource sequence within the operation — working key with the operation | NUMBER | Primary-key field |
| 3 | RESOURCE_ID | The resource being used | NUMBER | |
| 4 | ACTIVITY_ID | Costing activity | NUMBER | |
| 5 | ASSIGNED_UNITS | Units of the resource assigned | NUMBER | |
| 6 | USAGE_RATE_OR_AMOUNT | Usage rate or fixed amount per basis | NUMBER | |
| 7 | USAGE_RATE_OR_AMOUNT_INVERSE | The inverse form of the usage rate | NUMBER | |
| 8 | BASIS_TYPE | Item vs lot basis for the usage | NUMBER | |
| 9 | SCHEDULE_FLAG | Whether the resource is scheduled | NUMBER | |
| 10 | AUTOCHARGE_TYPE | How the resource charges as work moves — numeric, undecoded | NUMBER | |
| 11 | STANDARD_RATE_FLAG | Whether charges use the standard rate | NUMBER | |
| 12 | RESOURCE_OFFSET_PERCENT | Lead-time offset of the resource within the routing | NUMBER |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading BOM_OPERATION_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>, <OPERATION_SEQUENCE_ID>, <RESOURCE_SEQ_NUM>, <watermark>
-- ============================================================
-- Table : BOM_OPERATION_RESOURCES — Resources required per routing operation — usage rate, assigned units, and the basis and charge types that drive costing, capacity, and scheduling
-- Purpose: Column-selected read of BOM_OPERATION_RESOURCES — auto-generated from field metadata
-- Grain : One row per OPERATION_SEQUENCE_ID + RESOURCE_SEQ_NUM
-- 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.OPERATION_SEQUENCE_ID AS "The routing operation the resource is assigned to — working key with the resource sequence",
t.RESOURCE_SEQ_NUM AS "Resource sequence within the operation — working key with the operation",
t.RESOURCE_ID AS "The resource being used",
t.ACTIVITY_ID AS "Costing activity",
t.ASSIGNED_UNITS AS "Units of the resource assigned",
t.USAGE_RATE_OR_AMOUNT AS "Usage rate or fixed amount per basis",
t.USAGE_RATE_OR_AMOUNT_INVERSE AS "The inverse form of the usage rate",
t.BASIS_TYPE AS "Item vs lot basis for the usage",
t.SCHEDULE_FLAG AS "Whether the resource is scheduled",
t.AUTOCHARGE_TYPE AS "How the resource charges as work moves — numeric, undecoded",
t.STANDARD_RATE_FLAG AS "Whether charges use the standard rate",
t.RESOURCE_OFFSET_PERCENT AS "Lead-time offset of the resource within the routing"
FROM <catalog>.<schema>.BOM_OPERATION_RESOURCES t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.OPERATION_SEQUENCE_ID = <OPERATION_SEQUENCE_ID>
-- AND t.RESOURCE_SEQ_NUM = <RESOURCE_SEQ_NUM>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.OPERATION_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
ON BOM_OPERATION_RESOURCES.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_IDON BOM_OPERATION_RESOURCES.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID
More BOM & Costing tables
- BOM_OPERATION_SEQUENCESRouting operations — one row per operation per routing per effectivity window, department-assigned, with the count-point and backflush controls that decide where work is recorded
- BOM_OPERATIONAL_ROUTINGSThe routing header — one routing per assembly item, organization, and alternate designator, with the common-routing pointer and the completion subinventory finished assemblies land in
- BOM_RESOURCESThe 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
- 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