Search Results pon_colors




Overview
Explore in AI Chat

Overview

PON_COLORS is a reference (lookup) table in the PON – Sourcing product module of Oracle E-Business Suite, owned by the PON schema. It stores the master list of colors and shapes that the Live Console uses when rendering supplier bid graphs. Its stated purpose is to ensure that each supplier's bid is uniquely identifiable on a graph, both by a distinct color and by an associated shape and image file. The table is not transactional; it is a presentation-layer configuration table whose contents drive chart rendering behavior rather than sourcing logic or award decisions.

The object was reported as VALID in the ETRM documentation. Its documented physical schema lists 11 columns, and its Data Vault classification is given heuristically as standalone. From a modeling perspective, this implies PON_COLORS behaves as a hub-style reference entity: it holds a durable, code-like business key (COLOR_ID) rather than being embedded as a satellite on a transactional parent. Because it has no foreign keys pointing outward, it should be treated as an independent reference hub that other objects point to.

Key Information Stored

The table is keyed by COLOR_ID, which is both the surrogate primary key (constraint PON_COLORS_PK) and, together with ZD_EDITION_NAME, the business-key candidate captured by unique index PON_COLORS_U1. The documented columns are:

  • COLOR_ID – the primary identifier for each color definition; the join column used by every dependent table.
  • COLOR_NAME – the user-facing or display name of the color, used in graph legends and setup screens.
  • COLOR_HEX_CODE – the hexadecimal RGB value used by the Live Console to render the actual color in the graph.
  • SHAPE – the marker shape associated with the color, used as a secondary visual differentiator between suppliers.
  • IMAGE_FILE_NAME – the file name of the image asset associated with the shape/color combination.
  • ZD_EDITION_NAME – the editioning column supporting EBS Online Patching (Edition-Based Redefinition), which is why the unique index and not the primary key carries this attribute.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – the standard Oracle EBS who-audit columns recording when and by whom each color row was created and last modified.

Common Use Cases and Queries

Because PON_COLORS is a small reference table, it is rarely queried in isolation. The most typical usage is joining it to dependent color-binding tables to resolve a color identifier into a displayed name, hex code, and shape. A representative query resolves all colors used by a system color set:

  • SELECT c.COLOR_ID, c.COLOR_NAME, c.COLOR_HEX_CODE, c.SHAPE FROM PON.PON_COLORS c WHERE c.ZD_EDITION_NAME = 'ORA$BASE';
  • Joining to dependent configuration: SELECT s.COLOR_ID, c.COLOR_NAME FROM BSC_SYS_COLORS_B s JOIN PON_COLORS c ON c.COLOR_ID = s.COLOR_ID;
  • Validating referential integrity before deleting or inactivating a color: count referencing rows in BSC_COLOR_RANGES, ICX_PAGE_COLORS, and BSC_SYS_COLORS_TL.

Common practical scenarios include reviewing or extending the set of available graph colors, verifying that a new color does not collide with an existing entry, and confirming that the hex code and shape mapping render correctly on the Live Console. Reporting on this table is mainly administrative or diagnostic, such as auditing color definitions or documenting which colors are assigned to which supplier graph ranges.

Related Objects

PON_COLORS is referenced by several dependent tables, each joining on COLOR_ID. These relationships define the practical scope of the table:

  • BSC_SYS_COLORS_B – the system color base table, referencing PON_COLORS.COLOR_ID; this is likely the primary consumer in the Balanced Scorecard / Live Console area.
  • BSC_SYS_COLORS_TL – the translated system color table, also referencing COLOR_ID for language-specific color labels.
  • BSC_COLOR_RANGES – defines color ranges, referencing COLOR_ID to bind a range to a specific color definition.
  • ICX_PAGE_COLORS – page/portal color assignment, referencing COLOR_ID for page-level color configuration.
  • ICX_PAGE_COLORS_TL – the translated counterpart of ICX_PAGE_COLORS, again referencing COLOR_ID.

No foreign keys originate from PON_COLORS itself, confirming its standalone reference-hub role. When working with any of the above tables, PON_COLORS should always be joined on COLOR_ID and filtered by the correct ZD_EDITION_NAME value for the active edition.