Search Results operation_description




Overview
Explore in AI Chat

Overview

The APPS.BOM_OPERATION_NETWORKS_V view exposes the directed operation network defined within an Oracle E-Business Suite manufacturing routing. It presents each network transition — the movement from a From operation sequence to a To operation sequence — alongside the descriptive attributes of both endpoint operations, so that a single row fully describes one edge of the routing graph. Because it denormalizes the operation and department descriptions onto the transition record, the view is well suited to reporting, integration, and diagnostic queries that require readable operation descriptions rather than raw surrogate identifiers.

The object is owned by APPS and is defined over synonyms to the underlying BOM tables. It is not a base table; it carries no independent storage and reflects only the effective operation definitions resolved at query time.

Underlying Base Objects

The view is defined over the following documented objects:

  • BOM_OPERATION_NETWORKS (BON) — the driving table, supplying the network edge itself (FROM_OP_SEQ_ID, TO_OP_SEQ_ID, TRANSITION_TYPE, PLANNING_PCT, and the standard WHO columns).
  • BOM_OPERATION_SEQUENCES (BOS1, BOS2) — joined as the From (FROM_OP_SEQ_ID) and To (TO_OP_SEQ_ID) operation sequences respectively, supplying sequence numbers, effectivity dates, operation descriptions, and standard operation references.
  • BOM_STANDARD_OPERATIONS (BSO1, BSO2) — outer-joined to the From and To sequences to obtain the standard operation code and description.
  • BOM_DEPARTMENTS (BD1, BD2) — joined to return the department code for each endpoint operation.
  • WSMPUTIL (PACKAGE) — its get_eff_stdop_id and get_eff_dept_id functions resolve the effective standard operation and department for a given operation sequence, which is why the joins to BSO1 and BD1 are function-based rather than direct.

Key Columns

Common Use Cases and Queries

Typical uses include routing network reports, operation precedence analysis, and integration extracts where operation descriptions are required without additional lookups.

  • List all transitions for a routing with readable descriptions:
SELECT routing_sequence_id,
       from_seq_num, from_operation_desc, from_dept_code,
       to_seq_num,   to_operation_desc,   to_dept_code,
       transition_type, planning_pct
FROM   apps.bom_operation_networks_v
WHERE  routing_sequence_id = :routing_sequence_id
ORDER  BY from_seq_num, to_seq_num;
  • Search transitions by operation description, the primary use of the searched term:
SELECT from_operation_code, from_operation_desc,
       to_operation_code,   to_operation_desc
FROM   apps.bom_operation_networks_v
WHERE  UPPER(from_operation_desc) LIKE UPPER('%'||:description||'%')
OR     UPPER(to_operation_desc)   LIKE UPPER('%'||:description||'%');

Because FROM_OPERATION_DESC and TO_OPERATION_DESC are resolved dynamically through the DECODE expression and the WSMPUTIL function calls, queries against description columns do not benefit from simple column indexes; filtering on FROM_OP_SEQ_ID, TO_OP_SEQ_ID, or ROUTING_SEQUENCE_ID is generally more efficient.