Search Results icx_colors




Overview
Explore in AI Chat

Overview

ICX_COLORS is a reference (lookup) table owned by the ICX schema, the database account associated with Oracle iProcurement and the broader Oracle Internet Commerce / self-service framework. The ETRM metadata describes it simply as a "Color standards table," which identifies its role precisely: it stores the canonical set of named color values used by iProcurement and related self-service shopping and UI components to render consistent visual attributes across pages, regions, and administrative configuration screens.

Because the table is small, static, and maintained as a system-owned lookup rather than transactional data, its ETRM Data Vault classification heuristic is standalone. In Data Vault modeling terms, this is best treated as a reference satellite (or, where the color name is reused as a natural key, as a small hub with an attached descriptive satellite). No foreign-key relationships into or out of ICX_COLORS are documented, so it functions as an isolated reference dimension rather than a link table.

Key Information Stored

The documented physical schema for 12.2.2 shows only three columns, reflecting the table's compact design:

  • NAME — the primary key column and the business identifier for each color standard. The primary key constraint is ICX_COLORS_PK, defined on NAME.
  • COLOR_VALUE — the actual color representation (typically an RGB, hex, or token value) associated with the named standard.
  • DESCRIPTION — a human-readable label or explanation of the color standard.

Since the primary key is a natural business key (NAME) rather than a system-generated surrogate, no separate sequence-derived ID column is documented. NAME therefore serves simultaneously as the unique business key and the join key for embedding applications. The absence of WHO columns, timestamps, or audit columns in the documented schema is consistent with a seeded, non-transactional reference object.

Common Use Cases and Queries

Typical usage involves joining ICX_COLORS to display or validate color attributes in iProcurement configuration, personalization, and diagnostics. Representative patterns include:

  • Listing all available color standards: SELECT name, color_value, description FROM icx.icx_colors ORDER BY name;
  • Resolving a specific value during diagnostics: SELECT color_value FROM icx.icx_colors WHERE name = :p_name;
  • Validating orphaned references in dependent tables by outer-joining ICX_COLORS to any column storing a color NAME, identifying rows where the color code no longer exists in the standards table.

Reporting use cases are limited to configuration audits, upgrade validation, and documentation of UI theming. Because the table contains no date-effective or transactional attributes, it is not a candidate for historical or trend reporting.

Related Objects

The ETRM relationship data classifies ICX_COLORS as standalone, with no documented foreign keys. Related objects are therefore conceptual rather than enforced-referential, and are drawn from the ICX product family that consumes color standards:

  • ICX_LOOKUPS / FND_LOOKUPS — general lookup framework; color codes may be surfaced as lookup values or validated against them.
  • ICX_STYLES / style or theme configuration tables — consume color standards for rendering.
  • PO_ATTRIBUTE_VALUES and related purchasing attribute tables — may reference descriptive color values in item and catalog configuration.
  • FND_FLEX_VALUES — where color is modeled as a value set, values can be cross-validated against ICX_COLORS.
  • ICX_CATALOG_* tables — iProcurement catalog and UI configuration objects that display color-coded content.

Because no FK constraints are documented, joins to these objects are application-level conventions rather than database-enforced relationships, and any integration should treat NAME as the dependable business join key.