Search Results generic_instance_root

Overview

APPS.CZ_CONFIG_API_PUB is the public API package for the Oracle E-Business Suite Configurator (CZ) module, which supports the Oracle Configurator and Configure-to-Order (CTO) functionality within Oracle Order Management and Manufacturing. The package exposes a supported, externally callable interface for manipulating configuration data—most notably for copying an existing configuration model (a configuration header and its associated revision) into a new configuration. It serves as the sanctioned entry point for developers, integrators, and concurrent programs that need to duplicate configurations programmatically without directly touching the underlying Configurator data model.

This package body is a thin wrapper: as documented in the header comment (Bug 7673721, $Header: czcfgapb.pls 120.8 2012/01/24), the substantive business logic was relocated to the companion package CZ_CONFIG_API_PVT. CZ_CONFIG_API_PUB therefore primarily performs argument pass-through and provides the stable public signature that external callers depend upon. This separation of public and private layers is a standard Oracle EBS API design pattern that allows internal logic to evolve without breaking the published contract.

Key Procedures and Functions

ETRM documentation lists three documented program units in this package:

• COPY_CONFIGURATION — Copies an existing configuration identified by its configuration header ID and revision number into a new configuration. Callers specify a copy mode, and the procedure returns the identifiers of the newly created configuration header and revision, along with tables mapping original item IDs to newly created item IDs. It also returns the standard API status outputs (return status, message count, message data). Optional parameters allow the caller to control the handling of deleted components and to supply a new name for the copied configuration.
• COPY_CONFIGURATION_AUTO — Performs an automated variant of the configuration copy operation. It shares the same conceptual inputs and outputs as COPY_CONFIGURATION but applies automatic handling of the configuration during the copy. Both procedures delegate their work directly to identically named procedures in CZ_CONFIG_API_PVT.
• VERIFY_CONFIGURATION — Validates the integrity and consistency of a configuration. It is used to confirm that a configuration is structurally valid before or after operations such as copying.

Tables Accessed

The provided ETRM metadata does not enumerate specific base tables accessed through APPS synonyms. Because the package is a wrapper around CZ_CONFIG_API_PVT, the actual DML and queries against the Configurator schema tables (configuration headers, revisions, component/item associations, and the originating item mapping) are performed within the private package. Callers should treat CZ_CONFIG_API_PUB as the logical owner of those configuration records and rely on the returned item ID mapping tables rather than querying the underlying tables directly.

Usage Notes

This package is typically invoked when a configuration must be duplicated—such as creating a variant of a previously configured model, cloning a configuration for a new sales order or quote, or mass-copying configurations through a concurrent program. It is referenced by eleven other packages in the E-Business Suite, confirming its role as a shared, foundational API rather than an isolated utility.

Because it is classified as a PUB (public) API, it is the correct target for custom code and extensions; the corresponding CZ_CONFIG_API_PVT package should not be called directly. Standard EBS API conventions apply: callers must pass a valid API version, check the x_return_status output for success or error conditions, and iterate over the message stack using x_msg_count and x_msg_data when failures occur. Typical invocation contexts include Configurator-related forms, order and quote processing logic, and custom PL/SQL or concurrent programs that need to copy configuration definitions programmatically.