Results for “bom_std_op_resources”

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

Overview

BOM_STD_OP_RESOURCES is a standard Bills of Material table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the resource requirements attached to standard operations defined within Oracle Bills of Material and Oracle Manufacturing. A standard operation represents a reusable template of work performed at the routing or department level. Each row in BOM_STD_OP_RESOURCES equates one bill of resources line to a specific standard operation, capturing the resource, the usage rate, the basis for charging, and the scheduling characteristics associated with that operation.

The table is registered as VALID in the ETRM repository and forms part of the engineering and manufacturing foundation used to generate routings, standard operation assignments, and costing rollups. From a Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. This suggests that the table behaves primarily as a descriptive satellite recording attributes over time, dependent on a parent business entity rather than acting as an independent hub or a pure junction link.

Key Information Stored

The documented physical schema contains 39 columns. The most significant include the following:

• STANDARD_OPERATION_ID and RESOURCE_SEQ_NUM — together form the composite primary key through BOM_STD_OP_RESOURCES_PK and the unique index BOM_STD_OP_RESOURCES_U1, identifying the resource line within a standard operation.
• RESOURCE_ID — the resource being consumed or applied at the operation.
• ACTIVITY_ID — foreign key to CST_ACTIVITIES, tying the resource to a costing activity.
• USAGE_RATE_OR_AMOUNT and USAGE_RATE_OR_AMOUNT_INVERSE — the quantity or rate consumed, stored in both forward and inverse directions to support different calculation paths.
• BASIS_TYPE and AUTOCHARGE_TYPE — define how the resource usage is charged or derived (for example, per unit, per item, or based on activity).
• STANDARD_RATE_FLAG — indicates whether a standard rate applies to the resource.
• ASSIGNED_UNITS — the number of units assigned to the resource line.
• SCHEDULE_FLAG and SCHEDULE_SEQ_NUM — control whether the resource participates in scheduling and its sequence.
• SUBSTITUTE_GROUP_NUM and PRINCIPLE_FLAG — support substitute resource grouping and principal-versus-alternate designation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield columns.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, and the PROGRAM/REQUEST_ID audit columns — track who and what process created or last modified each row.

Common Use Cases and Queries

This table is central to standard operation resource reporting, resource consumption analysis, and costing integration. Typical queries retrieve all resources for a given standard operation id, or join to CST_ACTIVITIES for activity-based costing detail.

• Extracting resources for a standard operation: SELECT * FROM BOM.BOM_STD_OP_RESOURCES WHERE STANDARD_OPERATION_ID = :op_id ORDER BY RESOURCE_SEQ_NUM;
• Activity-based costing linkage: SELECT r.STANDARD_OPERATION_ID, r.RESOURCE_ID, a.ACTIVITY_ID FROM BOM.BOM_STD_OP_RESOURCES r, CST.CST_ACTIVITIES a WHERE r.ACTIVITY_ID = a.ACTIVITY_ID;
• Audit and change tracking using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Identifying principal versus substitute resources through PRINCIPLE_FLAG and SUBSTITUTE_GROUP_NUM.

Related Objects

• CST_ACTIVITIES — joined on ACTIVITY_ID; supplies costing activity context.
• BOM_STANDARD_OPERATIONS — the parent standard operation entity referenced by STANDARD_OPERATION_ID.
• BOM_OPERATION_RESOURCES — the routing-level counterpart holding operation resources.
• BOM_STD_OP_RESOURCE_BD and related _TL / _BD tables — DFF and translation storage for resource definitions.
• Oracle Manufacturing APIs such as BOM_STD_OP_PUB and routing interfaces that consume these resource rows when creating routings and standard operations.

Together, these relationships confirm the table's role as a satellite resource detail store anchored to standard operations and costing activities within the Oracle BOM and Cost Management ecosystems.