Search Results main_message_text




Overview
Explore in AI Chat

Overview

APPS.CZ_UI_CONT_TYPE_TEMPLS_VV is a reporting and integration view in the Oracle E-Business Suite application schema (APPS). Its name and column set identify it as an inventory-style view that flattens the relationship between configurable user interface (UI) definitions, content types, and the templates associated with them. The object is registered in FND Design Data under the application short name CZ (CZ.CZ_UI_CONT_TYPE_TEMPLS_VV) and carries a status of VALID in the documented 12.2.2 environment, with the same definition validated for 12.1.1.

The suffix _VV indicates a validation view. These views are constructed so that forms, concurrent programs, and external integrations can read descriptive content for a UI definition without navigating the full normalized model. The view presents each UI definition alongside its content-type classification and its associated template metadata, including user-facing text such as the title string and the main message text. For users who searched on main_message_text, this view is the documented source for the prompt or body text rendered on a UI screen or template, making it the natural entry point for reporting on interface text or extracting it for translation and review.

Underlying Base Objects

The view is defined over four documented objects: CZ_SIGNATURES, CZ_UI_CONT_TYPE_TEMPLS, CZ_UI_DEFS, and the nested view CZ_UI_TEMPLATES_VV. At the 12.2.2 metadata level these source objects are exposed through synonyms owned by APPS.

  • CZ_UI_DEFS supplies the UI definition header attributes, including UI_DEF_ID and UI_DEF_NAME.
  • CZ_UI_CONT_TYPE_TEMPLS provides the association between a UI definition, its content type, and the specific template record.
  • CZ_UI_TEMPLATES_VV is a nested validation view contributing the template-level descriptive attributes such as template name, description, title string, main message text, and layout style information.
  • CZ_SIGNATURES is referenced to support signature or identification logic applied to the underlying definitions.

The documented dependency list notes that CZ_UI_CONT_TYPE_TEMPLS_VV is not referenced by any database object. It sits at the top of the dependency chain; no other EBS object depends on it, so changes to the view do not cascade to dependent compiled objects.

Key Columns

All columns are exposed with the datatypes documented in the ETRM metadata.

  • UI_DEF_ID (NUMBER) — primary identifier linking the row to its UI definition header.
  • MASTER_TEMPLATE_FLAG and TEMPLATE_FLAG_INFO (VARCHAR2) — indicate whether the template is the master and carry descriptive flag text.
  • UI_DEF_NAME (VARCHAR2 255) — the name of the UI definition.
  • CONTENT_TYPE (NUMBER) and CONTENT_TYPE_NAME / CONTENT_TYPE_DESCR (VARCHAR2 30 / 2000) — the numeric content-type key plus its display name and description.
  • SEEDED_FLAG and DELETED_FLAG (VARCHAR2) — standard Oracle flags distinguishing Oracle-seeded rows from user-defined rows and indicating soft deletes.
  • TEMPLATE_ID and TEMPLATE_UI_DEF_ID (NUMBER) — the template identifier and the UI definition to which the template belongs.
  • TEMPLATE_NAME (VARCHAR2 255) and TEMPLATE_DESC (VARCHAR2 2000) — template display attributes.
  • TITLE_STRING and MAIN_MESSAGE_TEXT (VARCHAR2 2000) — the rendered title and body/prompt text of the template. MAIN_MESSAGE_TEXT is the column most frequently queried for user-facing message content.
  • LAYOUT_UI_STYLE_INFO (VARCHAR2 15) — layout or style indicator.
  • JRAD_DOC (VARCHAR2 255) — reference to the associated JRAD document.

Common Use Cases and Queries

Typical uses include auditing interface text, extracting message content for localization, and reporting which UI definitions and content types have associated templates. The following queries reflect the documented column list.

List all UI definitions with their content types and templates:

  • SELECT ui_def_name, content_type_name, template_name, title_string, main_message_text FROM apps.cz_ui_cont_type_templs_vv;

Isolate the main message text for a specific UI definition:

  • SELECT ui_def_name, template_name, main_message_text FROM apps.cz_ui_cont_type_templs_vv WHERE ui_def_name = :ui_def_name;

Locate user-defined, non-deleted rows carrying message text that may require review or translation:

  • SELECT ui_def_id, content_type_name, main_message_text FROM apps.cz_ui_cont_type_templs_vv WHERE seeded_flag = 'N' AND deleted_flag = 'N' AND main_message_text IS NOT NULL;

Search for message text matching a pattern and join back to the UI definition key:

  • SELECT ui_def_id, ui_def_name, main_message_text FROM apps.cz_ui_cont_type_templs_vv WHERE UPPER(main_message_text) LIKE '%' || UPPER(:keyword) || '%';

Because the view is not referenced by any other database object, it can be queried directly in reports, SQL*Plus extracts, or integration layers without concern for invalidating dependent compiled objects. When extracting large text sets, filter on DELETED_FLAG and SEEDED_FLAG to limit results to the intended population.