Search Results msc_operation_networks_v




Overview
Explore in AI Chat

Overview

MSC_OPERATION_NETWORKS_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Advanced Supply Chain Planning module (MSC). It presents the complete set of operation-to-operation transitions that make up a network routing used by the planning engine. In Advanced Supply Chain Planning, a routing defines the sequence of manufacturing or process operations required to produce an item. Where a simple routing models a single linear path, a network routing allows operations to be connected through multiple predecessor and successor relationships, supporting convergent and divergent flows.

The view flattens these relationships into a readable, denormalised form. Rather than exposing raw sequence identifiers, it resolves both the originating ("from") and destination ("to") operations into their operation sequence numbers and standard operation codes. It also translates the internal numeric transition type into the descriptive values PRIMARY and ALTERNATE. Because the view is defined with the APPS schema and is marked VALID, it can be queried directly by custom reports, extracts, and integrations requiring visibility into planned operation networks. It is a read-only, non-updatable construct; it edits nothing and is intended purely for query and reporting.

Underlying Base Objects

The view is defined over three core objects. MSC_OPERATION_NETWORKS supplies the network links themselves and contributes the row identifier, routing, plan, source instance, from/to sequence identifiers, transition type, planning percentage, audit columns, and the fifteen descriptive flexfield attributes. It is joined twice to MSC_ROUTING_OPERATIONS — once as MRO1 for the "from" operation and once as MRO2 for the "to" operation — which resolves the sequence numbers and standard operation codes on each side of the transition.

The three tables are joined on a composite key that ensures consistency: FROM_OP_SEQ_ID and TO_OP_SEQ_ID match OPERATION_SEQUENCE_ID, while PLAN_ID, SR_INSTANCE_ID, and ROUTING_SEQUENCE_ID must match across all three aliases. This guarantees that both endpoints of every link belong to the same plan, source instance, and routing. Additionally, the ETRM dependency listing references the package MSC_GET_NAME, which supplies lookup or name-resolution logic, and MSC_OPERATION_NETWORKS is exposed in the APPS schema as a synonym.

Key Columns

Common Use Cases and Queries

Typical uses include documenting the routing topology for a plan, identifying alternate paths, and validating that planned networks reconcile to source routings.

SELECT from_seq_num, from_operation_code,
       to_seq_num, to_operation_code,
       transition_type, planning_pct
FROM   apps.msc_operation_networks_v
WHERE  plan_id = :p_plan_id
ORDER  BY from_seq_num, to_seq_num;

To isolate alternate transitions or audit a specific operation, filter on TRANSITION_TYPE = 'ALTERNATE' or on FROM_OPERATION_CODE. Because the view is non-updatable, all usage is confined to SELECT reporting and data extraction.