Search Results cz_config_api_pvt




Overview
Explore in AI Chat

Overview

APPS.CZ_CONFIG_API_PVT is a private PL/SQL package in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 application schema. The "CZ" prefix identifies the package as part of the Oracle Configurator (also marketed historically as Oracle Configurator Developer and the Configurator runtime), a component of the Oracle Advanced Product Catalog / Configurator suite used to model configurable products. The "_PVT" suffix denotes that the package is a private implementation unit: it is not intended to be called directly by customer code, forms, or concurrent programs. Instead, it functions as the internal engine behind the public API CZ_CONFIG_API_PUB, which surfaces the supported configuration-copying and verification operations.

The package's core business purpose is the automated and manual duplication and validation of Configurator model definitions. When a configurable item is copied between models, organizations, or environments, the underlying configuration headers, attributes, inputs, items, and messages must be replicated while preserving referential integrity. CZ_CONFIG_API_PVT orchestrates that replication and performs consistency checks against the destination structures. Because it is classified as a private (PVT) API, all documented entry points are wrapped by the public package and are subject to change between releases without notice.

Key Procedures and Functions

The ETRM metadata documents three procedures or functions, each reflecting a distinct facet of the copy/verify workflow:

  • COPY_CONFIGURATION — Drives the replication of a complete configuration definition from a source to a target. This is the manual/interactive variant, invoked when the caller supplies the configuration context explicitly through the public wrapper.
  • COPY_CONFIGURATION_AUTO — Performs the same replication logic but in an automated mode, intended for programmatic or batch-style invocation where configuration identifiers are resolved automatically rather than passed interactively by a user.
  • VERIFY_CONFIGURATION — Validates a configuration against the supporting table structures, confirming that headers, items, attributes, inputs, and messages are internally consistent and complete. It is typically called after a copy operation to guarantee that the newly created configuration is structurally sound.

No parameter lists are reproduced here, as the documented metadata does not define them; the procedures are described strictly by intent derived from their names and dependencies.

Tables Accessed

The package reads and writes an extensive set of Configurator and supporting tables, referenced through APPS synonyms. The core Configurator entities include CZ_CONFIG_HDRS and its sequence-backed CZ_CONFIG_HDRS_S, CZ_CONFIG_ITEMS and CZ_CONFIG_ITEMS_S, CZ_CONFIG_ATTRIBUTES, CZ_CONFIG_EXT_ATTRIBUTES, CZ_CONFIG_INPUTS, and CZ_CONFIG_MESSAGES with CZ_CONFIG_MESSAGES_S. Together these hold the configuration's header, its constituent items, attribute definitions, external attribute bindings, user inputs, and validation messages. CZ_DB_SETTINGS supplies database-level configuration switches that influence how the copy behaves. ALL_TAB_COLUMNS is queried for metadata introspection, DUAL for singleton expression evaluation, and PLITBLM (the PL/SQL integer table) as an in-memory collection for bulk processing. The sequence tables confirm that the package allocates new primary keys during copy operations.

Usage Notes

CZ_CONFIG_API_PVT should never be invoked directly. Its supported access path is through APPS.CZ_CONFIG_API_PUB, which is the documented public interface. Indirectly, it is referenced by CZ_NETWORK_API_PUB, indicating that network configuration operations trigger the copy and verify logic internally. Typical invocation scenarios include Configurator Developer copy commands, concurrent programs that clone configurations between environments, and upgrade or cloning routines that need to re-establish configuration integrity. Because the package body is not a public contract, customizations must target CZ_CONFIG_API_PUB; any direct dependency on CZ_CONFIG_API_PVT risks breakage when Oracle patches the Configurator product family. The package must be compiled and executed against the APPS schema in every EBS 12.1.1 and 12.2.2 environment where Configurator is licensed and installed.