Search Results cz_ui_actions_s

Overview

APPS.CZ_UIOA_PVT is a private (PVT class) PL/SQL package body within the Oracle E-Business Suite configuration management framework known as Oracle Configurator / ETRM (Enterprise Transaction Repository Model). Its name derives from the function it performs: CZ (the Configurator/ETRM product prefix) combined with UIOA, understood as "User Interface Object Actions." The package provides the internal implementation layer that manages the lifecycle of user interface objects — UI definitions, UI pages, UI actions, page elements, templates, and page sets — that constitute the runtime presentation model of configured products. It is the workhorse beneath public configuration APIs, handling creation, refresh, copying, and deletion of the UI model artifacts. The object is VALID in the APPS schema and, per the ETRM documentation, is referenced by two other packages but does not itself reference any object outside the documented dependency list. In 12.1.1 and 12.2.2 the package is a private companion to CZ_UIOA_PUB or a related public entry point, and its routines are not intended for direct invocation by customer code.

Key Procedures and Functions

The package exposes 27 documented procedures and functions, organized around four functional clusters.

• UI lifecycle: CREATE_UI, REFRESH_UI, REFRESH_UI_SUBTREE, CREATE_UI_PAGE, and ADD_CX_BUTTON build and rebuild UI definitions, individual pages, and their subtrees from the underlying model and template data.
• Deletion: DELETE_UI_SUBTREE, DELETE_UI_PAGE, DELETE_UI_PAGE_REF, DELETE_LOCAL_TEMPLATE, and DELETE_LOCAL_TEMPLATE_ELEM remove UI branches, pages, page references, and locally defined template elements while preserving referential consistency.
• Copy operations: COPY_UI_SUBTREE, COPY_UI_PAGE, COPY_UI_PAGE_REF, COPY_LOCAL_TEMPLATE, and COPY_LOCAL_TEMPLATE_ELEM duplicate UI structures, often as the first step in creating a revision or a new publication.
• Document and template handling: PARSE_JRAD_DOCUMENT, SAVE_DOCUMENT, and COPY_JRAD_DOCUMENT parse and persist JRad (JDeveloper/ADF-style) UI definitions using XMLDOM and XMLPARSER; CREATE_REGION_FROM_TEMPLATE and CONVERT_TEMPLATE_REFERENCE materialize UI regions from stored template definitions and translate template references into concrete page elements.

No parameter lists are documented in the ETRM metadata; signatures are considered private and subject to change between releases.

Tables Accessed

The package reads and writes a broad set of CZ_% tables. UI structure is stored in CZ_UI_DEFS, CZ_UI_PAGES (with its _S sequence view), CZ_UI_PAGE_ELEMENTS (_S), CZ_UI_PAGE_REFS (_S), CZ_UI_PAGE_SETS (_S), and CZ_UI_ACTIONS (_S). Templates and their elements are held in CZ_UI_TEMPLATES, CZ_UI_TEMPLATE_ELEMENTS, CZ_UI_REF_TEMPLATES, CZ_UI_REFS, and CZ_UI_CONT_TYPE_TEMPLS. CZ_UITEMPLS_FOR_PSNODES_V joins templates to page-set nodes. Model and rule context comes from CZ_PS_NODES, CZ_RULES, CZ_EXPRESSION_NODES, CZ_MODEL_PUBLICATIONS, and CZ_MODEL_REF_EXPLS. Localized text is read from CZ_INTL_TEXTS (_S) and CZ_LOCALIZED_TEXTS, and project metadata from CZ_DEVL_PROJECTS. Logging uses CZ_DB_LOGS, and JDR repository metadata is read via JDR_ATTRIBUTES and JDR_DOCBUILDER. The package also calls FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, CZ_SECURITY_PVT, CZ_DEVELOPER_UTILS_PVT, CZ_TYPES, DBMS_LOB, DBMS_UTILITY, and DBMS_XMLDOM.

Usage Notes

CZ_UIOA_PVT is a private package and is not a supported public API. It is invoked indirectly when Configurator/ETRM runtime operations refresh or publish a UI, when a developer synchronizes a UI definition from an external JRad document, or when a concurrent process regenerates UI pages for a published model. The presence of SAVE_DOCUMENT, PARSE_JRAD_DOCUMENT, and DBMS_XMLDOM/XDB dependencies indicates it participates in XML-based import and export of UI definitions. Because it manipulates core CZ_% tables directly, it should never be called from customer extensions; any customization should go through the corresponding public API. During upgrades between 12.1.1 and 12.2.2 the body is recompiled against the target schema, and the dependency on virtually every CZ_UI_% table means the two referencing packages must be recompiled whenever this body is invalidated.