Search Results cz_ui_actions




Overview
Explore in AI Chat

Overview

CZ_UI_ACTIONS is a table in the CZ (Configurator) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores user-interface Actions definition — the metadata that drives how Configurator-generated user interfaces respond to user interactions. Each row defines a single action attached to a UI element on a source page within a UI definition, covering navigation targets, window behavior, rendering conditions, and optional processing-page presentation.

From a Data Vault modeling perspective, the mined heuristic classification is standalone. No foreign-key relationships were identified in the documented FK structure, so the table is best treated as an independent object rather than a hub, link, or satellite. Its composite primary key combines action, UI definition, source page, and edition context, distinguishing it as an edition-aware definition table typical of Configurator metadata in 12.2.2.

Key Information Stored

The documented physical schema contains 35 columns. The most significant are:

Common Use Cases and Queries

Typical uses include auditing the actions defined on a Configurator page, tracing navigation targets, and diagnosing actions that fail to render or launch.

  • List actions for a UI definition and page: SELECT ui_action_id, ui_action_type, target_url FROM cz.cz_ui_actions WHERE ui_def_id = :p_ui_def_id AND source_page_id = :p_page_id AND deleted_flag = 'N' AND zd_edition_name = :p_edition;
  • Report seeded versus customer-defined actions: filter on SEEDED_FLAG.
  • Identify URL-launching actions by joining URL_PROPERTY_ID to the corresponding property definition.
  • Edition comparisons: group by ZD_EDITION_NAME to see which actions exist in each edition.
  • Trace rendering conditions by joining RENDER_CONDITION_ID to the condition definition table.

Related Objects

The documented FK structure yields no joins; relationships are implied by the ID columns rather than enforced foreign keys. Significant related objects include:

  • CZ_UI_DEFINITIONS — joined on UI_DEF_ID; the owning UI definition.
  • CZ_UI_PAGES (or page metadata) — joined on SOURCE_PAGE_ID.
  • CZ_UI_ELEMENTS / component metadata — joined on ELEMENT_ID and CONTEXT_COMPONENT_ID.
  • CZ_UI_CONDITIONS — joined on RENDER_CONDITION_ID.
  • CZ_UI_NODES — joined on TARGET_UI_DEF_ID, TARGET_PAGE_ID, or TARGET_PERSISTENT_NODE_ID.
  • CZ_URL_PROPERTIES — joined on URL_PROPERTY_ID.
  • CZ_TEXT / text definitions — joined on PAGE_TITLE_TEXT_ID, MAIN_MESSAGE_TEXT_ID, and PROCESSING_CAPTION_TEXT_ID.
  • CZ_PAGE_TEMPLATES — joined on PROCESSING_PAGE_TEMPL_ID and PROC_PAGE_TEMPL_UI_DEF_ID.
  • CZ_UI_DEFS_TL — for translatable names of owning and target definitions.

Because these joins are not enforced at the database level, referential integrity is maintained by Configurator application logic.