Search Results cz_ui_template_elements




Overview

CZ_UI_TEMPLATE_ELEMENTS is a table in the CZ schema owned by the Oracle Configurator module (CZ) in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the individual UI Content Template components that make up a Configurator user interface definition. Its documented description is "UI Content Template components." In practice, this object functions as the association table that maps template definitions (via TEMPLATE_ID) and UI definitions (via UI_DEF_ID) to the specific elements that compose a runtime configuration UI — such as groups, prompts, options, and their relative positioning — with the element being tracked by ELEMENT_TYPE and ELEMENT_ID.

The heuristic Data Vault classification derived from the foreign-key structure is standalone. This suggests that, from a modeling standpoint, the table can be treated as an independent structure rather than a clearly identifiable hub, link, or satellite; it carries its own composite key and lifecycle columns without strongly normalized dependence on a parent hub table in the Data Vault sense.

Key Information Stored

The table is documented with twelve columns. The most operationally significant are:

  • TEMPLATE_ID — identifies the owning UI Content Template. Part of the composite primary key.
  • UI_DEF_ID — identifies the specific UI definition within the template. Part of the composite primary key.
  • ELEMENT_TYPE — discriminates the kind of UI element (for example, group, prompt, or option). Part of the composite primary key.
  • ELEMENT_ID — identifies the concrete element instance. Part of the composite primary key.
  • PERSISTENT_ELEMENT_ID — a durable identifier used to preserve element identity across template regeneration or reseeding.
  • DELETED_FLAG — soft-delete indicator, allowing elements to be logically removed while preserving history.
  • SEEDED_FLAG — distinguishes seeded (Oracle-delivered) elements from customer-defined ones.
  • CREATION_DATE, CREATED_BY — standard audit creation columns.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns for the most recent modification.

The surrogate primary key is CZ_UI_TEMPLATE_ELEMENTS_PK, defined over the four-column composite (TEMPLATE_ID, UI_DEF_ID, ELEMENT_TYPE, ELEMENT_ID). The same four-column combination is documented as the unique index acting as the business-key candidate, so the surrogate key and the business key coincide in this object.

Common Use Cases and Queries

Typical scenarios include auditing which elements belong to a given UI template, detecting orphaned elements, and comparing seeded versus customer-defined configuration content.

Enumerate all active elements for a template:

  • SELECT UI_DEF_ID, ELEMENT_TYPE, ELEMENT_ID, PERSISTENT_ELEMENT_ID FROM CZ.CZ_UI_TEMPLATE_ELEMENTS WHERE TEMPLATE_ID = :template_id AND NVL(DELETED_FLAG,'N') = 'N';

Count distinct element types per UI definition:

  • SELECT UI_DEF_ID, ELEMENT_TYPE, COUNT(*) FROM CZ.CZ_UI_TEMPLATE_ELEMENTS GROUP BY UI_DEF_ID, ELEMENT_TYPE;

Isolate seeded content for impact analysis before upgrades:

  • SELECT TEMPLATE_ID, ELEMENT_ID, SEEDED_FLAG FROM CZ.CZ_UI_TEMPLATE_ELEMENTS WHERE SEEDED_FLAG = 'Y';

Related Objects

Because the documented relationship classification is standalone, no explicit foreign keys are listed in the provided metadata. The columns nonetheless imply natural join paths to the following Configurator objects:

These associations are inferred from naming conventions and documented column semantics; the sole authoritative key constraint in the metadata is CZ_UI_TEMPLATE_ELEMENTS_PK.