Search Results cz_ui_template_elements_pk




Overview
Explore in AI Chat

Overview

The table CZ.CZ_UI_TEMPLATE_ELEMENTS is a VALID dictionary object owned by the CZ schema, delivered as FND Design Data under the designation CZ.CZ_UI_TEMPLATE_ELEMENTS. Its documented purpose is to record the structure of UI Content Templates, specifically the internal references that each template holds to UI actions, conditions, and captions. In Oracle EBS Release 12.1.1 and 12.2.2, this table therefore functions as the structural backbone of template-driven user interface configuration, allowing a template definition to be decomposed into its constituent elements and each element to be resolved against its underlying UI definition.

The object is stored in the APPS_TS_SEED tablespace with PCT Free 10, consistent with its role as seed-data configuration. From a heuristic Data Vault modeling perspective, the mined relationship data classifies this object as standalone. No foreign keys are documented — the metadata records that CZ.CZ_UI_TEMPLATE_ELEMENTS does not reference any database object. This classification and absence of FK constraints should be treated as a modeling suggestion only; the table carries its own composite primary key and is referenced by APPS synonyms, indicating that referential integrity is enforced through the application layer rather than the database.

Key Information Stored

The table contains twelve documented columns. The most significant are the four components of the composite primary key, which together distinguish each row and also serve as the sole unique business-key candidate (unique index CZ_UI_TEMPLATE_ELEMENTS_PK on the same columns).

  • TEMPLATE_ID (NUMBER) — identifies the UI Content Template to which the element belongs.
  • UI_DEF_ID (NUMBER) — identifies the UI definition against which the element is resolved.
  • ELEMENT_TYPE (NUMBER) — classifies the element, distinguishing UI actions, conditions, and captions.
  • ELEMENT_ID (NUMBER) — the identifier of the specific element within that type.
  • PERSISTENT_ELEMENT_ID (NUMBER) — a stable identifier that survives regeneration or re-sequencing of the element.
  • DELETED_FLAG (VARCHAR2) — soft-delete indicator, allowing elements to be logically removed without physical deletion.
  • SEEDED_FLAG (VARCHAR2) — indicates whether the row originated from Oracle seed data or was created by the customer.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO column audit attributes.

The surrogate primary key is best understood as the composite tuple (TEMPLATE_ID, UI_DEF_ID, ELEMENT_TYPE, ELEMENT_ID); no separate single-column surrogate is documented. The unique index on these four columns is the only documented business-key candidate, so uniqueness of an element within a template/UI-definition context is enforced there.

Common Use Cases and Queries

Typical usage centers on introspecting or auditing the composition of a UI template. A developer validating why a given template renders a particular action or caption will join the element rows back to the template and UI definition. The standard query pattern follows the documented projection:

  • Enumerate all elements for a template: SELECT TEMPLATE_ID, UI_DEF_ID, ELEMENT_TYPE, ELEMENT_ID FROM CZ.CZ_UI_TEMPLATE_ELEMENTS WHERE TEMPLATE_ID = :template_id AND DELETED_FLAG = 'N';
  • Identify customer-modified versus seed elements: SELECT * FROM CZ.CZ_UI_TEMPLATE_ELEMENTS WHERE SEEDED_FLAG = 'N';
  • Detect element churn using the persistent identifier: SELECT ELEMENT_ID, PERSISTENT_ELEMENT_ID FROM CZ.CZ_UI_TEMPLATE_ELEMENTS WHERE PERSISTENT_ELEMENT_ID IS NULL;
  • Include soft-deleted elements when auditing historical template structure by omitting the DELETED_FLAG predicate.

Reporting use cases include migration validation (confirming that element counts survive an upgrade from 12.1.1 to 12.2.2), remediation scripts that reactivate soft-deleted elements, and impact analysis when a UI definition changes.

Related Objects

The documented dependency data records no outgoing references: CZ.CZ_UI_TEMPLATE_ELEMENTS does not reference any database object. It is referenced by an APPS synonym CZ_UI_TEMPLATE_ELEMENTS and by the trigger CZ_UI_TEMPLATE_ELEMENTS_T1, which typically maintains the WHO columns and default flags on insert and update. Because no FK metadata is supplied, the following relationships are the most significant logically adjoining objects and should be verified against the actual schema:

  • CZ.CZ_UI_TEMPLATES — the template header joined on TEMPLATE_ID.
  • CZ.CZ_UI_DEFINITIONS — the UI definition joined on UI_DEF_ID.
  • The UI element dictionaries resolved by ELEMENT_TYPE and ELEMENT_ID for actions, conditions, and captions.
  • The APPS synonym CZ_UI_TEMPLATE_ELEMENTS and trigger CZ_UI_TEMPLATE_ELEMENTS_T1, both explicitly documented as dependent.
  • CZ.CZ_UI_TEMPLATES_TL and related translation tables where template captions are localized.

These objects should be confirmed against the customer's actual data model, since the ETRM metadata for this table documents no explicit foreign-key constraints.