Search Results cz_ui_images




Overview
Explore in AI Chat

Overview

CZ_UI_IMAGES is a Configurator (CZ) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores image and icon definitions used during configuration model authoring and at runtime. The Configurator is the engine behind Oracle's model-based configuration: users define models, templates, features, and options in a modeling environment, and end users subsequently drive those models through runtime selection screens. CZ_UI_IMAGES supports both phases by associating an image file with a specific UI definition, a usage context, and, where applicable, an entity. Icons surfaced through this table decorate modeler screens, option lists, and runtime picker interfaces, giving users visual cues rather than text-only choices.

The table resides in the CZ schema and is owned by the Configurator product. Its heuristic Data Vault classification is standalone, meaning no foreign-key relationships were mined into surrounding tables. As a modeling suggestion, this object is best treated as a reference or lookup satellite keyed by its own composite unique index rather than as a hub or link in a Data Vault model; it holds descriptive payload about image assignments and is not itself a transactional join point.

Key Information Stored

The table contains thirteen documented columns. The most consequential are described below.

  • UI_DEF_ID — Identifier of the UI definition to which the image belongs. This is the leading column of the primary key and ties each image row to a specific Configurator interface definition.
  • IMAGE_USAGE_CODE — Encodes the context in which the image is applied (for example, a specific modeling or runtime presentation slot). It is the second primary-key column.
  • ENTITY_CODE — Identifies the entity the image describes. It is the third primary-key column.
  • ZD_EDITION_NAME — Editioning column introduced by the 12.2 online patching architecture; it distinguishes rows across editions of the same logical record and appears in the unique index rather than the primary key proper.
  • IMAGE_FILE — Stores the image or icon file reference used at modeling and runtime.
  • MASTER_TEMPLATE_FLAG — Indicates whether the image entry belongs to a master template, governing inheritance behavior.
  • DELETED_FLAG — Soft-delete indicator, allowing rows to be logically removed while preserving referential history.
  • SEEDED_FLAG — Marks Oracle-seeded rows versus customer-created rows, a standard EBS convention for upgrade-safe reference data.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and last modified each row, when, and under which login session.

The documented primary key is CZ_UI_IMAGES_PK on (UI_DEF_ID, IMAGE_USAGE_CODE, ENTITY_CODE). The unique index additionally includes ZD_EDITION_NAME, making (UI_DEF_ID, IMAGE_USAGE_CODE, ENTITY_CODE, ZD_EDITION_NAME) the true business-key candidate. Because the table is standalone, no foreign-key columns were mined; the identifier columns function as logical references rather than enforced constraints.

Common Use Cases and Queries

Typical usage centers on auditing which images are attached to a given UI definition, troubleshooting missing icons at runtime, and migrating configurations between environments.

  • List all image assignments for a UI definition: SELECT ui_def_id, image_usage_code, entity_code, image_file FROM cz.cz_ui_images WHERE ui_def_id = :id AND NVL(deleted_flag,'N') = 'N';
  • Separate seeded reference images from customer-defined ones: SELECT seeded_flag, COUNT(*) FROM cz.cz_ui_images GROUP BY seeded_flag;
  • Report image inventory for a specific entity and usage context: SELECT image_file, master_template_flag FROM cz.cz_ui_images WHERE entity_code = :entity AND image_usage_code = :usage;
  • Reconcile recent maintenance activity via audit columns: SELECT ui_def_id, last_updated_by, last_update_date FROM cz.cz_ui_images WHERE last_update_date > SYSDATE - 30;

In 12.2 environments, queries intended to return a single logical row should constrain ZD_EDITION_NAME so that only the current edition's record is retrieved.

Related Objects

Although CZ_UI_IMAGES is classified as standalone, it participates logically with the broader Configurator data model through its identifier columns.

  • CZ_UI_DEFINITIONS — Parent definition table referenced by UI_DEF_ID; supplies the UI context for each image row.
  • CZ_UI_NODES — Node-level UI metadata that consumes images assigned for modeling presentation.
  • CZ_ENTITIES — Entity master corresponding to ENTITY_CODE, linking images to modeled entities.
  • CZ_UI_TEMPLATES — Template definitions governed by MASTER_TEMPLATE_FLAG inheritance behavior.
  • CZ_CONFIG_HEADERS and CZ_CONFIG_DETAILS — Runtime configuration records whose selection screens render the stored icons.
  • CZ_MODEL_DEFINITIONS — Model metadata whose modeling screens draw on image assignments.

All joins should be performed on the logical identifier columns (UI_DEF_ID, ENTITY_CODE), since the metadata documents no enforced foreign keys. The Configurator APIs underlying the CZ schema also read this table when rendering UI definitions in both modeler and runtime modes.