Results for “msc_operations”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_OPERATION_NETWORKS is a child table of MSC_OPERATIONS in the MSC (Advanced Supply Chain Planning) schema. It describes the network structure of operations within a network routing, capturing the directed transitions between operations on a routing. Where a standard routing implies a linear sequence of operations, a network routing permits convergent, divergent, and dependent flows, and this table is the structure that records those connections. Each row represents a single from-to relationship between two operations belonging to the same routing, plan, and source instance.

The table stores planning data extracted or calculated by the Advanced Supply Chain Planning engine rather than transactional production data, so it is transient and plan-scoped: rows carry PLAN_ID and SIMULATION_SET_ID and are refreshed during plan runs. Under a heuristic Data Vault classification derived from its foreign key topology, this object is best modeled as a link table — it resolves a many-to-many association between operations (from-operation and to-operation) within the context of a routing, plan, and source instance, and it therefore carries the dependent key of the relationships it connects alongside descriptive attributes.

Key Information Stored

The primary key is MSC_OPERATION_NETWORKS_PK, composed of PLAN_ID, ROUTING_SEQUENCE_ID, TO_OP_SEQ_ID, FROM_OP_SEQ_ID, and SR_INSTANCE_ID. A second unique index, MSC_OPERATION_NETWORKS_U1, extends the business-key space with additional columns including TO_ROUTING_SEQUENCE_ID, FROM_ITEM_ID, NEW_PLAN_ID, and SIMULATION_SET_ID, reflecting the planning-simulation dimension of the data. The most significant columns are:

• PLAN_ID — identifies the plan owning the network row; part of the primary key.
• ROUTING_SEQUENCE_ID — the routing to which the connected operations belong.
• FROM_OP_SEQ_ID / TO_OP_SEQ_ID — the two operations joined by the network arc, forming the core link semantics.
• FROM_OP_SEQ_NUM / TO_OP_SEQ_NUM — denormalized sequence numbers for the respective operations.
• SR_INSTANCE_ID — source instance identifier for multi-instance planning.
• TO_ROUTING_SEQUENCE_ID — supports transitions that cross routing boundaries.
• TRANSITION_TYPE and DEPENDENCY_TYPE — classify how one operation flows to the next and the dependency rule applied.
• MINIMUM_TIME_OFFSET / MAXIMUM_TIME_OFFSET — lead-time window constraints between the two operations.
• MINIMUM_TRANSFER_QTY, TRANSFER_QTY, TRANSFER_UOM, TRANSFER_PCT — quantity transfer rules between operations.
• PLANNING_PCT and CUMMULATIVE_PCT — percentage-of-planning allocation applied to the transition.
• EFFECTIVITY_DATE / DISABLE_DATE — effective dating of the network arc.
• NEW_PLAN_ID and SIMULATION_SET_ID — simulation and plan-copy context.
• ORGANIZATION_ID, APPLIED, APPLY_TO_CHARGES — organizational scoping and whether charges apply.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield columns for extensibility.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — standard audit fields.

Common Use Cases and Queries

Typical usage centers on analyzing network routing topology, diagnosing planning explosions or scheduling errors, and reporting on operation dependencies. A representative query joins the network table back to its operations:

SELECT n.PLAN_ID, n.ROUTING_SEQUENCE_ID, n.FROM_OP_SEQ_NUM, n.TO_OP_SEQ_NUM, n.TRANSITION_TYPE FROM MSC.MSC_OPERATION_NETWORKS n WHERE n.PLAN_ID = :plan_id AND n.ROUTING_SEQUENCE_ID = :routing_seq_id ORDER BY n.TO_OP_SEQ_NUM;

Because the table is plan-scoped, most reports filter on PLAN_ID and SIMULATION_SET_ID to isolate a single planning run or simulation. Common analytical scenarios include identifying all successors of a given operation (traverse FROM_OP_SEQ_ID to TO_OP_SEQ_ID), measuring cumulative planning percentages across a network, and validating that lead-time offsets fall within acceptable bounds before releasing schedules. Querying by SR_INSTANCE_ID is essential in multi-source environments. Bulk extraction for downstream planning dashboards is often performed by materializing rows for a specific PLAN_ID into a staging table.

Related Objects

The FK metadata ties this table to two parent relationships against MSC_ROUTING_OPERATIONS, joined on the combination of PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID, and either FROM_OP_SEQ_ID or TO_OP_SEQ_ID. This dual dependency confirms that every network row references two distinct routing operations. Significant related objects include:

• MSC_OPERATIONS — parent table whose operations the network rows connect.
• MSC_ROUTING_OPERATIONS — referenced by both FROM_OP_SEQ_ID and TO_OP_SEQ_ID through the composite foreign keys.
• MSC_ROUTINGS — provides the routing header that ROUTING_SEQUENCE_ID resolves to.
• MSC_PLANS — the plan definition referenced by PLAN_ID and governing row lifecycle.
• MSC_SR_INSTANCES — source instance master linked by SR_INSTANCE_ID.
• MSC_SIMULATION_SETS — simulation context referenced by SIMULATION_SET_ID for what-if comparisons.

Most access to this object occurs indirectly through the Advanced Supply Chain Planning concurrent programs that populate and purge network rows, and through planning engines that read the table when exploding network routings. Direct DML is not supported; the data is managed by the planning application.