Search Results msc_routings




Overview
Explore in AI Chat

Overview

The MSC_ROUTINGS table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the master table for storing routing definitions that are consumed by the planning engine. A routing defines the sequence of manufacturing operations, resources, and materials required to produce an assembly. Within the context of ASCP, this table holds the planning-specific snapshots and versions of routings sourced from the transactional manufacturing systems (e.g., Oracle Bills of Material). Its primary role is to provide the detailed process flow and resource constraints necessary for generating feasible, capacity-aware production plans and schedules.

Key Information Stored

The table's structure centers on uniquely identifying a routing and linking it to the relevant assembly and organizational context. The primary key is a composite of PLAN_ID, ROUTING_SEQUENCE_ID, and SR_INSTANCE_ID, which together ensure uniqueness for a specific routing within a given plan and source system instance. Critical columns include ASSEMBLY_ITEM_ID and ORGANIZATION_ID, which tie the routing to the specific item being built and the manufacturing facility where the operations occur. Other significant attributes often found in this table (implied by its relationships) include data for alternate routings, routing types, effectivity dates, and associated project and task identifiers for project manufacturing scenarios. The SR_INSTANCE_ID is crucial for multi-instance planning setups, denoting the source system from which the data originated.

Common Use Cases and Queries

This table is fundamental for capacity planning, production scheduling, and bottleneck analysis. Planners and analysts query it to understand the manufacturing steps planned for critical items. A common reporting use case is to list all active routings for a specific assembly item within a plan. A typical SQL pattern involves joining with the MSC_SYSTEM_ITEMS table to get item details:

  • SELECT msr.assembly_item_id, msi.item_name, msr.routing_sequence_id, msr.organization_id FROM msc_routings msr, msc_system_items msi WHERE msr.plan_id = :p_plan_id AND msr.assembly_item_id = msi.inventory_item_id AND msr.organization_id = msi.organization_id AND msr.sr_instance_id = msi.sr_instance_id;

Another critical use case is investigating resource requirements by joining MSC_ROUTINGS to MSC_ROUTING_OPERATIONS and MSC_RESOURCE_REQUIREMENTS to analyze the load imposed by a planned order on specific work centers or resources.

Related Objects

MSC_ROUTINGS is a central hub in the ASCP data model with several key dependencies. As per the provided metadata, it has foreign key relationships to MSC_SYSTEM_ITEMS (for the assembly item), MSC_PROJECTS, and MSC_PROJECT_TASKS. Most importantly, it is the parent table for detailed routing data. MSC_ROUTING_OPERATIONS stores the individual operations within each routing, MSC_RESOURCE_REQUIREMENTS holds the resource consumption details for those operations, and MSC_PROCESS_EFFECTIVITY manages date-effective alternate process steps. Any analysis of manufacturing steps in a plan must traverse from MSC_ROUTINGS down through these child tables to build a complete picture of the production process.