Search Results bombv_operation_networks




Overview
Explore in AI Chat

Overview

BOMBV_OPERATION_NETWORKS is a read-only Oracle EBS view owned by the APPS schema and registered under the Bills of Material (BOM) product family. It exposes the operation network relationships defined between routing operations, resolving the foreign keys held in BOM_OPERATION_NETWORKS into descriptive business attributes such as organization codes, organization names, item names, alternate routing designators, operation sequence numbers and effectivity dates. The view is documented as "Retrofitted" in ETRM, indicating it was introduced or re-registered to preserve backward compatibility for customers and integrations migrating from earlier releases to 12.1.1 or 12.2.2.

Functionally, the view answers the question "which routing operation feeds which other routing operation, and where do they physically occur?" Because operation networks can span organizations in a multi-plant environment, the view presents both a FROM side and a TO side for every network row. This makes it the principal reporting surface for flow manufacturing and routing network analysis, and a common dependency in custom concurrent programs, BI Publisher reports, OBIEE repositories and interface extracts.

Underlying Base Objects

The view is defined over six documented base objects, all referenced through APPS synonyms:

Each base table is joined twice, aliased with a numeric suffix for the FROM side and the TO side. The join path anchors the network row to two operation sequences via FROM_OP_SEQ_ID and TO_OP_SEQ_ID, then walks up to their parent routings, assemblies and organizations.

Key Columns

Common Use Cases and Queries

The view is typically queried to report cross-organization routing flows, to validate network setup prior to a manufacturing release, and to extract data for planning or MES integration. A representative query filtering on the TO organization name is:

  • SELECT from_organization_name, to_organization_name, from_operation_seq_num, to_operation_seq_num, connection_type, planning_percent FROM apps.bombv_operation_networks WHERE to_organization_name = :p_org;
  • SELECT to_organization_code, COUNT(*) FROM apps.bombv_operation_networks GROUP BY to_organization_code;
  • SELECT * FROM apps.bombv_operation_networks WHERE from_routing_sequence_id = :routing_id ORDER BY to_operation_seq_num;

Because the view is defined WITH READ ONLY, it supports query and extraction workloads only; no DML is permitted. Report authors should be aware that each row represents a single transition edge rather than a discrete operation, and that organizations appear twice per row, so filters on organization must specify the FROM or TO column explicitly to avoid double counting.