Results for “template_type_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view CZ_UITEMPL_MESSAGES_V is an Oracle E-Business Suite configuration object owned by the APPS schema and delivered as part of the CZ – Configurator product family. In EBS 12.1.1 and 12.2.2 it exposes a curated subset of Configurator user-interface template type metadata, specifically the template types associated with UI message rendering used by the Configurator runtime. The view is documented as VALID and is classified as a reporting and integration access point rather than a transactional entity.

Its role is to present a stable, pre-filtered projection of template type records so that Configurator message templates can be identified and referenced consistently by concurrent programs, extensions, and diagnostic queries. Because the view applies fixed predicates on template type, template group, and client code, consumers obtain an already-scoped list of message-capable UI templates without needing to reconstruct the filter logic themselves.

Underlying Base Objects

The documented referenced base objects are CZ_UI_TEMPLATE_TYPES_V (a view) and FND_PROFILE (a package). The primary source is CZ_UI_TEMPLATE_TYPES_V, from which CZ_UITEMPL_MESSAGES_V selects five columns. The dependency on FND_PROFILE indicates that profile option values participate in the resolution logic of the underlying template view, reflecting the standard EBS pattern where Configurator behavior is governed by profile settings such as the active client code.

The filter restricts output to TEMPLTYPE_GROUP_ID values 168 and 620, a CLIENT_CODE of NEWTEMPL, and an enumerated set of TEMPLATE_TYPE_ID values (600, 601, 603, 620, 606, 608, 610, 628, 616, 630, 622, 621, 623, 624, 625, and 639). These literals correspond to the message-oriented UI template definitions shipped with the Configurator UI generator.

Key Columns

• TEMPLATE_TYPE_NAME – Descriptive name of the UI template type; used as the human-readable identifier in reports and diagnostics.
• TEMPLATE_TYPE_ID – Numeric primary identifier of the template type; the value constrained by the view's IN-list and the key used in joins to other Configurator metadata.
• TEMPLTYPE_GROUP_NAME – Name of the template type group that classifies the template; limited to the groups identified by group IDs 168 and 620.
• TEMPLTYPE_GROUP_ID – Numeric identifier of the template type group, useful for grouping and sorting output by functional category.
• CLIENT_CODE – Client identifier indicating the UI rendering context; the view returns only NEWTEMPL, denoting the current template-based client implementation.

Common Use Cases and Queries

The view is typically used to determine which message-related UI template types are active for a given implementation, to validate that expected template IDs are present, and to supply lookup data to extensions that render or translate Configurator messages. A basic listing follows:

• SELECT template_type_id, template_type_name, templtype_group_id FROM cz_uitempl_messages_v ORDER BY templtype_group_id, template_type_id; — enumerates all message template types returned by the view.
• SELECT template_type_name FROM cz_uitempl_messages_v WHERE template_type_id = 600; — confirms existence and naming of a specific template type.
• SELECT templtype_group_name, COUNT(*) FROM cz_uitempl_messages_v GROUP BY templtype_group_name; — summarizes counts by template group for auditing purposes.

Because all filtering is embedded in the view definition, queries against it require no additional WHERE predicates for client or group scoping. Consumers should treat the returned set as implementation-defined; template IDs are fixed literals delivered by Oracle, and the view text should be reviewed after any Configurator patch or upgrade in 12.1.1 or 12.2.2 to confirm the enumerated IDs and group IDs remain valid.