Search Results sync_cloned_src_pub_data

Overview

APPS.CZ_PB_SYNC is a public PL/SQL package belonging to the Oracle E-Business Suite product family associated with the "CZ" schema prefix, historically linked to Oracle's product configuration and publication infrastructure (commonly seen in legacy configurator and Bill of Materials-adjacent components). Its AUTHID CURRENT_USER declaration means that the package executes with the privileges of the calling session rather than the definer's, which is significant in the APPS environment where synonym resolution and grants govern access to underlying objects.

The package's overriding purpose is to synchronize cloned public data between source and target instances. In multi-instance EBS topologies — particularly those used for cloning production into test or staging environments — public configuration data such as model publications, UI definitions, and publication usage records must be re-pointed or refreshed so that the cloned instance reflects consistent, instance-aware metadata. CZ_PB_SYNC encapsulates this reconciliation logic, providing both programmatic entry points and concurrent-manager wrappers that expose the same logic to the standard concurrent program framework.

The header comment indicates a ship date of 2002-12-18, placing this package historically in the 11i lineage and carried forward into 12.1.1 and 12.2.2. The 12.2.2 ETRM metadata classifies the package as API classification OTHER, meaning Oracle does not document it as a supported public API; it is effectively an internal utility.

Key Procedures and Functions

The package exposes four documented procedures, declared within a package specification that also defines a ref_cursor type.

• SYNC_CLONED_TGT_PUB_DATA — Synchronizes cloned public data on the target instance, accepting a target instance identifier and returning a run ID and status through OUT NOCOPY parameters. This is the core programmatic routine for target-side reconciliation.
• SYNC_CLONED_SRC_PUB_DATA — Performs the corresponding synchronization on the source instance, taking a decommission flag and returning run ID and status. The decommission flag allows the caller to signal whether a source deployment is being retired, which affects data handling.
• SYNC_CLONED_TGT_PUB_DATA_CP — Concurrent-program wrapper for the target synchronization. It follows the standard EBS concurrent manager signature, exposing Errbuf and Retcode parameters alongside the target instance argument, allowing invocation from the Concurrent Programs form.
• SYNC_CLONED_SRC_PUB_DATA_CP — Concurrent-program wrapper for the source synchronization, similarly exposing Errbuf and Retcode plus the decommission flag parameter.

The pairing of each business procedure with a _CP variant is the conventional Oracle pattern for exposing package logic to the concurrent manager while retaining a callable API surface.

Tables Accessed

The package references its data through APPS synonyms. The most relevant tables are:

• CZ_MODEL_PUBLICATIONS and CZ_MODEL_PUBLICATIONS_S — the base and shadow/publication tables central to the synchronization, holding published model metadata that must be reconciled across instances.
• CZ_PUBLICATION_USAGES — tracks where and how publications are consumed, information needed to correctly re-point usage after cloning.
• CZ_PB_CLIENT_APPS and CZ_PB_MODEL_EXPORTS — client application registrations and model export records within the publication infrastructure.
• CZ_UI_DEFS, CZ_UI_TEMPLATES, CZ_PB_LANGUAGES — UI definition and template data, plus language metadata, which travel with publication synchronization.
• CZ_DEVL_PROJECTS, CZ_ITEM_MASTERS, CZ_SERVERS — supporting master and server configuration data used to resolve instance context.
• V$DATABASE and V$INSTANCE — dynamic performance views used to determine the current database and instance identity, essential for deciding source-versus-target behavior.
• DUAL and PLITBLM — the standard single-row pseudo-table and the PL/SQL integer index-by table used for internal processing.

Usage Notes

CZ_PB_SYNC is normally invoked through the Oracle Concurrent Manager rather than directly from forms. The _CP procedures are registered as concurrent programs, enabling administrators to submit the target or source synchronization from the standard Submit Requests interface. In custom code, the underlying business procedures can be called directly, but callers must supply the target instance identifier or decommission flag and handle the OUT NOCOPY run ID and status parameters.

Because the package is classified as OTHER and is not a supported public API, integrators should treat it as internal and not build permanent dependencies on it. It is most useful during cloning and publication-refresh activities in multi-instance EBS deployments, where it ensures that public model and UI data remain coherent between source and target environments. The ETRM metadata records no packages referencing CZ_PB_SYNC, confirming it sits at the top of its dependency chain as an invoked utility rather than a shared library.