Search Results templtype_group_description




Overview
Explore in AI Chat

Overview

CZ_UI_TEMPLATE_TYPES_V is a reporting view owned by the APPS schema within the Oracle Configurator (CZ) product family. It presents a denormalized, flattened representation of the relationship between Configurator template type groups and the individual template types they contain. In Oracle EBS 12.1.1 and 12.2.2, this view supports the Configurator user interface generation and runtime rendering logic by exposing signature-based template metadata tagged with a target client context.

The view is particularly significant because it resolves the ambiguous "template_type_sigtype" concept that users frequently search for. Rather than requiring callers to join CZ_SIGNATURES and CZ_TYPE_RELATIONSHIPS directly, the view surfaces SIGNATURE_TYPE at both the group and specification level, aliased as TEMPLTYPE_GROUP_SIGTYPE and TEMPLATE_TYPE_SIGTYPE respectively. This makes it a convenient access point for reporting on how template types are classified by signature type.

Underlying Base Objects

The view is defined over the following documented base objects:

  • CZ_SIGNATURES (synonym) — referenced twice, as TTGRP (template type group) and TTSPEC (template type specification/template type).
  • CZ_TYPE_RELATIONSHIPS (synonym) — aliased RELS, providing the UTM/UTO relationship links between subject (group) and object (type).
  • FND_PROFILE (package) — referenced for profile option context, consistent with Configurator UI generation.
  • DUAL (synonym) — used to generate the synthetic CLIENT_CODE rows via UNION ALL.

The join semantics rely on RELS.SUBJECT_TYPE equating to TTGRP.SIGNATURE_ID and RELS.OBJECT_TYPE equating to TTSPEC.SIGNATURE_ID, with DELETED_FLAG = '0' filters applied to exclude soft-deleted records. Only relationship types 'UTM' and 'UTO' participate. The synthetic CLNT inline view produces three client codes ('NEWTEMPL', 'UIGEN', 'RUNTIME'), each gated by SUBJECT_TYPE predicates (2065, 160, and others), effectively partitioning template types by consumer context.

Key Columns

  • CLIENT_CODE — Truncated to 8 characters; identifies the consuming UI context ('NEWTEMPL', 'UIGEN', or 'RUNTIME'). When the client code is null in source, NVL substitutes 'RUNTIME'.
  • REQUIRED_FLAG — Single-character derived flag; DECODE maps 'UTM' to '1' and 'UTO' to '0', with a fallback of 'X'.
  • TEMPLTYPE_GROUP_ID / _NAME / _DESCRIPTION — Attributes of the template type group signature.
  • TEMPLTYPE_GROUP_SIGTYPE — The signature type of the group, derived from TTGRP.SIGNATURE_TYPE.
  • TEMPLATE_TYPE_ID / _NAME / _DESCRIPTION — Attributes of the individual template type signature.
  • TEMPLATE_TYPE_SIGTYPE — The signature type of the template type, derived from TTSPEC.SIGNATURE_TYPE. This is the column most relevant to the "template_type_sigtype" search, exposing where the underlying signature type classification lives.

Common Use Cases and Queries

Typical scenarios include auditing which template types are classified under a given signature type, determining which client contexts (New Template, UI Generation, Runtime) expose a template type, and filtering to required template types using REQUIRED_FLAG.

Sample query to list template types and their signature types by client context:

To isolate runtime-only template types for a specific signature type:

  • SELECT * FROM APPS.CZ_UI_TEMPLATE_TYPES_V WHERE CLIENT_CODE = 'RUNTIME' AND TEMPLATE_TYPE_SIGTYPE = :p_sigtype;

To find required template types only:

  • SELECT TEMPLATE_TYPE_ID, TEMPLATE_TYPE_NAME FROM APPS.CZ_UI_TEMPLATE_TYPES_V WHERE REQUIRED_FLAG = '1';

Because it is a view rather than a table, it should be treated as read-only, and performance depends on the cardinality and indexing of CZ_SIGNATURES and CZ_TYPE_RELATIONSHIPS. The ORDER BY on CLIENT_CODE, TEMPLTYPE_GROUP_ID, and TEMPLATE_TYPE_ID provides deterministic sequencing suitable for UI rendering and report output.