Search Results element_signature_id




Overview
Explore in AI Chat

Overview

The CZ_UIELEMENT_IMAGES_V view is a Configurator (CZ) product database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, user-facing projection of UI element image assignments that belong to Oracle Configurator user interface definitions. Specifically, the view exposes image metadata (file name, storage path, usage code, alternate text, and a related element signature) for images that are associated with configurator UI elements but are not tied to any particular UI definition instance (UI_DEF_ID = 0).

The view carries status VALID and is documented in the ETRM repository as a standard, queryable reporting object. Its role in Oracle EBS reporting and integration is to provide a stable, denormalized read interface over the more granular CZ_UI_PATHED_IMAGES_V view, joining it to CZ_SIGNATURES so that each image can be presented alongside the human-readable name and description of the signature (element type) it represents. Developers building Configurator-related reports, extensions, or extract interfaces commonly query this view instead of the underlying base objects because the join and the filtering predicates are already applied.

Underlying Base Objects

The documented base objects referenced by CZ_UIELEMENT_IMAGES_V in 12.2.2 are:

  • CZ_SIGNATURES (referenced through a SYNONYM) — supplies the signature rows that identify element types in Oracle Configurator.
  • CZ_UI_PATHED_IMAGES_V (VIEW) — supplies the physical image record, including file name, full path, usage code, entity code, UI definition identifier, and deletion flag.

The view text joins these two sources on USIG.SIGNATURE_ID = IMG.ENTITY_CODE. In effect, the entity code carried on the image record is repurposed as the element signature identifier. The view further restricts output with the predicates IMG.UI_DEF_ID = 0, IMG.DELETED_FLAG = '0', and IMG.IMAGE_USAGE_CODE = 40. These predicates constrain the result set to non-deleted, globally scoped images whose usage code designates them for element-level display. Because the view is defined by join rather than by a materialized copy, any change to CZ_SIGNATURES or CZ_UI_PATHED_IMAGES_V is reflected immediately at query time.

Key Columns

  • IMAGE_USAGE_CODE — numeric usage classification for the image. Within this view the value is restricted to 40, indicating the element-level usage category.
  • ELEMENT_SIGNATURE_ID — the signature identifier of the configurator element the image is associated with. This is the aliased ENTITY_CODE from the image source and is the column surfaced when users search on "element_signature_id."
  • IMAGE_FILE — the file name of the image.
  • ELEMENT_TYPE_NAME — the NAME of the associated signature, describing the element type.
  • ALT_TEXT — the signature DESCRIPTION, used as alternate text for accessibility or display purposes.
  • UI_DEF_ID — the UI definition identifier. Because the view filters to 0, this column always returns 0 in this view and identifies the record as not bound to a specific UI definition.
  • FULL_IMAGE_PATH — the resolved storage path of the image file, suitable for constructing a display or download reference.

Common Use Cases and Queries

The view is typically used to enumerate the images available for configurator element types, to validate that an image file and path exist for a given element signature, and to render element images with appropriate alternate text. A representative query looks up all images for a specific element signature:

  • SELECT element_signature_id, element_type_name, image_file, alt_text, full_image_path FROM cz_uielement_images_v WHERE element_signature_id = :signature_id;
  • SELECT image_file, full_image_path FROM cz_uielement_images_v ORDER BY element_type_name; — produce a catalog of all element-level images.
  • SELECT v.element_signature_id, s.signature_id FROM cz_uielement_images_v v, cz_signatures s WHERE v.element_signature_id = s.signature_id; — reconcile images against signatures.

Because the view filters on DELETED_FLAG = '0', results exclude logically removed images, making it safe for end-user reporting without additional cleanup predicates.