Results for “bombv_rtg_operation_resources”

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

Overview

APPS.BOMBV_RTG_OPERATION_RESOURCES is a read-only view in the Bills of Material (BOM) product module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It is documented in the ETRM repository as "Retrofitted," indicating that it originated in an earlier EBS release and was carried forward into the current code line without functional redesign. The view consolidates routing, operation, and resource assignment data into a single denormalized projection suitable for inquiry, reporting, and integration rather than for transactional maintenance. It joins the operational routing header, the operation sequence detail, and the operation resource assignment to present one row per resource assigned to an operation within a routing.

The object exposes the operation sequence number as OPERATION_SEQUENCE_NUMBER, which is the identifier most commonly used by report writers and interface developers to sequence and correlate resources against their parent operation. Organization context is supplied through both the organization code and organization name, and the assembly is represented by a key flexfield reference column rather than a literal item name.

The view is defined WITH READ ONLY, so it cannot be used for inserts or updates; DML must be directed at the underlying base tables.

Underlying Base Objects

The documented base objects referenced by the view are, with the exception of the organization units table, exposed through synonyms in the APPS schema: BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_RESOURCES, BOM_OPERATION_SEQUENCES, HR_ALL_ORGANIZATION_UNITS, MTL_PARAMETERS, and MTL_SYSTEM_ITEMS. The joins establish the following relationships:

• BOM_OPERATIONAL_ROUTINGS to BOM_OPERATION_SEQUENCES on ROUTING_SEQUENCE_ID, giving the operation level.
• BOM_OPERATION_SEQUENCES to BOM_OPERATION_RESOURCES on OPERATION_SEQUENCE_ID, giving the assigned resource level.
• BOM_OPERATIONAL_ROUTINGS to MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS on ORGANIZATION_ID, supplying the organization code and name.
• BOM_OPERATIONAL_ROUTINGS to MTL_SYSTEM_ITEMS on ASSEMBLY_ITEM_ID and ORGANIZATION_ID, supplying the assembly item context.

A security predicate on OP.ORGANIZATION_ID is embedded in the WHERE clause, so the view is filtered to operations whose organization the caller is permitted to see. This makes it appropriate for multi-organization reporting without additional organization access logic.

Key Columns

• OPERATION_SEQUENCE_NUMBER — the sequence number of the operation within the routing; the primary search key for users locating resources by operation.
• RESOURCE_SEQUENCE_NUMBER — the ordering of the resource within the operation.
• EFFECTIVE_START_DATE — the effectivity date of the operation sequence.
• ALTERNATE_ROUTING_CODE — the alternate routing designator.
• ORGANIZATION_CODE and ORGANIZATION_NAME — organization identifiers sourced from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• "_KF:ROUTING_ITEM_NAME" — a flexfield reference column for the assembly item, resolved by the reporting tool rather than returned as plain text.
• USAGE_RATE_OR_AMOUNT and INVERSE_RATE_OR_AMOUNT — resource usage expressed in the assigned basis, with its inverse.
• ASSIGNED_UNITS — the number of units charged for the resource.
• OFFSET_PERCENT — the resource offset percent, typically used for scheduling lead or lag.
• Lookup-derived columns such as "_LA:AUTOCHARGE_FLAG", "_LA:RESOURCE_BASIS_TYPE", "_LA:SCHEDULE_FLAG", and "_LA:STANDARD_RATE_FLAG" — decoded from MFG_LOOKUPS at runtime.
• OPERATION_SEQUENCE_ID, ROUTING_SEQUENCE_ID, RESOURCE_ID, and ACTIVITY_ID — surrogate keys supporting joins to related views and tables.
• CREATED_ON, CREATED_BY, UPDATED_ON, and UPDATED_BY — audit columns.

Common Use Cases and Queries

Typical uses include routing cost and capacity analysis, resource load reporting, and export of routing structures for external planning systems. A common pattern filters by organization and alternate routing, then orders by operation sequence:

SELECT operation_sequence_number, resource_sequence_number, alternate_routing_code, usage_rate_or_amount, assigned_units, offset_percent FROM apps.bombv_rtg_operation_resources WHERE organization_code = :org AND alternate_routing_code = :alt ORDER BY operation_sequence_number, resource_sequence_number;

A second pattern joins the surrogate keys back to detail views for resource names and basis codes:

SELECT v.operation_sequence_number, r.resource_code, v.usage_rate_or_amount FROM apps.bombv_rtg_operation_resources v, apps.bom_resources r WHERE r.resource_id = v.resource_id AND v.organization_code = :org;

Because operation_sequence_number is returned as a numeric sequence rather than a surrogate identifier, it is the natural key for grouping, sorting, and matching resources to operation-level reporting output.