Skip to content
EBS Reference

BOM_OPERATION_RESOURCES

Schema: BOMmaster

Resources required per routing operation — usage rate, assigned units, and the basis and charge types that drive costing, capacity, and scheduling

Module: BOM & CostingNot org-partitioned
Notes

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

12 fields · 2 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1OPERATION_SEQUENCE_IDThe routing operation the resource is assigned to — working key with the resource sequenceNUMBER
Key
2RESOURCE_SEQ_NUMResource sequence within the operation — working key with the operationNUMBER
Key
3RESOURCE_IDThe resource being usedNUMBER
4ACTIVITY_IDCosting activityNUMBER
5ASSIGNED_UNITSUnits of the resource assignedNUMBER
6USAGE_RATE_OR_AMOUNTUsage rate or fixed amount per basisNUMBER
7USAGE_RATE_OR_AMOUNT_INVERSEThe inverse form of the usage rateNUMBER
8BASIS_TYPEItem vs lot basis for the usageNUMBER
9SCHEDULE_FLAGWhether the resource is scheduledNUMBER
10AUTOCHARGE_TYPEHow the resource charges as work moves — numeric, undecodedNUMBER
11STANDARD_RATE_FLAGWhether charges use the standard rateNUMBER
12RESOURCE_OFFSET_PERCENTLead-time offset of the resource within the routingNUMBER

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

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

Query parameters
-- ============================================================
-- 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;

5 parameters not filled: <catalog>, <schema>, <OPERATION_SEQUENCE_ID>, <RESOURCE_SEQ_NUM>, <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

  • BOM_OPERATION_RESOURCESBOM_OPERATION_SEQUENCESforeign key · N:1
    ON BOM_OPERATION_RESOURCES.OPERATION_SEQUENCE_ID = BOM_OPERATION_SEQUENCES.OPERATION_SEQUENCE_ID
  • BOM_OPERATION_RESOURCESBOM_RESOURCESforeign key · N:1
    ON BOM_OPERATION_RESOURCES.RESOURCE_ID = BOM_RESOURCES.RESOURCE_ID

Browse more BOM & Costingtables →

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.