Search Results msc_plans




Overview
Explore in AI Chat

Overview

The MSC_PLANS table is a core master data table within the Oracle Advanced Supply Chain Planning (ASCP) and Oracle Supply Chain Planning modules of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central repository for defining and storing the metadata for every planning run or scenario. Each record in this table represents a distinct plan, which is a fundamental entity used to execute, manage, and analyze supply chain planning outputs. The table holds the plan's name, critical configuration settings, and its operational status, acting as the primary reference point for all subsequent planning data and transactions associated with that specific plan instance.

Key Information Stored

The table's primary key is the PLAN_ID, a unique system-generated identifier for each plan. While the provided metadata does not list all columns, based on its central role, the table typically stores essential attributes such as the PLAN_NAME, COMPILE_DESIGNATOR, PLAN_TYPE (e.g., ASCP, DRP), and status flags indicating whether the plan is active or frozen. It also contains foreign key relationships that link the plan to its configuration. Notably, the metadata confirms the presence of an ASSIGNMENT_SET_ID (linking to MSC_ASSIGNMENT_SETS) which defines sourcing and assignment rules, and an ORGANIZATION_ID (linking to HZ_PARTIES) which identifies the owning or master planning organization.

Common Use Cases and Queries

This table is fundamental for administrative queries, data validation, and integration reporting. Common use cases include listing all available plans for a user interface, validating a plan's existence before launching a data snapshot or plan run, and generating reports on plan usage. A typical query retrieves basic plan information for a specific plan name or type.

SELECT plan_id, plan_name, compile_designator, organization_id
FROM msc_plans
WHERE plan_type = 'ASCP'
  AND NVL(disable_date, SYSDATE+1) > SYSDATE
ORDER BY creation_date DESC;

Another critical use is to join with child tables, such as MSC_PLAN_ORGANIZATIONS, to retrieve the full list of organizations included in a specific plan's scope.

Related Objects

As the central planning entity, MSC_PLANS has numerous dependent objects. The provided metadata specifies several foreign key relationships. It is referenced as a parent table by key transactional and setup tables, including:

  • MSC_FILES: Stores output and log files generated by the plan.
  • MSC_PLAN_ORGANIZATIONS: Defines which organizations are part of the plan's scope.
  • MSC_SNAPSHOT_TASKS: Tracks the status of data collection (snapshot) processes for the plan.
  • MSC_SUP_DEM_ENTRIES: Stores the core planned supply and demand entries generated by the plan run.
Furthermore, it references MSC_ASSIGNMENT_SETS and HZ_PARTIES as foreign key parents. This network of relationships underscores the table's pivotal role in the planning data model.