Search Results cz_model_publications_s




Overview
Explore in AI Chat

Overview

The APPS.CZ_PB_SYNC package body is a synchronization utility within the Oracle E-Business Suite product publication infrastructure, sometimes referred to internally as "PB" (publication/build) tooling. Its principal business function is to reconcile publication-related data between a source environment and a cloned target environment after a database clone operation. Because Oracle EBS clones reproduce the source database wholesale, environment-specific publication metadata — server registrations, model publication records, language definitions, client application registrations, and export artifacts — must be re-pointed or regenerated so that the target instance reflects its own identity (host name, instance name, database name) rather than that of the source system.

The package draws on environment context supplied by the V$DATABASE, V$INSTANCE, and V$SESSION dynamic performance views, which allow it to detect the current database/instance identity at runtime and distinguish source-side work from target-side work. It is declared VALID in the APPS schema and carries no dependent database objects, indicating it is a terminal utility package invoked directly rather than called from other PL/SQL units.

Key Procedures and Functions

Four documented procedures comprise the package's public interface. They are organized in two logical pairs:

  • SYNC_CLONED_TGT_PUB_DATA — Performs the target-side synchronization of publication data after a clone, aligning publication records in the cloned environment with the target instance's own server and instance identity.
  • SYNC_CLONED_TGT_PUB_DATA_CP — A concurrent-program wrapper variant of the same target-side synchronization logic, exposing the routine for scheduled or user-initiated execution through the concurrent manager.
  • SYNC_CLONED_SRC_PUB_DATA — Handles the source-side counterpart work, capturing or preparing publication data from the originating environment so the target can be correctly reconciled.
  • SYNC_CLONED_SRC_PUB_DATA_CP — The concurrent-program entry point corresponding to the source-side synchronization procedure.

The "_CP" suffix convention follows Oracle EBS standards, where a procedure is specifically designed to be run as a concurrent request. No published parameter lists are available in the metadata; invocation is therefore typically driven by the concurrent program definition rather than by direct API calls.

Tables Accessed

The package reads and writes across the CZ publication and configuration tables, accessed through APPS synonyms. CZ_MODEL_PUBLICATIONS and its _S (sequence/translation) shadow table hold the published model definitions that must survive a clone intact and correctly re-pointed. CZ_PB_MODEL_EXPORTS and CZ_PB_CLIENT_APPS track export artifacts and registered client applications tied to each publication. CZ_PB_LANGUAGES provides language configuration, while CZ_UI_DEFS and CZ_UI_TEMPLATES supply user interface definition and template metadata associated with published models. CZ_PUBLICATION_USAGES records where publications are consumed. CZ_SERVERS, CZ_DEVL_PROJECTS, CZ_ITEM_MASTERS, and MTL_SYSTEM_ITEMS_VL supply server registration, development project, and item master context. DUAL and PLITBLM support housekeeping and bulk processing operations, and the V$ views provide the runtime identity check that drives clone detection.

Usage Notes

CZ_PB_SYNC is invoked in the post-clone phase of an EBS environment refresh, after the standard adclone/AutoConfig steps have completed, to repair publication metadata that remains bound to the source system. The presence of the "_CP" procedures confirms that the supported mechanism is a concurrent program submitted from the target instance; direct calls from forms are not part of the documented interface. Since the package references only APPS synonyms and no other database object depends on it, it can be re-run safely as part of an idempotent clone remediation checklist. Administrators should verify V$INSTANCE and V$DATABASE report the target identity before submission, as this is the condition the synchronization logic relies upon to distinguish source from target records.