Search Results msc_dependency_type

Overview

APPS.MSC_OPERATION_NETWORKS_V is a reporting and integration view within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. It exposes the operation-to-operation dependency network defined for a routing within a given planning run, presenting the predecessor and successor operations together with the transition semantics that govern material flow between them. The view is a denormalized, presentation-oriented layer over the MSC_OPERATION_NETWORKS base table, resolving surrogate identifiers into human-readable sequence numbers and standard operation codes, and translating internal lookup codes into descriptive meanings.

Because the source routing operations table carries operation-level attributes such as net_planning_percent, the view serves as the primary access point for planners and integrators who need to understand how operation networks are structured under a plan, including the timing offsets, dependency types, and transfer or planning percentages applied across each network edge. The user search term net_planning_percent maps directly to columns projected from MSC_ROUTING_OPERATIONS in this view.

Underlying Base Objects

The view is defined over three documented objects: the MSC_OPERATION_NETWORKS synonym (backed by the MSC_OPERATION_NETWORKS table), the MSC_ROUTING_OPERATIONS synonym (backed by the MSC_ROUTING_OPERATIONS table), and the MSC_GET_NAME package, which supplies lookup translations.

The driving table, MSC_OPERATION_NETWORKS (aliased MON), holds one row per network edge, keyed by routing_sequence_id, plan_id, sr_instance_id, and the from/to operation sequence identifiers. The view joins this table twice to a distinct projection of MSC_ROUTING_OPERATIONS (aliased MRO1 for the predecessor operation and MRO2 for the successor operation), matching on operation_seq_num, plan_id, sr_instance_id, and routing_sequence_id. A critical filter restricts the result set to networks where from_item_id is null, meaning the view reports only operation-level (item-independent) network definitions rather than item-specific overrides. The MSC_GET_NAME package is invoked to decode the MSC_TRANSITION_TYPE, MSC_DEPENDENCY_TYPE, and SYS_YES_NO lookups.

Key Columns

• row_id, routing_sequence_id, plan_id, sr_instance_id — identifying keys linking the network to its routing, plan, and source instance.
• from_op_seq_id / to_op_seq_id and the corresponding operation_seq_num and standard_operation_code from MRO1 and MRO2 — the predecessor and successor operations bounding each network edge.
• nvl(mon.planning_pct, mon.transfer_pct) — the effective planning percentage applied to the network, defaulting to transfer percentage when planning percentage is absent.
• mro1.net_planning_percent — the net planning percent of the predecessor operation, projected directly from MSC_ROUTING_OPERATIONS.
• transition_type, dependency_type, apply_to_charges — decoded lookup meanings describing the nature of the transition, the dependency relationship, and whether charges apply.
• minimum_time_offset / maximum_time_offset — timing bounds between operations.
• transfer_pct — the raw transfer percentage retained alongside the derived planning value.
• creation_date, created_by, last_update_date, last_updated_by, last_update_login, attribute_category, attribute1–attribute15 — standard audit and descriptive flexfield columns.

Common Use Cases and Queries

Typical usage includes validating routing network definitions before a plan run, analyzing operation dependencies, and exporting network structures to external planning or MES systems. The net_planning_percent and planning/transfer percentage columns are frequently queried to verify yield or scrap assumptions propagating between operations.

• List all network edges for a plan and routing:

  SELECT operation_seq_num, standard_operation_code, net_planning_percent,
         minimum_time_offset, maximum_time_offset
  FROM   apps.msc_operation_networks_v
  WHERE  plan_id = :plan_id
  AND    routing_sequence_id = :routing_seq_id;

• Inspect effective planning versus transfer percentages across a network.
• Audit transition and dependency types decoded from MSC_TRANSITION_TYPE and MSC_DEPENDENCY_TYPE.
• Feed downstream integration extracts where human-readable operation codes and lookup meanings are required.

Because the view filters on from_item_id IS NULL, queries intended to capture item-specific overrides must reach the base MSC_OPERATION_NETWORKS table directly rather than this view.