Search Results g_any_usage_name




Overview
Explore in AI Chat

Overview

APPS.CZ_API_PUB is a public application programming interface package within the Oracle E-Business Suite configuration management subsystem. Its name follows the EBS convention for packages classified as PUB, indicating that the routines it exposes form a supported, callable interface for external consumers rather than an internal implementation detail. The package sits at the boundary between Oracle's configurator and pricing modules and the broader set of EBS processes that require configuration data to be published, validated, or copied between publication contexts.

The $Header stamp in the package body records czapis.pls 120.0 2005/05/25, establishing the file as a long-standing component of the configuration offerings stack. The package is referenced by twenty-five other packages, a dependency count that confirms its role as a shared utility layer rather than a narrowly scoped helper. Within the ETRM 12.1.1 and 12.2.2 documentation sets it is catalogued under the APPS schema with a public API classification.

Key Procedures and Functions

The ETRM metadata for this object enumerates no documented procedures or functions, so the published reference set does not describe individual entry points. What the source excerpt does expose is the package's constant vocabulary, which in turn signals the operations the API supports.

  • Publication mode constants — G_PRODUCTION_PUB_MODE ('P') and G_TEST_PUB_MODE ('T') distinguish live publication from test publication, allowing callers to exercise the publication path without committing production-visible configuration.
  • Usage constants — G_ANY_USAGE_NAME ('Any Usage') supplies the default applicability scope when no usage name is supplied and the profile option CZ_PUBLICATION_USAGE is unset.
  • Config tree copy mode constants — G_NEW_HEADER_COPY_MODE ('H') creates a new configuration header and copies all configuration items, corresponding to save_config_behavior = "new_config" and used in re-order scenarios. G_NEW_REVISION_COPY_MODE ('R') creates a new revision instead, corresponding to save_config_behavior = "new_revision" and used for reconfiguration or repricing. These constants are the direct functional neighbours of the add_to_config_tree search term.
  • Validation context and type constants — G_PENDING_OR_INSTALLED ('P') and G_INSTALLED ('I') control whether validation resolves items against pending IB instances first or only against installed instances. VALIDATE_ORDER ('O'), VALIDATE_FULFILLMENT ('F'), VALIDATE_RETURN ('R'), and INTERACTIVE ('I') define the validation modes consumed by CZ_CF_API.VALIDATE.
  • Collection types — number_tbl_type and varchar_tbl_type provide the array parameters used throughout the publication routines.

Documented applicability parameters include optional configuration creation, model lookup, and effective dates; a required calling application identifier; and optional usage name and publication mode arguments.

Tables Accessed

The ETRM metadata records CZ_CONFIG_HDRS as the table reached through an APPS synonym. This header table is the anchor for configuration records, and the copy-mode constants described above operate directly against it: the 'H' mode inserts a new header, while the 'R' mode inserts a new revision beneath an existing header. Supporting configuration item and instance data referenced during validation and tree assembly are reached through the same synonym layer.

Usage Notes

CZ_API_PUB is invoked by the twenty-five dependent packages identified in the metadata rather than being exposed to end users directly. It is typically called from configurator and pricing flows — re-order, reconfigure, and repricing transactions — and from any custom code that needs to publish a configuration, validate it against order, fulfillment, or return rules, or clone a configuration tree into a new header or revision. Because the constants are declared in the package specification, callers should pass them by name rather than by literal value to remain safe across patch levels. Customisations should not modify the package body, since it is a shipped APPS object; wrapper logic belongs in a separate custom package that calls these public routines. The publication usage profile option CZ_PUBLICATION_USAGE should be reviewed on any environment that calls the publication routines without an explicit usage name.