Results for “value_str”

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

Overview

CZ_UI_PROPERTIES is a Configurator (CZ) module table in the Oracle E-Business Suite schema CZ. Its documented purpose is to attach property values to user interface definitions. In the Oracle Configurator architecture, UI definitions describe how a configuration model is presented to end users, and this table supplies the per-UI property values that control or describe those presentations. The object is marked VALID in the ETRM 12.2.2 dictionary and carries the standard Oracle Applications audit columns alongside Configurator-specific effective-dating and security columns.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. That characterization is a heuristic suggestion rather than a documented Oracle design statement: the table records attribute values (VALUE_STR and related control columns) that describe a parent entity, which is the classic profile of a satellite attached to a hub or link. The parent entity in this case is the UI definition row in CZ_UI_DEFS. Analysts building a dimensional or Data Vault layer over EBS should treat CZ_UI_PROPERTIES as descriptive context keyed by UI definition rather than as an independent business entity.

Key Information Stored

The documented schema exposes 14 columns. The most significant include:

• UI_DEF_ID — the foreign key to CZ_UI_DEFS. This is the principal join key and identifies which UI definition the property belongs to.
• KEY_STR — a string key that, together with UI_DEF_ID, forms the primary key. It identifies the specific property being valued for that UI.
• VALUE_STR — the property value itself, stored in string form.
• DELETED_FLAG — soft-delete indicator, allowing property rows to be logically retired without physical removal.
• EFF_FROM and EFF_TO — effective date range governing when the property value is considered active.
• EFF_MASK — mask governing effective-dating behavior for the row.
• SECURITY_MASK — mask controlling visibility or access restrictions on the property.
• CHECKOUT_USER — identifies the user who has the row checked out, supporting concurrent development of Configurator definitions.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle Applications audit trail columns.

The surrogate/primary key is defined by the CZ_UI_PROPERTIES_PK constraint over the composite of KEY_STR and UI_DEF_ID. The unique index CZ_UI_PROPERTIES_PK therefore serves as the documented business-key candidate: a property may appear only once per UI definition. No separate single-column surrogate identifier is documented.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios revolve around determining which properties are configured for a given UI, and what their current effective values are. A standard joined query retrieves UI definitions with their property values:

• SELECT p.UI_DEF_ID, p.KEY_STR, p.VALUE_STR FROM CZ_UI_PROPERTIES p WHERE p.UI_DEF_ID = :ui_def_id AND NVL(p.DELETED_FLAG,'N') = 'N'
• Effective-dated reporting adds EFF_FROM and EFF_TO predicates, for example SYSDATE BETWEEN p.EFF_FROM AND NVL(p.EFF_TO, SYSDATE + 1).
• Migration or comparison extracts commonly filter by LAST_UPDATE_DATE to isolate rows changed since a baseline load.

Because the table is small and key-oriented, it is also frequently queried during debugging of Configurator UI behavior, when a property intended to influence presentation does not appear to be taking effect. In those cases the CHECKOUT_USER and audit columns help determine whether an unpublished or checked-out change is responsible.

Related Objects

The documented relationship set for this object is deliberately narrow. The single declared foreign key is:

• CZ_UI_DEFS — referenced through CZ_UI_PROPERTIES.UI_DEF_ID. This is the parent UI definition table and the primary join path.

Beyond the declared FK, CZ_UI_PROPERTIES participates in the broader Configurator object family, which includes UI definition and property-definition structures, configuration model and component tables, and related CZ metadata used by the Configurator runtime and its concurrent programs. Because the documented metadata lists only CZ_UI_DEFS as a referenced table, joins to those other CZ objects should be validated against the specific environment before being relied upon in a report or interface.