Results for “bom_sub_operation_resources_v”

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

Overview

The APPS.BOM_SUB_OPERATION_RESOURCES_V view is a Bills of Material (BOM) reporting and integration object that exposes substitute resource assignments attached to operation sequences within Oracle E-Business Suite manufacturing structures. It belongs to the BOM product family and carries a VALID status in both 12.1.1 and 12.2.2. The view exists primarily so that substitute resource records held in the BOM_SUB_OPERATION_RESOURCES base table can be presented alongside descriptive attributes sourced from related resource, department, activity, and setup type entities, without requiring callers to reproduce the join logic themselves.

A notable characteristic of this view is its handling of the PRINCIPLE_FLAG column. It is returned as NVL(BOR.PRINCIPLE_FLAG, 2), meaning rows with a null principle flag are surfaced with the default value of 2. This is directly relevant to users searching on "principle_flag," since the view does not return the raw column and instead enforces a default. Reports that interpret principal versus substitute resource roles must therefore be written against the coerced value, not the underlying physical column.

Underlying Base Objects

The view is defined over six documented base objects, all referenced as APPS synonyms: BOM_SUB_OPERATION_RESOURCES, BOM_OPERATION_SEQUENCES, BOM_RESOURCES, BOM_DEPARTMENT_RESOURCES, CST_ACTIVITIES, and BOM_SETUP_TYPES. BOM_SUB_OPERATION_RESOURCES (aliased BOR) is the driving table and supplies the substitute resource rows and the majority of exposed columns.

The joins enforce meaningful restrictions. BOM_OPERATION_SEQUENCES (BOS) is joined on OPERATION_SEQUENCE_ID and constrained by NVL(BOS.OPERATION_TYPE, 1) = 1, so only standard operations are returned. BOM_RESOURCES (BR) supplies RESOURCE_CODE and UOM, while BOM_DEPARTMENT_RESOURCES (BDR) links department and resource so that the resource is validated against the operation's department. CST_ACTIVITIES (CA) is outer-joined on ACTIVITY_ID, and BOM_SETUP_TYPES (BST) is outer-joined on SETUP_ID to supply SETUP_CODE. The outer joins on activities and setup types allow substitute rows without a linked activity or setup to remain visible.

Key Columns

• OPERATION_SEQUENCE_ID — identifies the operation sequence to which the substitute resource belongs.
• RESOURCE_ID / RESOURCE_CODE / UOM — the substitute resource and its unit of measure, derived from BOM_RESOURCES.
• REPLACEMENT_GROUP_NUM / SUBSTITUTE_GROUP_NUM — grouping attributes used to associate interchangeable substitute resources.
• PRINCIPLE_FLAG — returned as NVL(PRINCIPLE_FLAG, 2), distinguishing principal from substitute assignments; nulls are coerced to 2.
• STANDARD_RATE_FLAG, ASSIGNED_UNITS, USAGE_RATE_OR_AMOUNT, USAGE_RATE_OR_AMOUNT_INVERSE, BASIS_TYPE, SCHEDULE_FLAG — resource usage rate and scheduling attributes carried from the base table.
• ACTIVITY / ACTIVITY_ID — optional costing activity, sourced from CST_ACTIVITIES via an outer join.
• SETUP_ID / SETUP_CODE — optional setup type, sourced from BOM_SETUP_TYPES via an outer join.
• RESOURCE_OFFSET_PERCENT, AUTOCHARGE_TYPE, ACD_TYPE, CHANGE_NOTICE, ORIGINAL_SYSTEM_REFERENCE — additional manufacturing and change-control attributes.
• ROW_ID — the ROWID of BOM_SUB_OPERATION_RESOURCES, usable as a unique row handle.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, and the REQUEST_ID / PROGRAM_ID concurrency set.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield segments for extensibility.

Common Use Cases and Queries

This view is typically used to report substitute resource definitions for an operation, to validate department-resource assignments, and to feed integration extracts requiring resource code, UOM, activity, and setup information in a single row. A representative query returning principal and substitute assignments with the coerced flag is:

SELECT OPERATION_SEQUENCE_ID, RESOURCE_CODE, UOM, PRINCIPLE_FLAG, REPLACEMENT_GROUP_NUM, USAGE_RATE_OR_AMOUNT, ACTIVITY, SETUP_CODE FROM APPS.BOM_SUB_OPERATION_RESOURCES_V WHERE OPERATION_SEQUENCE_ID = :p_operation_sequence_id ORDER BY REPLACEMENT_GROUP_NUM, PRINCIPLE_FLAG;

To isolate principal resources only, filter on PRINCIPLE_FLAG = 1, remembering that rows with a null base flag are reported as 2. Because the view already applies the department, resource, and OPERATION_TYPE = 1 restrictions, consumers should not expect it to return resources unrelated to the operation's department, nor non-standard operation types. For operations with no matching activity or setup type, the outer joins return null ACTIVITY and SETUP_CODE values.