Search Results launch_purge

Overview

APPS.MSC_CL_PURGE_STAGING is a PL/SQL package belonging to the MSC (Advanced Supply Chain Planning) schema family within Oracle E-Business Suite. Its business function is to manage the lifecycle of data held in the staging tables used by the MSC planning collections and planning engine interface. Staging tables temporarily hold collected source data — such as items, bills of material, routings, sourcing rules, and on-hand balances — while they await validation, preprocessing, and propagation into the planning data model. The package provides the mechanism by which that transient data is removed once it is no longer required, freeing the associated storage and resetting the staging area for the next collection cycle.

The package is organised around a set of named constants that define process flags (new, in-process, error, propagation, valid), staging table status values (empty, pulling, ready, collecting, purging, pre-processing), return codes (success, warning, error), and instance type classifications (discrete, process, other, mixed, exchange). These constants confirm that the purge logic is tightly integrated with the MSC instance state machine and is intended to run only against instances in an eligible status. The header identifies the file as MSCCLPSS.pls, a 2008-era release consistent with both 12.1.1 and 12.2.2.

Key Procedures and Functions

Five procedures are documented in the packaged specification:

• LAUNCH_PURGE — The primary entry point. It accepts standard concurrent program OUT parameters plus an instance identifier and an optional flag controlling whether rejected records are deleted, and orchestrates the overall purge request for the specified planning instance.
• PURGE_STAGING_TABLES_TRNC — Performs the truncate-based purge path for a given instance, removing staging content by truncation rather than row-level deletion.
• PURGE_STAGING_TABLES_DEL — Performs the delete-based purge path for a given instance, retaining the table structure and removing rows selectively.
• PURGE_STAGING_TABLES_SUB — The internal sub-routine that carries out the detailed purge work. It accepts an instance identifier and a blind-purge flag defaulting to SYS_NO. The blind-purge option allows the caller to bypass the normal eligibility checks when a forced cleanup is required.
• TRUNCATE_STAGING_TABLES — A standalone utility that truncates staging tables globally, exposing the standard concurrent program OUT parameters.

Tables Accessed

The documented tables referenced through APPS synonyms are:

• MSC_APPS_INSTANCES — The master record of planning instances. It is read to obtain instance type and staging status, and updated to reflect the purging and empty states.
• MSC_ST_SR_ASSIGNMENTS — Staging table for sourcing rule assignments, one of the collection entities subject to purge.
• FND_LOOKUP_VALUES — Used for reference lookups, typically to resolve purge-related settings and confirm enabled values.
• DUAL — Used for single-row expressions and status checks within the PL/SQL logic.

Usage Notes

The package is normally invoked from the Advanced Supply Chain Planning collection and purge concurrent programs rather than directly by end users. The LAUNCH_PURGE procedure is designed to match the standard concurrent program signature (ERRBUF, RETCODE), allowing it to be registered as a concurrent executable. The TRUNCATE_STAGING_TABLES procedure follows the same pattern for administrative full purges. Because the package is referenced by two other MSC packages, it also functions as a callable utility within the planning engine's internal flow, particularly when an instance transitions out of the collecting or collecting-complete status. Custom code should invoke LAUNCH_PURGE rather than the lower-level sub-routines, so that instance status validation and purge flag handling remain consistent, and should avoid the blind-purge option except during controlled recovery of a stuck instance.