Search Results image_file




Overview
Explore in AI Chat

Overview

APPS.CZ_UI_PATHED_IMAGES_V is a reporting and integration view within the Oracle E-Business Suite application schema. It exposes image metadata maintained by the user interface definition framework, which governs the rendering of images within configurable UI pages, templates, and master templates. The view is not a physical table; it is a stored query that selects from the underlying image repository and, critically, derives a fully qualified image path at runtime. This derivation is the defining characteristic of the view, as reflected in its name "PATHED_IMAGES" — the view returns both the raw stored value and a resolved path suitable for direct use by a browser or downstream presentation tier.

Because the view filters out logically deleted rows and applies no other restriction, it presents the current, active image registry as understood by the application. It is typically consumed by reporting extracts, data-migration scripts, and integration routines that need to enumerate the images associated with a given UI definition, template, or entity.

Underlying Base Objects

The view is defined over a single base object: the synonym CZ_UI_IMAGES, which resolves to the underlying image definition table owned by the application. All columns returned by the view map one-to-one to columns in CZ_UI_IMAGES, with the exception of the computed FULL_IMAGE_PATH column, which is synthesized by the view definition. The view itself is owned by APPS, and the synonym exposed to the EBS schema is APPS.CZ_UI_PATHED_IMAGES_V.

The WHERE clause restricts the result set to rows where DELETED_FLAG = '0'. Rows marked as deleted in the base table remain physically present but are excluded here, so the view always reflects the currently effective image registry. No joins to other tables are performed; the sole transformation is the path-derivation expression on IMAGE_FILE.

Key Columns

  • UI_DEF_ID — Identifier of the user interface definition to which the image belongs. This binds an image to a specific configurable UI layout or page.
  • MASTER_TEMPLATE_FLAG — Indicates whether the image is associated with a master template rather than an ordinary definition.
  • IMAGE_USAGE_CODE — Classifies how the image is used within the UI framework (for example, a functional role such as icon, banner, or background).
  • ENTITY_CODE — Identifies the business entity or module context for the image, supporting multi-entity deployments and filtering.
  • IMAGE_FILE — The raw image file reference as stored. This is the value most directly associated with user searches on "image_file".
  • FULL_IMAGE_PATH — A computed column produced by concatenating a path prefix with IMAGE_FILE. If IMAGE_FILE does not already begin with a forward slash or a URL scheme (such as "://"), the literal prefix '/OA_MEDIA/' is prepended; otherwise the stored value is used unchanged. This column is the principal reason to query the view rather than the base table.
  • SEEDED_FLAG — Distinguishes Oracle-seeded image definitions from customer-created ones, which is important when deciding whether a row may be safely modified or removed during upgrades.
  • DELETED_FLAG — Logical deletion indicator; always '0' in rows returned by this view.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who-columns for change tracking.

Common Use Cases and Queries

The primary use case is resolving a stored image reference into a usable path. The following query returns active images with their resolved paths for a given UI definition:

  • SELECT UI_DEF_ID, IMAGE_FILE, FULL_IMAGE_PATH FROM APPS.CZ_UI_PATHED_IMAGES_V WHERE UI_DEF_ID = :p_def_id;

To search for an image by its stored file name — the "image_file" lookup pattern — a query such as the following is typical:

  • SELECT ENTITY_CODE, IMAGE_USAGE_CODE, IMAGE_FILE, FULL_IMAGE_PATH FROM APPS.CZ_UI_PATHED_IMAGES_V WHERE IMAGE_FILE LIKE '%logo%';

Because the view hides deleted rows, it is also well suited to audit and migration extracts that must capture the complete set of active, seeded images:

  • SELECT SEEDED_FLAG, COUNT(*) FROM APPS.CZ_UI_PATHED_IMAGES_V GROUP BY SEEDED_FLAG;

In integration scenarios, FULL_IMAGE_PATH should be consumed directly in HTML, XML, or JSON payloads so that the consumer does not need to reimplement the '/OA_MEDIA/' prefix logic. Care should be taken to treat the view as read-only; updates to image metadata must be directed at the base table through the supported application APIs rather than the view.