Results for “msc_routing_operations”

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

Overview

MSC_ROUTING_OPERATIONS is a planning table within the MSC (Advanced Supply Chain Planning) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual operations that compose a routing, forming the operation-level detail beneath the routing header held in MSC_ROUTINGS. Each row represents one operation within a specific routing sequence for a given plan, source instance, and simulation context. The table supports the planning engine's representation of manufacturing and process routings, capturing sequence numbers, yields, resource-relevant durations, department assignment, and planning flags that drive capacity and scheduling calculations.

From a Data Vault modeling perspective, the heuristic classification of this table is hub-leaning. That is, its primary key structure (SR_INSTANCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, PLAN_ID) behaves largely like a hub of unique operation identities within a planning context, with dependent descriptive attributes acting as satellite content. This classification is a modeling suggestion drawn from the FK topology, not a statement of Oracle's internal design.

Key Information Stored

The primary key, MSC_ROUTING_OPERATIONS_PK, is a composite surrogate key of SR_INSTANCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, and PLAN_ID. A separate unique index, MSC_ROUTING_OPERATIONS_U1, defines a broader business-key candidate: PLAN_ID, SR_INSTANCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, NEW_PLAN_ID, and SIMULATION_SET_ID.

• PLAN_ID — the planning instance to which the operation belongs; also an FK to MSC_ROUTINGS.
• ROUTING_SEQUENCE_ID / OPERATION_SEQUENCE_ID — identify the parent routing and the specific operation within it.
• OPERATION_SEQ_NUM — the display/execution sequence of the operation in the routing.
• DEPARTMENT_ID / DEPARTMENT_CODE — the department performing the operation; DEPARTMENT_ID references BOM_DEPARTMENTS.
• OPERATION_TYPE — classification of the operation (for example, standard versus non-standard).
• YIELD, CUMULATIVE_YIELD, REVERSE_CUMULATIVE_YIELD — yield percentages at the operation and cumulative levels, central to planning scrap and net quantity calculations.
• NET_PLANNING_PERCENT — the percentage of the operation considered in net planning.
• SETUP_DURATION, TEAR_DOWN_DURATION, OPERATION_LEAD_TIME_PERCENT, MINIMUM_TRANSFER_QUANTITY, STEP_QUANTITY, STEP_QUANTITY_UOM — duration, transfer, and step-quantity attributes used by the scheduler and capacity engine.
• STANDARD_OPERATION_CODE — the reference standard operation.
• EFFECTIVITY_DATE / DISABLE_DATE — the effective window of the operation.
• USE_IN_PLAN — flag indicating whether the operation participates in the plan.
• ORGANIZATION_ID — the inventory organization context.
• NEW_PLAN_ID, NEW_PLAN_LIST, APPLIED, SIMULATION_SET_ID, REFRESH_NUMBER — planning refresh and simulation bookkeeping columns.

Common Use Cases and Queries

Typical uses include reporting routing operation content for a plan, verifying yields and durations feeding the planning engine, and tracing operation dependencies through MSC_OPERATION_NETWORKS. A representative query lists operations for a routing:

• SELECT operation_sequence_id, operation_seq_num, department_code, yield, cumulative_yield, setup_duration, tear_down_duration, use_in_plan FROM msc_routing_operations WHERE plan_id = :p_plan AND routing_sequence_id = :p_routing AND sr_instance_id = :p_src ORDER BY operation_seq_num;
• Join to MSC_ROUTINGS on PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID to report routing headers with their operation counts.
• Join to BOM_DEPARTMENTS on DEPARTMENT_ID to resolve department descriptions for capacity reporting.
• Join to MSC_OPERATION_RESOURCE_SEQS on PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID, OPERATION_SEQUENCE_ID to analyze resource loading per operation.

Related Objects

• MSC_ROUTINGS — parent routing header; joined on PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID.
• MSC_OPERATION_NETWORKS — operation-to-operation dependencies; references this table via FROM_OP_SEQ_ID and TO_OP_SEQ_ID along with PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID.
• MSC_OPERATION_RESOURCE_SEQS — resource requirements per operation; joined on PLAN_ID, ROUTING_SEQUENCE_ID, SR_INSTANCE_ID, OPERATION_SEQUENCE_ID.
• MSC_OPERATION_COMPONENTS — component assignments per operation; joined on the same four key columns.
• BOM_DEPARTMENTS — department reference for DEPARTMENT_ID.