Results for “bom_stp_std_op_resources_v”

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

Overview

The BOM_STP_STD_OP_RESOURCES_V view is an Oracle EBS Bills of Material (BOM) reporting object owned by the APPS schema. It presents the resources assigned to standard operations, filtered specifically to standard operations of operation type 4. The view consolidates resource-level attributes — sequence, usage rate, basis type, autocharge behavior, scheduling information, and descriptive flexfield attributes — into a single denormalized structure suitable for reporting, validation, and integration.

The object is central to manufacturing engineering and cost rollup inquiries: standard operations define reusable routing steps, and the resources attached to them carry the labor, machine, and overhead consumption rates used by the cost rollup and by work-in-process execution. Because the view joins resource master data with department-level resource assignments, it also exposes the AVAILABLE_24_HOURS_FLAG attribute, the column most frequently referenced by users searching this object. That flag indicates whether the resource, in the context of its assigned department, is considered available around the clock for capacity and scheduling calculations.

Underlying Base Objects

The view is defined over the following base objects, all exposed in APPS as synonyms:

• BOM_STD_OP_RESOURCES — the driving table, holding the resource assignment for each standard operation, including sequence and usage details.
• BOM_RESOURCES — resource master, supplying the resource code and unit of measure.
• BOM_STANDARD_OPERATIONS — standard operation header; the join includes the filter BSO.OPERATION_TYPE = 4, restricting output to standard operations of that type.
• BOM_DEPARTMENT_RESOURCES — department-to-resource assignment; this is the source of AVAILABLE_24_HOURS_FLAG.
• CST_ACTIVITIES — activity definition, joined with an outer join (CA.ACTIVITY_ID(+)) so that resources without an associated activity are still returned.

The joins are: BSOR.RESOURCE_ID = BR.RESOURCE_ID; BDR.DEPARTMENT_ID = BSO.DEPARTMENT_ID and BDR.RESOURCE_ID = BSOR.RESOURCE_ID; and BSOR.STANDARD_OPERATION_ID = BSO.STANDARD_OPERATION_ID.

Key Columns

• ROW_ID — row identifier derived from the base table, useful for updates through INSTEAD-OF triggers.
• STANDARD_OPERATION_ID / OPERATION_TYPE — identifies the parent standard operation; operation type is constrained to 4.
• RESOURCE_ID / RESOURCE_CODE / UNIT_OF_MEASURE — resource identity and its usage unit of measure.
• RESOURCE_SEQ_NUM, USAGE_RATE_OR_AMOUNT, USAGE_RATE_OR_AMOUNT_INVERSE, BASIS_TYPE — sequencing and consumption basis for the resource.
• AUTOCHARGE_TYPE, STANDARD_RATE_FLAG, ASSIGNED_UNITS, SCHEDULE_FLAG — costing and scheduling behavior attributes.
• AVAILABLE_24_HOURS_FLAG — sourced from BOM_DEPARTMENT_RESOURCES; indicates 24-hour availability of the resource in the department.
• ACTIVITY_ID / ACTIVITY — the cost activity associated with the resource, where defined.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield columns from the standard operation resource assignment.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include routing and standard operation resource reports, capacity planning extracts, cost rollup verification, and identifying resources flagged for 24-hour availability.

• List resources for a given standard operation with usage and basis detail.
• Filter resources whose AVAILABLE_24_HOURS_FLAG is set, supporting scheduling and capacity studies.
• Join to cost activities to analyze activity-driven overhead consumption.

Sample query:

SELECT standard_operation_id, resource_code, unit_of_measure, resource_seq_num, usage_rate_or_amount, basis_type, available_24_hours_flag, activity, schedule_flag, autocharge_type
FROM apps.bom_stp_std_op_resources_v
WHERE standard_operation_id = :p_std_op_id
ORDER BY resource_seq_num;