Search Results cz_imp

Overview

APPS.CZ_IMP_MGR is a maintenance and housekeeping package body that belongs to the Oracle E-Business Suite Configuration Management (CZ) schema, the component responsible for product configuration, bills of material import, and related transfer utilities. In Oracle EBS 12.1.1 and 12.2.2, the CZ schema hosts a family of tables prefixed CZ_IMP% that are used as staging and intermediate structures during configuration import and transfer processing. These tables accumulate run-level data that is not intended to be retained indefinitely.

CZ_IMP_MGR provides the administrative routines that remove obsolete import data, either by deleting rows associated with specific run identifiers or by truncating the full set of CZ_IMP% staging tables. Its header comment ($Header: czimngrb.pls 120.0) indicates the package body has been stable since 2005 and is marked noship, confirming that it is an internal, non-shipped utility invoked by Oracle's own maintenance logic rather than by end users. The API classification in the ETRM repository is OTHER, reflecting that it is a supporting cleanup package rather than a public business API.

Key Procedures and Functions

The documented public entry points in ETRM 12.2.2 are three cleanup procedures:

• PURGE_CP — The principal purge routine, typically exposed as a concurrent program (the _CP suffix denotes a concurrent-program wrapper). It removes accumulated import/staging data from the CZ import tables.
• PURGE_TO_DATE_CP — A date-bounded variant of the purge concurrent program. It restricts deletion to import records older than a supplied cutoff date, allowing administrators to retain recent activity while clearing historical rows.
• PURGE_TO_RUNID_CP — A run-bounded variant that purges data for a specific run identifier or range of run identifiers, so individual failed or superseded runs can be eliminated without affecting other imports.

Internally the body also defines two PL/SQL collection types (tRunId, tName) and helper logic that dynamically discovers every table owned by CZ whose name matches CZ_IMP%, then issues dynamic DELETE or TRUNCATE statements against them. Deletions are committed in batches governed by the BATCHSIZE setting, limiting undo growth and reducing the risk of long-running transactions on large staging tables.

Tables Accessed

The package reads and writes the following documented objects, generally through APPS synonyms:

• CZ_DB_SETTINGS — Read to retrieve the BATCHSIZE value that controls commit frequency during purging.
• CZ_XFR_RUN_INFOS — Deleted to remove run header/definition information associated with purged runs.
• CZ_XFR_RUN_RESULTS — Deleted to remove the per-run result records produced by transfer processing.
• DBA_TABLES — Queried to enumerate all CZ_IMP% tables owned by the CZ schema, which drives the dynamic SQL loop.
• DBMS_APPLICATION_INFO — Used to set the module name (for example CZIMPORT) so purge activity is traceable in database session monitoring.
• DUAL and PLITBLM — Referenced indirectly during package execution and bulk collection handling.

Usage Notes

CZ_IMP_MGR is not a business API and is not referenced by any other package in the ETRM repository (referenced by 0 packages). It is invoked either directly from Oracle's internal CZ migration routines or, more commonly, from concurrent programs registered against the PURGE_*_CP entry points. Administrators run these concurrent programs when CZ import staging tables grow unacceptably large or when a specific transfer run must be removed after failure. Because the purge logic uses TRUNCATE and unrestricted DELETE against staging tables, it should be scheduled only during periods when no CZ import or configuration transfer is active; the run-scoped variant is safer for targeted cleanup. The DBMS_APPLICATION_INFO.SET_MODULE call makes purge sessions identifiable in V$SESSION, aiding diagnosis of long-running cleanup jobs in high-volume environments.