Search Results purge_instance_plan_data

Overview

MSC_PURGE_LID is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Advanced Supply Chain Planning (ASCP) module. Its principal business function is the controlled removal of planning data associated with a specific planning instance, plan, or the Local Instance Data (LID) structures that ASCP uses to stage supply and demand information. The package header carries the RCS identifier MSCPPURS.pls 120.1 dated April 2007, indicating that it has been a stable component of the planning architecture across the 12.1.1 and 12.2.2 releases. The package exposes a set of purge procedures, each scoped to a different level of granularity, allowing planners and administrators to reclaim storage and eliminate obsolete planning artifacts without disrupting active plans.

Key Procedures and Functions

• PURGE_LID_TABLES — The primary entry point for purging local instance data tables. It accepts an instance identifier, a complete-refresh indicator, a date, and separate supply and demand flags that control which classes of data are removed.
• PURGE_ODS_TABLES_DEL — Deletes Operational Data Store records tied to the supplied instance identifier, cleaning the staging layer that feeds planning collections.
• PURGE_INSTANCE_DATA — Added specifically to support the purge_instance_data flow. It receives a PL/SQL collection of instance identifiers (typed as a table of NUMBER) and purges data for the entire list in a single invocation.
• PURGE_PLAN_DATA — Analogous to the instance-level procedure but operates on a collection of plan identifiers rather than instances.
• PURGE_INSTANCE_PLAN_DATA — A combined-scope procedure that removes data for a single instance and single plan pairing, providing the most targeted purge granularity.
• PURGE_LOCALID_TABLE — Maintains the local identifier structures, including MSC_ITEM_ID_LID, by removing obsolete identifier rows.
• PURGE_ODS_DATA — Removes ODS planning data, complementing the ODS table deletion logic used elsewhere in the package.
• PURGE_ODS_LEG_DATA — Cleans the legacy ODS data segments retained for backward compatibility.
• PURGE_INST_ENTITY_ODS_DATA — Removes ODS data scoped to specific instance entities, allowing partial cleanup of entity-level staging records.

Tables Accessed

The package reads and writes the core ASCP staging tables. MSC_APPS_INSTANCES defines the planning instances whose data is being purged, while MSC_LOCAL_ID_DEMAND and MSC_LOCAL_ID_SUPPLY hold the local identifier supply and demand records targeted by the LID purge procedures. Detailed planning content resides in MSC_DEMANDS, MSC_DESIGNATORS, MSC_ITEM_ID_LID, MSC_JOB_OPERATIONS, MSC_JOB_OPERATION_NETWORKS, MSC_JOB_OP_RESOURCES, MSC_JOB_REQUIREMENT_OPS, and MSC_RESOURCE_REQUIREMENTS, all of which are cleaned during instance or plan purge operations. Supporting metadata is drawn from FND_APPLICATION, FND_LOOKUP_VALUES, FND_ORACLE_USERID, and FND_PRODUCT_INSTALLATIONS, which supply application identifiers, lookup meanings, schema credentials, and installation status used to qualify and validate purge targets.

Usage Notes

MSC_PURGE_LID is not typically called directly by end users. It is invoked by ASCP concurrent programs and administrative utilities related to instance and plan maintenance, and it may be wrapped by custom purge scripts in environments with high planning data volumes. The procedure constants define internal state values (empty, pulling, ready, collecting, purging, pre-processing) and status codes (success, error) that callers may inspect through the ERRBUF and RETCODE OUT parameters. The package is referenced by zero other packages, confirming that it functions as a leaf-level utility rather than a shared library. Because purge operations are destructive, invocations should be scheduled during maintenance windows and preceded by standard ASCP planning-data backups in both 12.1.1 and 12.2.2 environments.