Search Results cz_ui_templates_vv




Overview
Explore in AI Chat

Overview

CZ_UI_TEMPLATES_VV is a denormalized reporting view owned by the APPS schema in the Oracle E-Business Suite Configurator (CZ) product. It presents the user interface templates defined in the Configurator runtime layer, joining each template record to its owning UI definition, its template type signature, its parent container classification, its title text, its optional button bar template, and its localized message strings. The double-V suffix denotes a validation view that resolves code values into human-readable names using DECODE logic rather than an underlying lookup table.

In Oracle EBS 12.1.1 and 12.2.2, this view is primarily consumed for reporting, diagnostics, and integration. Because the Configurator generates dynamic UI screens for configured items at runtime, developers and administrators query this view to inventory templates, verify configuration completeness, and extract the descriptive text that appears in generated UI pages. The view also exposes the MAIN_MESSAGE_TEXT column, which resolves the MAIN_MESSAGE_ID foreign key to its localized string. This is the column most commonly referenced by users searching for "main_message_text," and it is the authoritative source of the main message body displayed by a Configurator UI template.

The view is defined as a multi-table outer join with ORDER BY TEMPLATE_ID, UI_DEF_ID, and it filters out logically deleted rows through repeated DELETED_FLAG conditions.

Underlying Base Objects

The ETRM metadata identifies four referenced base objects: CZ_LOCALIZED_TEXTS_VL, CZ_SIGNATURES, CZ_UI_DEFS, and CZ_UI_TEMPLATES. The first is itself a view exposing localized text strings, while the other three are synonyms resolving to the base Configurator tables.

  • CZ_UI_TEMPLATES (aliased UCT) is the driving table and supplies template identity, layout, container, message type, and the MAIN_MESSAGE_ID foreign key.
  • CZ_UI_DEFS (UDF) provides the master template flag and the UI definition name.
  • CZ_SIGNATURES (TSIG) supplies the template type name.
  • CZ_LOCALIZED_TEXTS_VL is joined twice: once as TILTX to resolve TITLE_ID into TITLE_STRING, and once as MMLTX to resolve MAIN_MESSAGE_ID into MAIN_MESSAGE_TEXT.
  • CZ_UI_TEMPLATES is joined a second time as BBTPL to resolve the button bar template name.

All joins are outer joins, and each joined table carries an explicit DELETED_FLAG = '0' predicate, so orphaned or deleted reference rows yield nulls rather than suppressing the template row.

Key Columns

Common Use Cases and Queries

Typical scenarios include retrieving the main message for a template, listing all templates by container type, and auditing seeded versus custom templates.

SELECT TEMPLATE_ID, TEMPLATE_NAME, MAIN_MESSAGE_TEXT
FROM   APPS.CZ_UI_TEMPLATES_VV
WHERE  MAIN_MESSAGE_TEXT IS NOT NULL;

SELECT TEMPLATE_NAME, MESSAGE_TYPE_NAME, TITLE_STRING
FROM   APPS.CZ_UI_TEMPLATES_VV
WHERE  MESSAGE_TYPE_NAME = 'ERROR';

SELECT TEMPLATE_NAME, PARENT_CONTAINER_TYPE_NAME, LAYOUT_UI_STYLE_INFO
FROM   APPS.CZ_UI_TEMPLATES_VV
WHERE  SEEDED_FLAG = '1'
ORDER  BY TEMPLATE_ID;

Because the view already decodes container, message, and layout codes, it is suitable for direct use in BI Publisher reports, Oracle Applications concurrent programs, and ad hoc SQL without additional lookup joins.