Results for “bom_operation_resources”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM.BOM_OPERATION_RESOURCES is the Oracle EBS Bills of Material table that stores the resource assignments attached to routing operations. Each row defines a specific resource — such as labor, machine, or equipment — consumed at a given operation sequence within a manufacturing routing. The table carries a VALID status in the BOM schema and is a core component of the manufacturing routing data model, bridging operation sequences and costed activities. In Oracle EBS 12.1.1 and 12.2.2 the structure is consistent, with the 12.2.2 release documenting 44 physical columns under owner BOM.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This reflects its role: rows describe attributes and properties that depend on the parent operation sequence rather than acting as an independent business hub. Any downstream analytical model should treat BOM_OPERATION_RESOURCES as a dependent detail table keyed to its parent operation.

Key Information Stored

The documented primary key is BOM_OPERATION_RESOURCES_PK, composed of OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM. This surrogate composite uniquely identifies each resource line within an operation. A secondary unique index, BOM_OPERATION_RESOURCES_U2, spans OPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM, ACD_TYPE, and BASIS_TYPE, indicating a business-key candidate that distinguishes resource lines by activity/cost and basis dimension.

• OPERATION_SEQUENCE_ID — Foreign key to the parent routing operation in BOM_OPERATION_SEQUENCES.
• RESOURCE_SEQ_NUM — Sequence number assigning the resource within the operation.
• RESOURCE_ID — The resource being used at this operation.
• ACTIVITY_ID — Foreign key to CST_ACTIVITIES, linking the resource to a costing activity.
• ASSIGNED_UNITS — Number of resource units assigned, such as machines or employees.
• USAGE_RATE_OR_AMOUNT and USAGE_RATE_OR_AMOUNT_INVERSE — Usage quantity or rate and its inverse for consumption calculations.
• BASIS_TYPE — Determines whether usage is based on item quantity or resource time.
• ACD_TYPE — Activity/cost driver classification participating in the unique business key.
• STANDARD_RATE_FLAG and SCHEDULE_FLAG — Flags controlling rate costing and scheduling participation.
• SETUP_ID — Foreign key to BOM_SETUP_TYPES for setup-dependent resources.
• RESOURCE_OFFSET_PERCENT and SUBSTITUTE_GROUP_NUM — Scheduling offsets and substitute resource grouping.
• PRINCIPLE_FLAG, AUTOCHARGE_TYPE, and CHANGE_NOTICE — Behavioral and engineering change controls.
• Audit columns including LAST_UPDATE_DATE, CREATED_BY, and the ATTRIBUTE1–ATTRIBUTE15 DFF set.

Common Use Cases and Queries

Typical usage includes routing resource reporting, capacity and cost roll-up, and resource utilization analysis. A common query joins the resource assignments back to their parent operation and the host bill:

• List all resources for a given routing operation by joining BOM_OPERATION_RESOURCES to BOM_OPERATION_SEQUENCES on OPERATION_SEQUENCE_ID.
• Roll up assigned units and usage rates per operation to compute capacity and labor/machine loading.
• Extract resource-to-activity mappings by joining to CST_ACTIVITIES on ACTIVITY_ID for costed bill analysis.
• Trace capacity hour rollups by joining to CRP_RESOURCE_HOURS on OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM.

A representative pattern is SELECT r.OPERATION_SEQUENCE_ID, r.RESOURCE_SEQ_NUM, r.RESOURCE_ID, r.ASSIGNED_UNITS FROM BOM_OPERATION_RESOURCES r WHERE r.OPERATION_SEQUENCE_ID = :op_seq. Reporting on BASIS_TYPE and ACD_TYPE supports routing consistency audits.

Related Objects

• BOM_OPERATION_SEQUENCES — Parent object; joined via OPERATION_SEQUENCE_ID.
• CST_ACTIVITIES — Referenced via ACTIVITY_ID for costing activity linkage.
• BOM_SETUP_TYPES — Referenced via SETUP_ID for setup-type resources.
• CRP_RESOURCE_HOURS — Child/dependent table referencing this object on OPERATION_SEQUENCE_ID and RESOURCE_SEQ_NUM.
• Bills of Material and routing APIs (for example, the BOM_ROUTING_PUB interfaces) that create and maintain operation resource data.