Search Results triggers_enabled




Overview
Explore in AI Chat

Overview

APPS.CZ_MANAGER is a utility PL/SQL package within the Oracle E-Business Suite configuration management subsystem. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the calling schema rather than the definer, which is a deliberate design choice for a maintenance and data-integrity utility that must operate against the objects visible to the invoking session. Its header revision (czmangrs.pls 115.9, dated 2002) indicates the package is longstanding, stable, and has been carried forward largely unchanged into Oracle EBS 12.1.1 and 12.2.2. The package’s purpose is administrative: it supports assessment of data consistency, controlled enablement and disabling of database triggers and constraints during bulk operations, resequencing of underlying database sequences, clearing of transient setup state, and purging of obsolete configuration data. The presence of the PURGE_CP procedure accounts for user searches on the term “purge_cp,” since this routine is the concurrent-program-facing entry point for the purge operation.

Key Procedures and Functions

  • ASSESS_DATA — Performs an assessment pass over the package’s managed data, evaluating consistency of configuration records and reporting on conditions that require administrative attention before corrective or purge actions are taken.
  • TRIGGERS_ENABLED — Accepts a switch value to enable or disable the database triggers associated with the managed tables, allowing bulk maintenance activity to proceed without trigger-side effects.
  • CONSTRAINTS_ENABLED — Accepts a switch value to enable or disable the integrity constraints that guard the managed tables, complementing the trigger control above so that large data operations are not blocked or slowed by per-row validation.
  • REDO_SEQUENCES — Accepts a redo-start flag and an optional increment, used to resequence or realign the database sequences associated with configuration data so that generated identifiers remain consistent after cleanup or migration activity.
  • RESET_CLEAR — Resets transient or temporary setup/processing flags, returning the subsystem to a clean, cleared state following an interrupted or partially completed maintenance cycle.
  • PURGE — The core purge routine, removing obsolete configuration records and their dependent rows according to the package’s own purge logic.
  • PURGE_CP — The concurrent-program wrapper around the purge operation. It exposes the standard EBS concurrent-program interface, returning an error buffer and return code so that a concurrent program can report completion status to the concurrent manager.

Tables Accessed

The ETRM metadata records no explicit table references for CZ_MANAGER through APPS synonyms, and the package is not referenced by any other package (0 dependents). The tables manipulated are therefore those owned by or synonymous with the configuration management (CZ_) schema family. Functionally, the procedures operate on configuration/feature setup tables, their child or dependent relation tables (for the purge and reset routines), and the database sequence objects realigned by REDO_SEQUENCES. The absence of documented synonym references reflects gaps in the extracted metadata rather than an absence of data access; the actual table list is resolved at runtime against the CZ_ schema objects owned by APPS.

Usage Notes

CZ_MANAGER is not a business transaction API and is not exposed to end-user forms. It is an administrative utility invoked in three principal ways. First, PURGE_CP is registered as a concurrent program and submitted from the EBS Standard Concurrent Programs (or a custom request group) by administrators performing scheduled or on-demand purge of obsolete configuration data; its Errbuf/Retcode signature is the standard concurrent-program contract. Second, the enable/disable and resequencing procedures are typically called from controlled scripts or ad hoc SQL*Plus sessions during data migration, cloning, or patching windows, where disabling triggers and constraints temporarily improves throughput and resequencing restores identifier integrity afterward. Third, custom extensions may call ASSESS_DATA and RESET_CLEAR to validate state and clean up after bulk loads. Because the package is declared AUTHID CURRENT_USER and has no documented dependent packages, administrators should invoke it from the APPS schema or from a session with equivalent privileges, and should treat purge and constraint/trigger operations as maintenance-window activities requiring a current backup.