Search Results inv_mgd_purge_cp




Overview
Explore in AI Chat

Overview

INV_MGD_PURGE_CP is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema. Its name follows the inventory management (INV) naming convention, indicating a purge utility associated with Oracle's Warehouse Management or Advanced Inventory module. The "_CP" suffix typically designates a concurrent program driver, and the presence of FND_REQUEST, FND_CONCURRENT_REQUESTS, and DBMS_LOCK dependencies confirms that this package is designed to submit and manage a concurrent purge request within the EBS concurrent manager infrastructure.

The business function of INV_MGD_PURGE_CP is to manage the purging of material-handling and inventory management data tables. Purge programs in this area remove obsolete or historical records generated by inventory transactions, material handling events, task flows, or warehouse workload data so that long-running operational tables do not accumulate stale rows indefinitely. As a controlled purge driver, the package validates the runtime environment, enforces single-instance locking, and dispatches the underlying purge worker through the concurrent manager rather than deleting data inline.

Key Procedures and Functions

The ETRM metadata documents a single public procedure:

  • PURGE — The entry point for the package. Based on the dependencies on FND_REQUEST and FND_CONCURRENT_REQUESTS, PURGE is responsible for validating that no conflicting purge run is in progress, submitting the purge concurrent request through FND_REQUEST.SUBMIT_REQUEST, and tracking the resulting request identifier. It uses DBMS_LOCK to acquire an exclusive lock, preventing concurrent purge executions that could corrupt transactional data or produce duplicate delete processing.

INV_MGD_PURGE_CP also carries a self-referential dependency, meaning the package invokes its own internal logic either recursively or as part of a two-phase submit-and-wait pattern. No source parameters are documented in the metadata; the exact argument list should be confirmed by inspecting the package header in the target environment.

Tables Accessed

The documented referenced objects include:

  • FND_CONCURRENT_REQUESTS — Queried to verify the status of previously submitted purge requests, ensuring a prior run has completed before a new submission is allowed, and to resolve request identifiers to their runtime phase.
  • DBMS_LOCK — The Oracle-supplied locking package, used to serialize purge execution and prevent parallel invocations from overlapping.
  • PLITBLM — A PL/SQL table utility package, generally used internally for array and index-by table handling within the purge logic.
  • FND_REQUEST, FND_MSG_PUB, FND_API, FND_PROFILE, HR_ORGANIZATION_UNITS, and INV_ORGHIERARCHY_PVT — Supporting dependencies used to submit the concurrent request, publish error messages, resolve profile options, and determine the organization hierarchy or operating unit scope for which the purge applies.

The metadata indicates this package is not referenced by any other database object, so it acts as a top-level entry point rather than a shared utility.

Usage Notes

INV_MGD_PURGE_CP is typically invoked from the EBS concurrent program framework, either through a registered concurrent program definition or from a form or custom code that calls the PURGE procedure directly. Because it delegates work through FND_REQUEST and DBMS_LOCK, it should not be called from interactive transaction flows where synchronous execution is expected. Administrators generally schedule it nightly or during maintenance windows, specifying the organization and date range to purge. Before running on production data, the purge scope should be validated, and DBAs should confirm that no dependent inventory or material-handling processes are active. The package is available in both 12.1.1 and 12.2.2, with the same APPS ownership and VALID status in each release.