Search Results icx_pages




Overview
Explore in AI Chat

Overview

ICX_PAGES is a transactional configuration table owned by the ICX schema, the product schema associated with Oracle iProcurement and the broader Oracle Internet Commerce/self-service framework. The table stores page-level definitions for personal home pages (PHP) belonging to individual application users. Each record describes a single page element or page container that a user has configured within the self-service user interface, capturing presentation metadata such as the page name, description, page type, main region assignment, and refresh behavior. In Oracle EBS 12.1.1 and 12.2.2, this object functions as the persistence layer behind personalized portal-style layouts surfaced through iProcurement and related self-service responsibilities.

From a dimensional modeling perspective, the ETRM metadata classifies ICX_PAGES as satellite-leaning. This heuristic derives from its foreign key structure: the table references FND_USER through ICX_PAGES.USER_ID while carrying descriptive and behavioral attributes rather than serving as a pure intersection between two independent entities. A satellite classification suggests the table is best modeled as a dependent attribute set keyed to a parent user hub, with the page identity carried by its own primary key.

Key Information Stored

The table contains fifteen documented columns. The most significant are:

  • PAGE_ID — Surrogate primary key, enforced by ICX_PAGES_PK1. Also exposed through the unique index ICX_PAGES_U1, making it the dominant business-key candidate in the documented schema.
  • PAGE_CODE — Functional code identifying the page definition, used by application logic to resolve the correct page.
  • USER_ID — Foreign key to FND_USER, tying each page to its owning application user.
  • PAGE_NAME and PAGE_DESCRIPTION — Display attributes presented in the user interface.
  • RESPONSIBILITY_ID — Links the page to a specific responsibility, scoping visibility and access.
  • SEQUENCE_NUMBER — Controls ordering of pages or page elements during rendering.
  • PAGE_TYPE — Classifies the page, distinguishing layout or functional variants.
  • MAIN_REGION_ID — Identifies the primary region that anchors the page layout.
  • REFRESH_RATE — Governs how frequently the page content is refreshed.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns maintained by the framework.

Common Use Cases and Queries

Typical usage centers on personalization diagnostics, page inventory reporting, and cleanup of stale user-defined pages. A common pattern retrieves all pages for a named user:

  • SELECT p.page_id, p.page_name, p.page_type, p.sequence_number FROM icx.icx_pages p, applsys.fnd_user u WHERE p.user_id = u.user_id AND u.user_name = :user_name ORDER BY p.sequence_number;
  • Joining to FND_RESPONSIBILITY on RESPONSIBILITY_ID to determine which pages belong to which responsibility menu context.
  • Auditing refresh behavior by grouping on REFRESH_RATE to identify aggressively refreshing pages that may affect performance.
  • Extracting page inventories for migration or comparison between environments using PAGE_CODE as the stable identifier.

Related Objects

  • FND_USER — Referenced via ICX_PAGES.USER_ID; the principal parent in the satellite relationship.
  • FND_RESPONSIBILITY — Implied by RESPONSIBILITY_ID, scoping page availability.
  • ICX_PAGES_PK1 — Primary key constraint on PAGE_ID.
  • ICX_PAGES_U1 — Unique index on PAGE_ID, the documented business-key candidate.
  • Associated ICX region and menu tables referenced by MAIN_REGION_ID and PAGE_TYPE definitions.

ICX_PAGES is therefore a compact but structurally important object for understanding how per-user page personalization is persisted in Oracle iProcurement.