Search Results template_type_name




Overview
Explore in AI Chat

Overview

APPS.CZ_UITEMPL_UTILITY_V is a configuration utility view in Oracle E-Business Suite, delivered as part of the application technology stack that supports UI template definitions and their association with client codes. In EBS 12.1.1 and 12.2.2, the view functions as a constrained projection of a broader template metadata repository, surfacing a small, fixed set of template type records that belong to a specific template group and client. Its purpose is to provide a stable, filtered read-only interface for downstream components and for the utility logic that binds template type identifiers to grouping and client context. Because the view hard-codes its filter predicates rather than accepting bind parameters, it behaves as a purpose-built lookup rather than a general-purpose reporting object; consumers query it directly, and the returned rows reflect the intersection of group, client, and template type identifiers defined at delivery time.

The user search term "template_type_id" is one of the three exposed key columns and is the primary identifier used to join the view to application template configuration. The view is especially relevant when diagnosing template resolution behavior, since the same column appears in the filter predicate as an explicit inclusion list.

Underlying Base Objects

The documented definition of the view is a single SELECT over CZ_UI_TEMPLATE_TYPES_V, filtered by templtype_group_id = 180, client_code = 'NEWTEMPL', and an explicit template type identifier list of (170, 174, 545, 565, 188, 622). The metadata also lists FND_PROFILE (PACKAGE) among referenced base objects. FND_PROFILE does not appear in the view text excerpt; it is referenced because the template type view it selects from resolves profile option values at runtime to determine the effective client code used in the client_code = 'NEWTEMPL' comparison. This means the view's result set is indirectly profile-sensitive: if the active client code resolves differently for a session, rows may be returned or suppressed accordingly.

The view itself performs no aggregation, no outer joins, and no set operators. It is a simple filter-and-project construct, which makes it inexpensive to query but tightly coupled to the delivery values of group 180 and the NEWTEMPL client.

Key Columns

  • TEMPLATE_TYPE_ID — The numeric identifier of an individual UI template type. This is the column most commonly searched and used for joins to template configuration and assignment data. The view pre-restricts it to the values 170, 174, 545, 565, 188, and 622.
  • TEMPLATE_TYPE_NAME — The descriptive name corresponding to TEMPLATE_TYPE_ID, used for display and reporting.
  • TEMPLTYPE_GROUP_ID — The template grouping identifier. For this view the value is always 180, since the predicate fixes it.
  • TEMPLTYPE_GROUP_NAME — The descriptive name of the template group.
  • CLIENT_CODE — The client context for which the template types are valid. The view restricts this to 'NEWTEMPL', so every returned row carries that value.

Common Use Cases and Queries

The primary use case is resolving the names and group context for the specific template types required by the template utility. A typical query returns the full filtered set:

SELECT template_type_id, template_type_name, templtype_group_id, templtype_group_name, client_code FROM apps.cz_uitempl_utility_v;

Because the view already filters on template_type_id, an additional predicate on that column is only useful to narrow to a single delivered identifier, for example WHERE template_type_id = 170. Analysts commonly join the view to other template-related tables on TEMPLATE_TYPE_ID to enrich it with assignment or layout metadata:

SELECT u.template_type_id, u.template_type_name FROM apps.cz_uitempl_utility_v u ORDER BY u.template_type_id;

It is also used in troubleshooting to confirm which template types are bundled for the NEWTEMPL client in a given environment, and to verify that expected identifiers such as 170 or 622 remain present after patching. For broader reporting across all client codes and groups, the underlying CZ_UI_TEMPLATE_TYPES_V should be queried directly, since the utility view deliberately limits scope.