Search Results cz_pub_mgr




Overview
Explore in AI Chat

Overview

APPS.CZ_PUB_MGR is a VALID PL/SQL package body in the Oracle E-Business Suite APPS schema that supports the Oracle Configurator and Configure-to-Order publication infrastructure. It provides the shared manager-level runtime services used when publishing and maintaining model publication data sets — the configuration models, reference explanations, client application definitions, language rows, and publication usages that together define what a released Configurator model exposes to downstream order capture and manufacturing flows. The package is classified under the ETRM as OTHER rather than as a public Oracle API, which indicates it is an internal implementation package rather than a supported integration surface. It is not referenced by any database object, although it is referenced by one other package, confirming its role as a leaf-level utility layer invoked by higher-level publication drivers. In EBS 12.1.1 and 12.2.2 the package body is compiled against the APPS edition and remains VALID, so its logic is available to any caller that has EXECUTE privileges on the package.

Key Procedures and Functions

The documented interface contains eight procedures and functions, each concerned with preparing and restoring the environment during a publication or purge operation.

  • ASSESS_DATA — Evaluates the state of publication-related data, providing the caller with a determination of whether the target model or publication set is safe to process.
  • TRIGGERS_ENABLED — Reports whether database triggers are currently enabled, allowing the publication logic to account for or temporarily disable trigger behavior during bulk operations.
  • CONSTRAINTS_ENABLED — Reports whether referential constraints are enabled, supporting the same bulk-load and data-maintenance decision points as TRIGGERS_ENABLED.
  • REDO_SEQUENCES — Re-establishes or resynchronizes sequence values after publication activity, ensuring generated identifiers remain consistent with the reloaded data set.
  • PURGE — Removes obsolete publication and staging rows, reclaiming space for superseded model publications and their dependent records.
  • MODIFIED — Determines whether a publication entity has changed since a prior checkpoint, used to avoid redundant republishing.
  • RESET_CLEAR — Restores flags, status columns, or control attributes to their initial state so that a subsequent publication run starts from a clean baseline.
  • REDO_STATISTICS — Refreshes or re-collects optimizer statistics for the affected tables following large data changes introduced by publication or purge.

No parameter signatures are documented in the ETRM metadata, so callers should reference the package specification source in the APPS schema for exact argument lists and return types.

Tables Accessed

The package reads and writes through APPS synonyms for the following documented tables: CZ_DB_LOGS, CZ_DEVL_PROJECTS, CZ_MODEL_PUBLICATIONS, CZ_MODEL_REF_EXPLS, CZ_PB_CLIENT_APPS, CZ_PB_LANGUAGES, CZ_PB_MODEL_EXPORTS, CZ_PUBLICATION_USAGES, CZ_RP_ENTRIES, and PLITBLM. CZ_MODEL_PUBLICATIONS and CZ_PB_MODEL_EXPORTS hold the publication records and export payloads that the purge and modified checks operate against. CZ_MODEL_REF_EXPLS and CZ_RP_ENTRIES store reference explanations and runtime parameter entries consumed by the assessment logic. CZ_DEVL_PROJECTS identifies the development project ownership of a model. CZ_PB_CLIENT_APPS and CZ_PB_LANGUAGES define the client application and language dimensions applied during publication. CZ_PUBLICATION_USAGES records where a publication is consumed. CZ_DB_LOGS provides the logging destination, while PLITBLM is the standard Oracle PL/SQL table type used for in-memory collections. Additional internal dependencies include CZ_BASE_MGR, CZ_UTILS, and STANDARD.

Usage Notes

CZ_PUB_MGR is not intended for direct customer invocation. It is typically called by the Configurator publication and purge concurrent programs, by the model publication form flows, and by the single other package that references it, which orchestrates the publication lifecycle. Because the utilities toggle trigger and constraint awareness, reset control flags, redo sequences and statistics, and purge staging rows, they are best invoked in the controlled, single-threaded context of a scheduled publication job rather than from ad hoc SQL. Custom code should not call these procedures without first confirming that no concurrent publication is active for the same model set. On EBS 12.2.2, ensure the package body is recompiled after any online patching cycle that touches the CZ schema so that the APPS edition references remain valid.