Search Results processing_page_templ_id

Overview

CZ_UI_COLLECT_TMPLS_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the CZ (Configurator) product. In releases 12.1.1 and 12.2.2 it exposes the relationship between user interface definitions (UI definitions) and the collection templates that are referenced by those definitions. Its primary purpose is to enumerate every template that an individual UI definition consumes, whether the template is bound directly to the UI definition or referenced indirectly through container types, page elements, pages, or actions. Because Configurator relies heavily on reusable UI templates to render configurable models, this view serves as the consolidated lookup that resolves those template references into a single, queryable set. For reporting and integration purposes, the view allows developers and analysts to identify which templates are attached to a given UI definition without having to navigate the many internal reference tables individually. It is therefore a convenient access point for template-impact analysis, migration checks, and diagnostics involving the template_id column.

Underlying Base Objects

The view is defined over six documented base objects, all exposed through APPS synonyms: CZ_UI_TEMPLATES, CZ_UI_DEFS, CZ_UI_CONT_TYPE_TEMPLS, CZ_UI_PAGE_ELEMENTS, CZ_UI_PAGES, and CZ_UI_ACTIONS. The core join links CZ_UI_DEFS to CZ_UI_TEMPLATES on UI_DEF_ID, restricted by a DELETED_FLAG of '0' on both sides. A UNION ALL subquery aggregates template references from four additional sources: container type templates (CZ_UI_CONT_TYPE_TEMPLS), page elements (CZ_UI_PAGE_ELEMENTS via CTRL_TEMPLATE_ID), pages (CZ_UI_PAGES via OUTER_PAGE_TEMPLATE_ID and PAGE_STATUS_TEMPLATE_ID), and actions (CZ_UI_ACTIONS via PAGE_TEMPLATE references) in CZ_UI_ACTIONS, CZ_UI_ACTIONS' PROCESSING_PAGE_TEMPL_ID). The EXISTS clause correlates these indirect references back to the UI definition and template, ensuring that only templates actually referenced by the definition are returned. The result is a normalized projection over otherwise fragmented template assignments.

Key Columns

The view exposes twelve columns. UI_DEF_ID identifies the owning UI definition, while NAME carries its name. DEVL_PROJECT_ID and COMPONENT_ID associate the definition with a development project and component. PERSISTENT_UI_DEF_ID and MASTER_TEMPLATE_FLAG, together with FROM_MASTER_TEMPLATE_ID, indicate master-template inheritance relationships. TEMPLATE_ID and TEMPLATE_NAME identify the referenced template, and TEMPLATE_TYPE classifies it. PARENT_CONTAINER_TYPE records the container context for the template, and TEMPLATE_UI_DEF_ID provides the UI definition that underlies the template itself. The template_id column is the most frequently queried attribute, since it is the join key to CZ_UI_TEMPLATES and the value analysts use to trace template usage.

Common Use Cases and Queries

Typical uses include listing all templates for a UI definition, locating which definitions use a specific template, and auditing master-template inheritance. For example, to find every UI definition that references a given template:

• SELECT UI_DEF_ID, NAME, TEMPLATE_ID, TEMPLATE_NAME FROM CZ_UI_COLLECT_TMPLS_V WHERE TEMPLATE_ID = :template_id; — resolves a template lookup initiated by a template_id search.
• SELECT TEMPLATE_ID, TEMPLATE_NAME, TEMPLATE_TYPE FROM CZ_UI_COLLECT_TMPLS_V WHERE UI_DEF_ID = :ui_def_id; — enumerates templates consumed by one definition.
• SELECT FROM_MASTER_TEMPLATE_ID, TEMPLATE_ID FROM CZ_UI_COLLECT_TMPLS_V WHERE MASTER_TEMPLATE_FLAG = 'Y'; — finds master-template derived definitions.

These queries support impact analysis before template changes, validation after migration, and integration extracts that require the definitive template-to-definition mapping.