Search Results cz_ui_cont_type_templs_vv




Overview
Explore in AI Chat

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, the object CZ_UI_CONT_TYPE_TEMPLS_VV is a read-only view owned by the APPS schema within the Oracle Configurator (CZ) product family. Its role is to present a denormalized, human-readable projection of the relationship between configurator UI definitions, UI content types, and the UI templates assigned to them. The suffix _VV conventionally denotes a "value view" — a view intended to join coded identifier columns with their descriptive translations, primarily for reporting, diagnostics, and integration extracts rather than for transactional processing.

The view resolves surrogate keys such as UI_DEF_ID, CONTENT_TYPE, and TEMPLATE_ID into meaningful names and descriptions sourced from the configurator metadata tables. It also decodes the MASTER_TEMPLATE_FLAG value into a descriptive string using a DECODE expression, labelling values as USER INTERFACE, UI MASTER TEMPLATE, or the various FRAGMENT categories (BOM settings, pagination, non-BOM settings). This makes the view particularly useful for administrators auditing how content-type templates are configured across a Configurator implementation.

Underlying Base Objects

The view is defined over four documented base objects, all referenced as SYNONYMs except the trailing nested view:

  • CZ_UI_CONT_TYPE_TEMPLS — the driving table (UTT alias), holding the UI definition, content type, template mapping, and master template flags.
  • CZ_UI_DEFS — the (UDF alias) source of the UI definition NAME.
  • CZ_SIGNATURES — the (SIG alias) source of the content type NAME and DESCRIPTION.
  • CZ_UI_TEMPLATES_VV — the (TPLV alias) nested value view supplying template name, description, title string, main message text, layout style information, and the JRAD document reference.

Every join to the secondary objects is an outer join ((+)), each further qualified by a '0' = ...DELETED_FLAG (+) predicate. This design ensures the driving row from CZ_UI_CONT_TYPE_TEMPLS is never lost even where the related definition, signature, or template has been soft-deleted or is absent.

Key Columns

Common Use Cases and Queries

Typical scenarios include verifying which templates are attached to each content type, identifying seeded versus custom templates, and diagnosing missing or soft-deleted template references. A representative query lists all active template assignments with resolved names:

  • SELECT UI_DEF_NAME, CONTENT_TYPE_NAME, TEMPLATE_NAME, TEMPLATE_FLAG_INFO FROM APPS.CZ_UI_CONT_TYPE_TEMPLS_VV WHERE DELETED_FLAG = '0';
  • Filter to master templates only: add AND MASTER_TEMPLATE_FLAG = '1'.
  • Detect orphaned mappings: add AND TEMPLATE_NAME IS NULL to reveal assignments whose template is missing or deleted.

Because it encapsulates multiple outer joins and decode logic, the view is the preferred access point for reports and interfaces rather than querying the base configurator tables directly.