Search Results cz_dev_enable_config_engine

Overview

APPS.CZ_UI_TEMPLATE_TYPES_V is a configuration and reporting view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, belonging to the Oracle Configurator / ETRM (Enterprise Trade and Relationship Management) schema family. It presents the universe of UI template types available to the Configurator at runtime, de-normalizing the relationships between template type groups, individual template types, and the client contexts in which each template applies. The view's distinguishing feature is the derivation of the CLIENT_CODE column, which enumerates the calling clients—NEWTEMPL, UIGEN, and RUNTIME—that may consume a given template type. Because the view overlays client membership and required-flag semantics onto the underlying signature and relationship data, it serves as a convenient integration and reporting source for identifying which template types are visible to authoring tools versus the runtime engine.

Underlying Base Objects

The view is defined entirely over four documented objects: CZ_SIGNATURES (synonym), CZ_TYPE_RELATIONSHIPS (synonym), the FND_PROFILE package, and DUAL. The inline DUAL union generates the three client-code rows referenced above, while CZ_TYPE_RELATIONSHIPS supplies the UTM (mandatory) and UTO (optional) links that bind a template type group (subject) to a template type (object). CZ_SIGNATURES is joined twice: once as TTGRP for the template type group and once as TTSPEC for the template type itself, both filtered on DELETED_FLAG = '0'. The FND_PROFILE package is invoked through FND_PROFILE.VALUE_WNPS('CZ_DEV_ENABLE_CONFIG_ENGINE'), which gates rows by configuration engine type alongside the hard-coded 'B' value.

Key Columns

• CLIENT_CODE — Derived from the inline client set (NEWTEMPL, UIGEN, RUNTIME) via SUBSTR(NVL(clnt.client_code,'RUNTIME'),1,8). Identifies the consuming client context; the search term associated with this view.
• REQUIRED_FLAG — Decoded from REL_TYPE_CODE: '1' for UTM (required), '0' for UTO (optional).
• TEMPLTYPE_GROUP_ID / TEMPLTYPE_GROUP_NAME / TEMPLTYPE_GROUP_DESCRIPTION / TEMPLTYPE_GROUP_SIGTYPE — Attributes of the group signature (TTGRP).
• TEMPLATE_TYPE_ID / TEMPLATE_TYPE_NAME / TEMPLATE_TYPE_DESCRIPTION / TEMPLATE_TYPE_SIGTYPE — Attributes of the individual template type signature (TTSPEC).

Common Use Cases and Queries

Typical uses include auditing template availability per client, reconciling required versus optional template memberships, and filtering out configuration-engine-incompatible types. The client predicate embedded in the view logic already restricts NEWTEMPL to subject types other than 2065, UIGEN to subject type 2065, and RUNTIME to subject types outside 160 and 2065, so querying directly returns the pre-filtered set.

SELECT client_code,
       templtype_group_name,
       template_type_name,
       required_flag
  FROM apps.cz_ui_template_types_v
 WHERE client_code = 'RUNTIME'
 ORDER BY templtype_group_id, template_type_id;

A second common pattern isolates mandatory template types for a given group:

SELECT template_type_id, template_type_name
  FROM apps.cz_ui_template_types_v
 WHERE required_flag = '1'
   AND templtype_group_id = :group_id;

Collectively, the view provides a stable, report-friendly projection of Configurator template metadata suitable for integration checks and administrative reporting.