Search Results analyze_plan

Overview

The APPS.MSC_MANAGE_PLAN_PARTITIONS package is a core infrastructure component of Oracle Advanced Supply Chain Planning (ASCP), delivered within the MSC (Manufacturing and Supply Chain) application module. Its principal business function is the automated administration of database partitioning for planning data. Because ASCP plans can generate very large volumes of transient supply/demand data, the underlying tables are physically partitioned, and each plan or planning instance is bound to a specific partition. This package manages the lifecycle of those partitions—identifying free partitions, allocating them to plans or instances, creating new partitions through dynamic DDL when none are available, and reclaiming (purging or dropping) partitions no longer in use.

In EBS 12.1.1 and 12.2.2 the package is frequently identified by consultants troubleshooting "partition manager" behaviour, since it is the mechanism that silently performs DDL against partitioned tables during plan creation and deletion. It encapsulates all of the low-level partition bookkeeping so that the Planner UI and concurrent programs do not need to issue DDL directly.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions:

• GET_PLAN – A function invoked from the Create Plan UI. It determines whether a free partition exists in MSC_PLAN_PARTITIONS; if so it returns the associated plan_id, otherwise it creates a new partition via DDL and records it. Returns FND_API status codes (SUCCESS, ERROR, UNEXP_ERROR).
• GET_INSTANCE – A function returning a free instance identifier for allocation.
• GET_PARTITION_NAME – A procedure returning the partition name that stores a given plan or instance for an input table, using a flag to distinguish plan partitions from instance partitions.
• CREATE_INST_PARTITION – Creates a partition to hold instance-level planning data.
• PURGE_PARTITION – Removes data from and/or releases a partition back to the free pool.
• CREATE_FORCE_PARTITION and DROP_FORCE_PARTITION – Create or drop partitions irrespective of normal free-pool logic, typically for administrative or recovery operations.
• CREATE_EXIST_PLAN_PARTITIONS and DROP_EXIST_PLAN_PARTITIONS – Bulk create or drop the partitions belonging to existing plans.
• CREATE_EXIST_INST_PARTITIONS – Bulk creation of partitions for existing instances.
• GET_PARTITION_NUMBER – Returns the numeric partition identifier.
• ANALYZE_PLAN – Initiates statistics gathering on a plan's partition for optimizer performance.
• CREATE_PARTITIONS – General partition creation routine used across the package.

Tables Accessed

The package operates against the following documented tables (referenced via APPS synonyms):

• MSC_PLAN_PARTITIONS – The central registry of plan-to-partition assignments and usage flags.
• MSC_INST_PARTITIONS – Registry of instance-to-partition assignments.
• MSC_PLANS and MSC_PLANS_S – Plan definitions and their MLS/translation shadow, used to validate plan references.
• MSC_APPS_INSTANCES and MSC_APPS_INSTANCES_S – Planning instance definitions.
• AD_DDL – The AD utility used to execute the dynamic DDL statements that physically create or drop partitions.
• DBA_TABLES and DUAL – Metadata queries and constant returns.
• FND_ORACLE_USERID and FND_PRODUCT_INSTALLATIONS – Application schema and installation context.

Usage Notes

This package is not an end-user API. It is invoked internally by the Create Plan and planning instance forms of ASCP, by concurrent programs that build or purge plans, and by administrative scripts that pre-create or drop partitions. Because it performs DDL, it must run with sufficient privileges (typically as APPS) and its execution is generally not transactional. Custom code should call it only with care, since an incorrect invocation can leave orphaned partitions or consume free partition slots. The five dependent packages that reference it are typically other MSC planning utilities. When diagnosing partition errors, DBAs commonly trace calls into MSC_MANAGE_PLAN_PARTITIONS to determine whether the free partition pool is exhausted or a DDL statement failed.