Search Results bom_op_resources_view




Overview
Explore in AI Chat

Overview

BOM_OP_RESOURCES_VIEW is an APPS-owned database view in the Oracle E-Business Suite Bills of Material (BOM) module. It presents a flattened, reporting-ready representation of operation resources — the resources assigned to routing operations within a bill of materials. In EBS 12.1.1 and 12.2.2, routing data is distributed across several normalized base tables (routings, operation sequences, resources, and operation resource assignments), and reconstructing a readable view of these relationships requires multi-table joins. BOM_OP_RESOURCES_VIEW performs that consolidation, exposing resource assignments together with their parent routing, operation sequence, department, and assembly context in a single queryable object.

The view is catalogued in ETRM with a status of VALID and is documented as the "Operation resources view." Its primary role is to support reporting, data extraction, and integration scenarios where consumers need operation-resource detail without navigating the base schema directly. Because it joins descriptive flexfield and lookup-decoded values into the result set, it is particularly useful for ad hoc reporting and downstream interfaces.

Underlying Base Objects

The view is defined over the following documented objects, all referenced through APPS synonyms:

The joins key resources to operation resources, operation resources to operation sequences, sequences to departments and routings, and routings to the item flexfield view by organization and assembly item. Lookup decoding is applied to autocharge type, standard rate flag, basis type, and schedule flag.

Key Columns

Common Use Cases and Queries

Typical uses include routing resource reports, cost rollup feed extracts, and integration queries that need resource assignments per operation. A representative query lists resources for a given assembly in an organization:

  • SELECT operation_seq_num, department_code, resource_code, assigned_units, usage_rate_or_amount FROM bom_op_resources_view WHERE organization_id = :org_id AND assembly_item_id = :item_id ORDER BY operation_seq_num, resource_seq_num;
  • SELECT resource_code, schedule_flag, basis_type, usage_rate_or_amount FROM bom_op_resources_view WHERE organization_id = :org_id AND routing_type = 1;
  • SELECT department_code, operation_seq_num, COUNT(*) FROM bom_op_resources_view WHERE organization_id = :org_id GROUP BY department_code, operation_seq_num;

Because the lookup columns are decoded at runtime through INV_MEANING_SEL, results reflect current lookup meanings. Report consumers should filter by ORGANIZATION_ID and assembly item to avoid full-table scans across the underlying routing tables.