Search Results persistent_ui_def_id




Overview
Explore in AI Chat

Overview

APPS.CZ_UI_COLLECT_TMPLS_V is a seeded Oracle EBS view belonging to the application's user interface configuration framework. It presents a consolidated list of UI definitions (CZ_UI_DEFS) joined with the templates (CZ_UI_TEMPLATES) that those definitions either own directly or reference indirectly through the surrounding page, element, action, or container-type metadata. In practice, it answers the question "which templates apply to a given UI definition, and by what relationship?" — supporting reporting, troubleshooting, and integration over the configuration that drives Oracle's configurable UI and collection (CZ) infrastructure. The view is exposed under the APPS schema and is available in both 12.1.1 and 12.2.2. Users searching on template_id will find it here as a first-class column, alongside the definition's identity columns such as ui_def_id, name, devl_project_id, and component_id.

Underlying Base Objects

The view is defined over six ETRM-documented base objects, all referenced through public synonyms resolved to the APPS-visible schema:

  • CZ_UI_DEFS — the master UI definition records (aliased UDF). Supplies ui_def_id, name, devl_project_id, component_id, persistent_ui_def_id, master_template_flag, and from_master_template_id.
  • CZ_UI_TEMPLATES — the template definitions (aliased UIT). Supplies template_id, template_name, template_type, parent_container_type, and the template's own ui_def_id, exposed here as template_ui_def_id.
  • CZ_UI_CONT_TYPE_TEMPLS — associates container types with templates; contributes template references through the container-type path.
  • CZ_UI_PAGE_ELEMENTS — page element records that can carry a control template (ctrl_template_id, ctrl_template_ui_def_id).
  • CZ_UI_PAGES — page records contributing outer_page_template_id and page_status_template_id references.
  • CZ_UI_ACTIONS — action records contributing processing_page_templ_id / proc_page_templ_ui_def_id.

All source tables are filtered with deleted_flag = '0' to exclude soft-deleted configuration rows. The view's logic is an OR between a direct join (UDF.ui_def_id = UIT.ui_def_id) and an EXISTS clause over a UNION ALL of template references gathered from container-type templates, page elements, pages, and actions, matched back to CZ_UI_TEMPLATES on both template_id and the template's ui_def_id.

Key Columns

Common Use Cases and Queries

Typical uses include auditing template usage, resolving which template drives a given page region, and diagnosing conflicts after a patch or clone. A direct lookup by template:

  • SELECT ui_def_id, name, template_id, template_name, template_type FROM apps.cz_ui_collect_tmpls_v WHERE template_id = :template_id;
  • SELECT name, template_name, parent_container_type FROM apps.cz_ui_collect_tmpls_v WHERE ui_def_id = :ui_def_id;
  • SELECT DISTINCT template_type FROM apps.cz_ui_collect_tmpls_v WHERE master_template_flag = 'Y';

Because the view unions several reference paths and applies an EXISTS predicate, joins on template_id can return multiple rows per definition; use DISTINCT when a single row per definition is required. For deeper analysis, join the view back to CZ_UI_DEFS or CZ_UI_TEMPLATES on ui_def_id to enrich results with additional configuration attributes.