Search Results purge_to_date_cp

Overview

APP.CZ_IMP_MGR is a database package in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that supports the maintenance, housekeeping, and lifecycle management of data associated with the Configuration Management (CZ) import process. The package is classified under the ETRM API classification "OTHER," indicating it is a utility or administrative package rather than an interface or public API intended for external consumption. Its primary purpose is to purge obsolete or stale import and transfer data, thereby preventing the growth of transactional and staging tables within the CZ schema.

The header comment, "$Header: czimngrs.pls 120.0 2005/05/25 07:14:08 appldev noship $", indicates the package has been part of the EBS codebase since at least 2005. The "noship" designation reflects that it is a server-side package rather than a client-shipped artifact. A package-level constant, BATCH_SIZE, is defined as 10000, which governs the volume of rows processed per batch during purge operations. Two constants, G_CONCURRENT_SUCCESS and G_CONCURRENT_ERROR, mirror the standard concurrent program return codes (0 and 2 respectively), confirming the package is designed to be invoked as or by concurrent programs.

Key Procedures and Functions

The package exposes three documented procedures, all of which follow the standard concurrent program parameter convention of an error buffer (errbuf) and a return code (retcode):

• PURGE_CP — The base purge procedure. It performs a purge operation without an explicit date or run identifier filter, serving as the general-purpose entry point for cleaning import data.
• PURGE_TO_DATE_CP — The procedure located by the search term "purge_to_date_cp." It accepts an additional numeric parameter, p_days, which allows the caller to specify a retention window. The procedure purges records older than the specified number of days, enabling administrators to retain recent data while removing historical data.
• PURGE_TO_RUNID_CP — Purges data associated with a specific transfer run. It accepts an additional numeric parameter, p_run_id, which identifies the run whose data should be removed. This is useful for targeted cleanup of a single failed or obsolete import run.

Tables Accessed

The package references several tables and utilities through APPS synonyms:

• CZ_XFR_RUN_INFOS — Stores metadata about transfer or import runs. The purge procedures use this table to identify which records are eligible for removal, particularly in PURGE_TO_RUNID_CP and PURGE_TO_DATE_CP.
• CZ_DB_SETTINGS — Holds configuration settings for the Configuration Management schema. It is likely consulted to determine defaults such as retention periods or batch sizes used during purge processing.
• DBA_TABLES — Queried to validate the existence of tables prior to purging, supporting dynamic or defensive SQL within the package.
• DBMS_APPLICATION_INFO — Used to set module and action information for session monitoring, a common practice in concurrent programs to track progress.
• DUAL — Standard Oracle single-row pseudo-table used for scalar evaluations or control logic.
• PLITBLM — An internal Oracle table type used in PL/SQL for handling collections of rowids or similar identifiers, typically employed to batch delete operations.

Usage Notes

CZ_IMP_MGR is designed to be invoked from concurrent programs in Oracle EBS. The errbuf and retcode parameters conform to the standard concurrent program signature, and the presence of G_CONCURRENT_SUCCESS and G_CONCURRENT_ERROR constants confirms this design intent. Administrators typically schedule these purge procedures as periodic concurrent requests to manage the size of the CZ transfer and import tables. PURGE_TO_DATE_CP is invoked when a retention-based policy is applied (for example, purging records older than 30 days), while PURGE_TO_RUNID_CP is invoked for targeted cleanup of a specific run. The package is not referenced by any other packages according to the ETRM metadata, indicating it is a standalone administrative utility and not part of an application programming interface chain. Direct invocation from custom PL/SQL is possible but subject to the same standard parameter signature and should be performed with caution given the destructive nature of purge operations.