Results for “client_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The CZ_UITEMPL_CONTROLS_V view is a Configurator (CZ) product database object owned by the APPS schema. It is classified as a VIEW and holds a VALID status in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The object exposes a curated subset of Oracle Configurator user interface (UI) template type definitions, specifically the control-related template types that drive the presentation layer of the Configurator runtime user interface. Rather than presenting the complete catalog of UI template types, this view acts as a filtered projection whose purpose is to isolate a fixed, enumerated set of template types associated with a single template type group and client code.

In the context of EBS reporting and integration, the view provides a stable, low-cardinality reference set that downstream queries, concurrent programs, or extensions can consume without re-implementing the filtering logic. It is significant that the view carries a hard-coded predicate list in its defining SQL; this effectively pins the view to an Oracle-seeded configuration baseline rather than a customer-configurable one, making it a reliable lookup source but an unsuitable target for ad hoc extension.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view references two base objects:

  • CZ_UI_TEMPLATE_TYPES_V (VIEW) — the immediate source of all five projected columns. CZ_UITEMPL_CONTROLS_V is defined entirely as a restricted SELECT from this view, applying equality and IN-list predicates on TEMPLTYPE_GROUP_ID, CLIENT_CODE, and TEMPLATE_TYPE_ID.
  • FND_PROFILE (PACKAGE) — the standard Oracle Application Object Library profile option API package. Its presence in the dependency chain reflects the underlying dependency inherited through CZ_UI_TEMPLATE_TYPES_V, which resolves profile-option values (such as language or client context) when materializing template type rows.

The view text confirms the exact filter conditions applied to CZ_UI_TEMPLATE_TYPES_V: TEMPLTYPE_GROUP_ID equals 160, CLIENT_CODE equals 'NEWTEMPL', and TEMPLATE_TYPE_ID restricted to the enumerated set (161, 162, 164, 165, 6205, 6206). These literal values are Oracle-seeded identifiers, not runtime parameters.

Key Columns

The view exposes five columns, all inherited unchanged from CZ_UI_TEMPLATE_TYPES_V:

  • TEMPLATE_TYPE_NAME — the descriptive display name of the UI template type, used for identification in reports and user-facing output.
  • TEMPLATE_TYPE_ID — the numeric primary identifier of the template type. In this view it is constrained to the six seeded values listed above.
  • TEMPLTYPE_GROUP_NAME — the name of the grouping to which the template type belongs; in this view all rows resolve to the group identified by ID 160.
  • TEMPLTYPE_GROUP_ID — the numeric identifier of the template type group. Because the view predicates on the constant 160, this column is functionally constant across all returned rows.
  • CLIENT_CODE — the client classification code; here fixed to 'NEWTEMPL', again functionally constant for every row.

Two of the five columns are therefore invariant in practice, which is useful for consumers that expect consistent grouping and client context without filtering.

Common Use Cases and Queries

Typical uses include validating which control template types are active for the 'NEWTEMPL' client, driving lookups in Configurator UI extension code, and producing reference listings for functional documentation or migration checks. Because the view is pre-filtered, callers avoid embedding literal IDs in their own SQL.

  • Enumerating available control template types: SELECT TEMPLATE_TYPE_ID, TEMPLATE_TYPE_NAME FROM APPS.CZ_UITEMPL_CONTROLS_V ORDER BY TEMPLATE_TYPE_ID;
  • Confirming seeded membership for a specific ID: SELECT TEMPLATE_TYPE_NAME FROM APPS.CZ_UITEMPL_CONTROLS_V WHERE TEMPLATE_TYPE_ID = 6205;
  • Joining to base template type data for extended attributes not projected here: SELECT c.TEMPLATE_TYPE_NAME, t.* FROM APPS.CZ_UITEMPL_CONTROLS_V c, APPS.CZ_UI_TEMPLATE_TYPES_V t WHERE c.TEMPLATE_TYPE_ID = t.TEMPLATE_TYPE_ID;

Because TEMPLTYPE_GROUP_ID and CLIENT_CODE are fixed, queries should not treat them as variable filter dimensions. Any requirement to see template types outside the six seeded IDs must query CZ_UI_TEMPLATE_TYPES_V directly.