Search Results msc_plans




The MSC_PLANS table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for storing master production and distribution planning data within the Advanced Supply Chain Planning (ASCP) module. This table serves as the foundation for planning engine operations, capturing metadata, execution parameters, and output results for supply chain optimization. Below is a detailed technical summary of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Context

The MSC_PLANS table acts as the central repository for all planning definitions and executions in ASCP. It stores high-level plan attributes, including plan names, descriptions, ownership, and statuses. Each record represents a unique planning scenario, enabling organizations to model different supply chain strategies (e.g., constrained vs. unconstrained plans, multi-organization plans). The table is tightly integrated with Oracle's planning engine, feeding data to downstream processes like MRP, DRP, and global order promising.

Key Columns and Data Structure

  • PLAN_ID: Primary key, uniquely identifying each plan.
  • PLAN_NAME: User-defined name for the plan (e.g., "Global_Constrained_Plan_Q4").
  • ORGANIZATION_ID: References HR_ORGANIZATION_UNITS to associate plans with specific inventory organizations.
  • PLAN_TYPE: Numeric flag indicating plan methodology (1=ASCP, 2=DRP, 3=MPS).
  • STATUS: Execution state (e.g., 1=Not Started, 2=In Progress, 3=Complete).
  • LAST_UPDATE_DATE: Timestamp for SCD2 tracking, critical for audit trails.
  • CUTOFF_DATE: Horizon limit for plan calculations.
  • COMPILE_DESIGNATOR: Links to BOM and routing versions via BOM_COMPONENTS.
  • SR_INSTANCE_ID: References concurrent request IDs in FND_CONCURRENT_REQUESTS.

Integration with Other Modules

The table has foreign key relationships with:
  • MSC_PLAN_ORGANIZATIONS: Defines scope of organizations included in each plan.
  • MSC_PLAN_BUCKETS: Stores time-phased planning buckets.
  • MSC_SUPPLIES and MSC_DEMANDS: Contain plan output details.
It also interfaces with Inventory (MTL_SYSTEM_ITEMS), Order Management (OE_ORDER_HEADERS), and Manufacturing (BOM_BILL_OF_MATERIALS) via shared keys.

Technical Considerations

  • Indexing: Heavily indexed on PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID for join performance.
  • Partitioning: In EBS 12.2.2, supports range partitioning by LAST_UPDATE_DATE for large implementations.
  • API Interactions: Primarily accessed via MSC_APIs (e.g., MSC_PLAN_PUB) rather than direct DML.
  • Performance Impact: Table growth requires monitoring; Oracle recommends purging obsolete plans via MSC_PLAN_PURGE package.

Version-Specific Enhancements

In EBS 12.2.2, notable additions include:
  • Extended Unicode support for PLAN_DESCRIPTION.
  • New CLOUD_SYNC_FLAG column for hybrid cloud integrations.
  • Enhanced constraints to enforce referential integrity with FND_USER for CREATED_BY fields.

Business Process Implications

The table enables:
  • Multi-scenario analysis through parallel plan versions.
  • Audit trails for regulatory compliance (SOX, GxP).
  • Integration with Oracle Demantra for demand-driven planning.
In summary, MSC_PLANS is the architectural cornerstone of Oracle ASCP, providing the metadata framework that drives supply chain optimization. Its design reflects Oracle's hierarchical data model, balancing flexibility with referential integrity to support complex, multi-enterprise planning scenarios.