Results for “msc_routing_operations_u1”

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

Overview

MSC.MSC_ROUTING_OPERATIONS is a Plan Central (MSC) schema table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the individual operations that compose each routing as consumed by Advanced Supply Chain Planning (ASCP) and related planning engines. In a discrete or process manufacturing context, a routing describes the sequence of manufacturing steps executed to produce an item. This table captures each of those steps, together with their sequence numbering, effectivity windows, yield characteristics, department ownership, and timing attributes. The data is plan-scoped: every row is tied to a PLAN_ID and a source instance (SR_INSTANCE_ID), which allows the table to hold snapshots of routing operations for multiple plans and multiple source applications simultaneously.

The ETRM metadata classifies this object with a heuristic Data Vault designation of hub-leaning. This suggests that MSC_ROUTING_OPERATIONS functions primarily as a key-bearing entity within the integration model, with business keys anchored around plan, instance, routing, and operation identifiers, while substantial descriptive attributes (yield, durations, effectivity) behave in a satellite-like manner. Modeling exercises should treat the operation identity as the hub and the descriptive planning attributes as dependent, time-variant context.

Key Information Stored

The primary key is documented as MSC_ROUTING_OPERATIONS_PK (SR_INSTANCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQUENCE_ID, PLAN_ID). A separate unique index, MSC_ROUTING_OPERATIONS_U1, extends the business key with NEW_PLAN_ID and SIMULATION_SET_ID, reflecting the plan-comparison and simulation features of ASCP. Two nonunique indexes, MSC_ROUTING_OPERATIONS_N1 and MSC_ROUTING_OPERATIONS_N2, support access paths on operation sequence and routing sequence plus operation sequence number respectively.

• PLAN_ID – Identifier of the plan owning this routing operation record; a core partitioning key.
• SR_INSTANCE_ID – Source application instance identifier, disambiguating data sourced from multiple EBS instances.
• ROUTING_SEQUENCE_ID – Surrogate identifier of the parent routing (foreign key to MSC_ROUTINGS).
• OPERATION_SEQUENCE_ID – Surrogate identifier of the operation itself.
• OPERATION_SEQ_NUM – Ordinal position of the operation within the routing sequence.
• OPERATION_DESCRIPTION – Text description used in UI and reports.
• EFFECTIVITY_DATE / DISABLE_DATE – Validity window for the operation.
• FROM_UNIT_NUMBER / TO_UNIT_NUMBER – Unit-number effectivity range for serialized contexts.
• YIELD / CUMULATIVE_YIELD / REVERSE_CUMULATIVE_YIELD – Process yield at the operation, cumulative yield from routing start, and cumulative yield to routing start (reverse).
• DEPARTMENT_ID / DEPARTMENT_CODE – Owning department, with foreign key to BOM_DEPARTMENTS.
• MINIMUM_TRANSFER_QUANTITY – Minimum transfer quantity governing operation hand-off.
• SETUP_DURATION / TEAR_DOWN_DURATION – Operation timing components used in planning.
• OPERATION_TYPE – Process, Line, or Event classification (events excluded here).
• NEW_PLAN_ID / SIMULATION_SET_ID – Simulation and plan-comparison identifiers aligned with the U1 unique key.

Common Use Cases and Queries

Typical reporting selects operations for a plan, routing, and source instance. A representative query joining to the parent routing is:

• SELECT o.ROUTING_SEQUENCE_ID, o.OPERATION_SEQ_NUM, o.OPERATION_DESCRIPTION, o.YIELD, o.CUMULATIVE_YIELD FROM MSC.MSC_ROUTING_OPERATIONS o WHERE o.PLAN_ID = :plan AND o.SR_INSTANCE_ID = :inst ORDER BY o.ROUTING_SEQUENCE_ID, o.OPERATION_SEQ_NUM;
• Yielding analysis aggregates CUMULATIVE_YIELD across operations to derive end-to-end effective yield for a routing.
• Effectivity investigations filter on EFFECTIVITY_DATE and DISABLE_DATE to identify operations active on a given date.
• Simulation comparison queries join on the U1 columns (NEW_PLAN_ID, SIMULATION_SET_ID) to compare baseline and simulated routings.
• Department workload reporting groups by DEPARTMENT_ID/DEPARTMENT_CODE and sums SETUP_DURATION and TEAR_DOWN_DURATION.

Related Objects

• MSC.MSC_ROUTINGS – Parent of the routing; joined via PLAN_ID (and routing sequence keys).
• BOM.BOM_DEPARTMENTS – Referenced through DEPARTMENT_ID for department definitions.
• MSC.MSC_OPERATION_NETWORKS – Child table recording operation precedence networks; references this table via PLAN_ID.
• MSC.MSC_OPERATION_RESOURCE_SEQS – Child table recording resources per operation; references via PLAN_ID.
• MSC.MSC_OPERATION_COMPONENTS – Child table recording components consumed at operations; references via PLAN_ID.

Together these dependencies position MSC_ROUTING_OPERATIONS as the central operation-level anchor within the MSC planning data model, linking routing structure, resources, components, and operation networks for ASCP computations.