Search Results config_models_for_products




Overview

APPS.CZ_CF_API is the public configuration engine API package body for Oracle E-Business Suite Configure-to-Order (Cto) functionality. In EBS 12.1.1 and 12.2.2 it is delivered with the application as an API-classified package owned by APPS. Its purpose is to expose callable business logic for creating, copying, validating, deleting, and querying configuration models and configuration user interfaces (UIs). The package abstracts the underlying CZ_CONFIG_* schema so that forms, concurrent programs, Oracle Configurator, and custom extensions can manipulate configuration definitions programmatically without direct DML against the base CZ tables.

The body header (czcfapib.pls 120.15) reveals that CZ_CF_API also manages publication metadata, UI style selection (DHTML, Applet, JRAD, WEGA), and model instantiation semantics such as NETWORK, ROOT, GENERIC_INSTANCE_ROOT, INCLUDED, and component instance handling. This places the package at the center of both the repository side of CTO and the runtime side that resolves which model or UI applies to a given item, usage, or publication.

Key Procedures and Functions

Tables Accessed

The body references APPS synonyms for CZ_CONFIG_HDRS and CZ_CONFIG_HDRS_S (configuration headers and their translation/interface rows), CZ_CONFIG_ITEMS (configuration line items), CZ_CONFIG_ATTRIBUTES and CZ_CONFIG_EXT_ATTRIBUTES (attribute and extended-attribute values), CZ_CONFIG_INPUTS, CZ_CONFIG_USAGES, CZ_CONFIG_MESSAGES and CZ_CONFIG_MESSAGES_S (validation and runtime messages), CZ_MODEL_POOL_MAPPINGS, CZ_MODEL_PUBLICATIONS, CZ_DEVL_PROJECTS, CZ_DB_SETTINGS, and CZ_DB_LOGS (diagnostics). UTL_HTTP is also invoked, indicating that the package can call out to an external configuration service.

Usage Notes

CZ_CF_API is invoked from Oracle Configurator forms, CTO concurrent programs, and custom PL/SQL that must resolve or manipulate configuration models and UIs. It is referenced by 28 other packages, so modifications should be treated as high-impact. Because EBS 12.1.1 and 12.2.2 share the same underlying CZ schema, the API surface is identical across both releases; Upgrade patches are applied via the shared APPS code tree. Custom callers should set the correct UI style constant and use ANY_APPLICATION_ID / ANY_USAGE_ID when a generic lookup is intended.