Search Results msc_plan_schedules




Overview
Explore in AI Chat

Overview

The MSC_PLAN_SCHEDULES table is a core data repository within the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module. It serves as the primary storage location for master production schedules (MPS) and master demand schedules (MDS), which are fundamental inputs to the planning engine. These schedules define the planned quantities and dates for items, driving the generation of material and resource plans. Furthermore, the table has a specialized role in supporting In Line Vehicle Sequencing (ILVS) functionality within Oracle Supply, where it stores the name of the input production schedule used for sequencing operations.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies a schedule record within the planning context. The key columns are SR_INSTANCE_ID, which identifies the specific instance in a multi-instance deployment; ORGANIZATION_ID, which points to the inventory organization; PLAN_ID, which references the overarching plan definition; and INPUT_SCHEDULE_ID, which is a foreign key to the MSC_DESIGNATORS table and identifies the specific schedule name or designator. While the provided metadata does not list all columns, the primary and foreign key relationships indicate the table stores the critical linkage between a plan, an organization, and the specific schedule data (MPS/MDS) consumed during the planning run.

Common Use Cases and Queries

This table is central to reporting and data validation for planning outputs. Common use cases include auditing which schedules were used as input for a specific plan, identifying all organizations with a master schedule within a plan, and troubleshooting ILVS configurations. A typical query would join to related tables to translate IDs into meaningful names. For example, to list all master schedules for a given plan:

  • SELECT mp.plan_name, mo.organization_code, md.designator
  • FROM msc_plan_schedules mps,
  • msc_plans mp,
  • msc_plan_organizations mo,
  • msc_designators md
  • WHERE mps.plan_id = mp.plan_id
  • AND mps.sr_instance_id = mo.sr_instance_id
  • AND mps.organization_id = mo.organization_id
  • AND mps.plan_id = mo.plan_id
  • AND mps.input_schedule_id = md.designator_id
  • AND mp.plan_id = :p_plan_id;

Related Objects

The MSC_PLAN_SCHEDULES table has documented foreign key relationships with two other critical planning tables, ensuring referential integrity. The primary relationship is with MSC_PLAN_ORGANIZATIONS, linking via the columns PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID. This enforces that a schedule is associated with a valid organization within the plan. The second relationship is with MSC_DESIGNATORS, linked via the INPUT_SCHEDULE_ID column. This join retrieves the descriptive name and type of the schedule (e.g., 'MPS_01'). These relationships are essential for constructing accurate joins in any reporting or data extraction involving master schedule data.