Results for “message_name”

8 results




Overview
Explore in AI Chat

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

Overview

In Oracle E-Business Suite releases 12.1.1 and 12.2.2, the ICX.POR_IMAGES table is the image registry underpinning Oracle iProcurement. As the Description field states simply, this object stores "Images" — the binary and/or referenced image assets that iProcurement renders inside the storefront, catalog, and checkout pages. The table is owned by the ICX schema (Oracle iProcurement / Internet Computing Components), carries a VALID status in the data dictionary, and contains four documented columns on the 12.2.2 physical schema. Its primary key is IMAGE_NAME, which the ETRM metadata identifies as the sole unique identifier for each row.

From a Data Vault modeling perspective, the mined relationship data classifies POR_IMAGES as a standalone object with no foreign-key dependencies to other tables. This heuristic suggests it can be modeled as a hub, where IMAGE_NAME serves as the business key that uniquely identifies each image entity. Because the metadata records no inbound or outbound FK structure, no link or satellite relationships are implied; the table behaves as an independent lookup/reference store rather than a transactional or associative entity. The registry is shared across iProcurement's internal components, so changes to its contents directly affect what end users see in the shopping interface.

Key Information Stored

The documented physical schema of ICX.POR_IMAGES comprises four columns. IMAGE_NAME is the surrogate and primary key — a unique string identifying each registered image; because it is the only documented unique index, it is also the sole business-key candidate. MESSAGE_NAME ties the image to a message or label reference used by the iProcurement UI layer, providing the semantic link between the stored asset and the interface element that displays it. ALT_TEXT_KEY stores the reference to the alternate-text value (for accessibility and tooltips) associated with the image. IMAGE_TYPE captures the classification or format of the image asset, allowing the application to distinguish, for example, icon classes or rendering modes. Not every column is enumerated here — only the four documented in the ETRM metadata — but these are the fields that carry the business meaning of the table. The compact four-column design reflects the table's purpose as a lightweight registry rather than a content repository.

Common Use Cases and Queries

The most common scenario is resolving which image asset is presented for a given UI element. A typical query joins iProcurement message metadata to the image registry:

  • Retrieve an image by key: SELECT IMAGE_NAME, MESSAGE_NAME, ALT_TEXT_KEY, IMAGE_TYPE FROM ICX.POR_IMAGES WHERE IMAGE_NAME = :p_image_name;
  • List images by type for a UI review: SELECT IMAGE_NAME, MESSAGE_NAME FROM ICX.POR_IMAGES WHERE IMAGE_TYPE = :p_type ORDER BY IMAGE_NAME;
  • Audit alternative text coverage: SELECT IMAGE_NAME, ALT_TEXT_KEY FROM ICX.POR_IMAGES WHERE ALT_TEXT_KEY IS NULL;
  • Reporting on which messages reference images, supporting accessibility and localization reviews.

These patterns are useful during implementations, upgrades, and branding exercises when administrators validate that every storefront image has an associated message and accessible alternate text.

Related Objects

Because the ETRM metadata records POR_IMAGES as a standalone object with no documented foreign keys, its relationships are semantic rather than enforced. The most significant dependent or referencing objects are:

  • ICX.POR_IMAGES' own primary key IMAGE_NAME — the join column used by any application code that resolves an image.
  • MESSAGE_NAME links logically to iProcurement/ICX message-definition tables such as FND_MESSAGES or the POR message repository, which supply the displayable label.
  • ALT_TEXT_KEY resolves to message/translation sources such as FND_MESSAGES_TL for localized alternate text.
  • ICX.POR_STORE_HEADERS and other POR catalog tables that reference images by IMAGE_NAME for storefront and catalog branding.
  • iProcurement JSP/UI components and the POR catalog APIs that read POR_IMAGES at runtime to render pages.
  • Related ICX image and media tables that follow the same registry pattern for other asset classes.

Administrators should treat POR_IMAGES as reference data: it is safe to query, and updates should follow Oracle's supported configuration paths rather than direct DML.