Results for “bombv_std_opratn_resources”

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

Overview

The APPS.BOMBV_STD_OPRATN_RESOURCES view is a read-only reporting object within the Oracle E-Business Suite Bills of Material (BOM) module. It presents resource assignments attached to standard operations, combining resource sequencing, usage rates, and organizational context into a single denormalized result set. The view carries the "Retrofitted" designation in the ETRM metadata, indicating it was introduced or re-platformed as part of Oracle's transition toward a business view (BV) layer that isolates reporting consumers from direct dependency on base transaction tables. In releases 12.1.1 and 12.2.2, this view serves as a stable interface for custom reports, Discoverer workbooks, BI Publisher data templates, and downstream integrations that require standard operation resource detail without joining the underlying operational tables manually. The user's search term, resource_sequence_number, maps directly to the first column of the view, which is derived from RE.RESOURCE_SEQ_NUM on the base resource table.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

• BOM_STD_OP_RESOURCES (aliased RE) — the driving table holding resource assignments, rates, and sequence numbers for each standard operation.
• BOM_STANDARD_OPERATIONS (aliased OP) — supplies the operation code and organization identifier for each standard operation.
• HR_ALL_ORGANIZATION_UNITS (aliased AL) — provides the organization name.
• MTL_PARAMETERS (aliased PA) — provides the organization code.

The joins are keyed on ORGANIZATION_ID across MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, and BOM_STANDARD_OPERATIONS, with RE.STANDARD_OPERATION_ID linking resources to their parent operation. The final predicate, '_SEC:OP.ORGANIZATION_ID' IS NOT NULL, enforces organization-level security (MOAC) by restricting results to organizations the querying responsibility is authorized to access. The view is declared WITH READ ONLY, so it cannot be used as a DML target.

Key Columns

• RESOURCE_SEQUENCE_NUMBER — the sequence in which the resource is consumed or applied within the operation; directly answers the search term.
• ORGANIZATION_CODE / ORGANIZATION_NAME — the plant identifier and descriptive name for the owning organization.
• OPERATION_CODE — the standard operation to which the resource belongs.
• USAGE_RATE_OR_AMOUNT / INVERSE_RATE_OR_AMOUNT — the resource consumption rate and its inverse, used in costing and capacity calculations.
• ASSIGNED_UNITS — the number of units of the resource assigned to the operation.
• "_LA:AUTOCHARGE_TYPE", "_LA:BASIS_TYPE", "_LA:SCHEDULE_FLAG", "_LA:STANDARD_RATE_FLAG" — lookup-backed attributes whose literal strings instruct the EBS framework to resolve meanings from MFG_LOOKUPS (BOM_AUTOCHARGE_TYPE, CST_BASIS, SYS_YES_NO).
• STANDARD_OPERATION_ID, RESOURCE_ID, ACTIVITY_ID — surrogate keys for joining back to base entities.
• UPDATED_ON / UPDATED_BY / CREATED_ON / CREATED_BY — audit columns sourced from the resource record.

Common Use Cases and Queries

Typical scenarios include reporting resource loading per standard operation, validating usage rates prior to cost rollup, and exporting operation-resource structures for MES or third-party scheduling systems. The AUDIT columns and "_LA:" columns are frequently omitted in extracts because their literal values are not meaningful outside the EBS lookup framework.

A representative query retrieving resource sequences for a given operation and organization:

• SELECT resource_sequence_number, organization_code, operation_code, usage_rate_or_amount, assigned_units FROM apps.bombv_std_opratn_resources WHERE operation_code = :operation_code AND organization_code = :org_code ORDER BY resource_sequence_number;

Because row visibility is governed by the MOAC predicate embedded in the view, results are automatically filtered to the organizations accessible to the connected responsibility, making the view suitable for multi-org aware reporting without additional WHERE clause restrictions.