Search Results from_operation_code




Overview
Explore in AI Chat

Overview

The BOM_OPERATION_NETWORKS_V view is an APPS-owned database view in the Oracle E-Business Suite Bills of Material (BOM) module. Its documented description is "Operation networks view." The view exposes the relationships, or networks, that connect operations within a manufacturing routing. Specifically, it joins each network transition record from the underlying BOM_OPERATION_NETWORKS table to both the source ("from") and destination ("to") operation sequences, resolving the descriptive details of each endpoint.

In the EBS 12.1.1 and 12.2.2 schema, this view is typically consumed by reporting, integration, and planning extracts that need a denormalized, human-readable representation of operation flow. Rather than requiring the caller to independently join network records to two separate operation-sequence rows and to the standard-operations and departments tables, the view performs this resolution in a single object. It also provides denormalized endpoint attributes such as operation codes, operation descriptions, department codes, and effectivity dates.

Underlying Base Objects

The ETRM 12.2.2 metadata identifies the following referenced base objects, all accessed through synonyms in the APPS schema: BOM_DEPARTMENTS, BOM_OPERATION_NETWORKS, BOM_OPERATION_SEQUENCES, BOM_STANDARD_OPERATIONS, and the WSMPUTIL package.

The view text confirms this structure. BOM_OPERATION_NETWORKS is the driving table, aliased BON, supplying the transition records. It is joined to two instances of BOM_OPERATION_SEQUENCES (BOS1 for the from-operation, BOS2 for the to-operation) on FROM_OP_SEQ_ID and TO_OP_SEQ_ID respectively. Two instances of BOM_DEPARTMENTS (BD1, BD2) supply the department codes for each endpoint. Two outer-joined instances of BOM_STANDARD_OPERATIONS (BSO1, BSO2) supply standard operation codes where a standard operation is referenced.

The view relies on the WSMPUTIL package functions GET_EFF_STDOP_ID and GET_EFF_DEPT_ID to resolve the effective standard operation identifier and effective department identifier, ensuring that the correct effectivity-dated reference records are used for each operation sequence.

Key Columns

Common Use Cases and Queries

A frequent requirement is to report operation networks together with their planning percentages. The following query lists transitions for a routing, including the planning percentage:

  • SELECT from_seq_num, from_operation_code, to_seq_num, to_operation_code, transition_type, planning_pct FROM apps.bom_operation_networks_v WHERE routing_sequence_id = :p_routing_seq_id;

To identify transitions carrying a specific planning percentage:

  • SELECT routing_sequence_id, from_seq_num, to_seq_num, planning_pct FROM apps.bom_operation_networks_v WHERE planning_pct = :p_pct;

Integration extracts often denormalize endpoint descriptions for downstream manufacturing execution or shop-floor systems:

  • SELECT from_operation_code, from_operation_desc, from_dept_code, to_operation_code, to_operation_desc, to_dept_code FROM apps.bom_operation_networks_v WHERE routing_sequence_id = :p_routing_seq_id ORDER BY from_seq_num, to_seq_num;

Because the view already resolves effective standard operations and departments, these queries avoid the manual joins otherwise required against BOM_OPERATION_SEQUENCES, BOM_STANDARD_OPERATIONS, and BOM_DEPARTMENTS.