Search Results parent_container_type_name




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.CZ_UI_TEMPLATES_VV is a view in the Oracle E-Business Suite Applications (APPS) schema that exposes the configuration metadata used by the Oracle Application Framework (OAF) / HTML user interface infrastructure delivered through the CZ product family. It presents the definitions of UI templates that govern how pages, regions, containers, and messaging elements are rendered when the corresponding UI definition is instantiated. The view is classified as VALID and is managed as FND Design Data under the design data identifier CZ.CZ_UI_TEMPLATES_VV. Because it consolidates template records with their localized display names and associated message and title strings, it functions as a reporting and integration surface rather than as a base transactional table. Administrators, support analysts, and developers query it to inspect, audit, and troubleshoot the template hierarchy that drives personalized or seeded page layouts, and downstream views and components reference it when resolving container-type-to-template associations.

Underlying Base Objects

The view is defined over the following documented base objects: CZ_UI_TEMPLATES (SYNONYM), CZ_UI_DEFS (SYNONYM), CZ_SIGNATURES (SYNONYM), and CZ_LOCALIZED_TEXTS_VL (VIEW). CZ_UI_TEMPLATES is the principal source of template records, supplying identifiers, flags, type codes, and layout style attributes. CZ_UI_DEFS contributes the UI definition name that contextualizes each template. CZ_SIGNATURES provides supporting signature data, and CZ_LOCALIZED_TEXTS_VL resolves the display strings—such as parent container type names and message type names—into the current session language. The view in turn is referenced by APPS.CZ_UI_CONT_TYPE_TEMPLS_VV, meaning template records surfaced here flow into higher-level container-type template mappings. The object therefore sits mid-hierarchy, joining definition-level and template-level metadata while remaining dependent on the localization layer for human-readable output.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing template hierarchies by parent container type, verifying which templates are seeded versus customer-defined, and tracing which UI definition owns a given template. A representative query follows.

SELECT TEMPLATE_ID, TEMPLATE_NAME, UI_DEF_NAME, TEMPLATE_TYPE_NAME, PARENT_CONTAINER_TYPE_NAME FROM APPS.CZ_UI_TEMPLATES_VV WHERE PARENT_CONTAINER_TYPE_NAME LIKE :container_name AND DELETED_FLAG = 'N';

To list master templates with their titles: SELECT TEMPLATE_NAME, TITLE_STRING, LAYOUT_UI_STYLE FROM APPS.CZ_UI_TEMPLATES_VV WHERE MASTER_TEMPLATE_FLAG = 'Y'; Analysts also join this view to CZ_UI_CONT_TYPE_TEMPLS_VV to map container types to the templates that render them, which supports troubleshooting rendering anomalies and sustaining consistent UI behavior across releases.