Search Results bomfv_operation_networks




Overview
Explore in AI Chat

Overview

BOMFV_OPERATION_NETWORKS is an APPS-owned, VALID view in the Oracle E-Business Suite Bills of Material (BOM) module. It is documented in ETRM as a retrofitted object, meaning it was re-implemented against the current 12.1.1 / 12.2.2 data model while preserving the interface expected by earlier releases. The view exposes the network of directed connections between operation sequences within manufacturing routings. Each row describes a single edge — a "from" operation sequence linked to a "to" operation sequence — together with the transition type, planning percentage, and effectivity window governing that link.

Because it resolves foreign keys into descriptive attributes (organization code and name, routing alternate designator, item context, and operation sequence numbers), the view is suited to operational reporting, routing analysis, and integration extracts. The user search term "from_operation_seq_num" corresponds directly to the view's FROM_OPERATION_SEQ_NUM column, which is the natural predicate for tracing predecessor operations on a routing.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through APPS synonyms:

The join path is anchored on BOM_OPERATION_NETWORKS: NE.FROM_OP_SEQ_ID equals SQ1.OPERATION_SEQUENCE_ID and NE.TO_OP_SEQ_ID equals SQ2.OPERATION_SEQUENCE_ID. Each operation sequence is then linked to its routing via ROUTING_SEQUENCE_ID, each routing to its assembly item via ASSEMBLY_ITEM_ID and ORGANIZATION_ID, and each organization to both MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS via ORGANIZATION_ID. This structure permits the same view to represent intra-organization and cross-organization routing networks.

Key Columns

Two hidden key-flex columns, _KF:ROUTING_FROM_ITEM_NAME and _KF:ROUTING_TO_ITEM_NAME, are exposed for descriptive flexfield integration.

Common Use Cases and Queries

Typical scenarios include reporting all networks that originate from a given operation sequence, reconciling routing transitions across organizations, and extracting connection data for MES or scheduling integration.

To trace all successors of a specific operation sequence number within an organization:

  • SELECT from_operation_seq_num, to_operation_seq_num, connection_type, planning_percent, from_organization_code, to_organization_code FROM bomfv_operation_networks WHERE from_operation_seq_num = :seq_num AND from_organization_code = :org_code;

To inspect the full network for an organization, including effectivity:

  • SELECT from_operation_seq_num, to_operation_seq_num, connection_type, planning_percent, start_effective_date, end_effective_date FROM bomfv_operation_networks WHERE from_organization_code = :org_code ORDER BY from_operation_seq_num, to_operation_seq_num;

To identify cross-organization connections and their alternate routings:

  • SELECT from_organization_code, to_organization_code, from_alternate_routing_code, to_alternate_routing_code, connection_type FROM bomfv_operation_networks WHERE from_organization_code <> to_organization_code;

For change auditing, the UPDATED_ON, UPDATED_BY, CREATED_ON, and CREATED_BY columns support incremental extracts. Because the view resolves organizations and routings into readable values, it is generally preferable to the underlying BOM_OPERATION_NETWORKS table for reporting, while direct table access remains appropriate for high-volume batch processing where join overhead is a concern.