Results for “icx_pages_u1”

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

Overview

ICX.ICX_PAGES is a core configuration table in the Oracle E-Business Suite ICX (Interaction Center / Self-Service) schema. It stores the definition of every page available within the Oracle Applications Framework (OAF) and legacy Self-Service personal home page (PHP) infrastructure. Each row describes a single page, its owning user, the responsibility under which the page is accessible, and the display ordering and refresh characteristics governing its presentation. The table sits at the heart of the personalized "Personal Home Page" experience delivered through the ICX layer, and it is the authoritative source that the runtime page-rendering engine consults when determining which pages a given PHP user may see and in what sequence.

From a Data Vault modeling perspective, the heuristic classification of ICX_PAGES is satellite-leaning. This is consistent with its role: it holds descriptive, attribute-rich context about pages that are anchored to an owning user and, transitively, to a responsibility. It is not a pure hub (its business identity is expressed through PAGE_CODE and PAGE_ID rather than a natural business key alone) and it is not a link resolving a many-to-many association, though it does carry an outbound foreign key to FND_USER. The 12.1.1 and 12.2.2 physical definitions of the object are documented as identical, with 15 columns, a single primary key, and three indexes, so no version-specific structural divergence is anticipated.

Key Information Stored

• PAGE_ID — Surrogate primary key, populated from the ICX_PAGES_S sequence. The unique index ICX_PAGES_U1 enforces uniqueness on this column.
• PAGE_CODE — The business-key candidate: a unique 30-character code identifying the page. Indexed by the non-unique ICX_PAGES_N2.
• USER_ID — The PHP user who owns the page; this is the outbound foreign key to FND_USER and is indexed by ICX_PAGES_N3.
• RESPONSIBILITY_ID — The responsibility under which the page may be accessed, tying the page to the security model.
• PAGE_NAME — Legacy display name used by Old BIS-style PHP pages.
• PAGE_DESCRIPTION — Free-text description (up to 240 characters) associated with the page.
• SEQUENCE_NUMBER — Governs the display ordering of pages for the user.
• PAGE_TYPE — Classification of the page; documented valid values are MAIN and USER.
• MAIN_REGION_ID — Identifies the first region rendered on the page.
• REFRESH_RATE — Interval controlling automatic page refresh.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide the audit trail required for all EBS transactional and configuration tables.

Common Use Cases and Queries

The predominant use of ICX_PAGES is diagnostic and administrative: identifying which pages a PHP user has configured, verifying display ordering, and auditing responsibility assignment. Because the table is small and driven by a unique sequence-generated key, direct SQL access is normally safe for read operations.

To list every page owned by a user, joined to the user name:

• SELECT p.page_id, p.page_code, p.page_name, p.page_type, p.sequence_number FROM icx.icx_pages p, fnd_user u WHERE p.user_id = u.user_id AND u.user_name = :user_name ORDER BY p.sequence_number;

To locate a page by its business key, exploiting the unique index ICX_PAGES_U1 and the page code index ICX_PAGES_N2:

• SELECT * FROM icx.icx_pages WHERE page_code = :page_code;

To audit responsibility coverage — which pages reference a given responsibility and how many are MAIN versus USER type — a grouping query is informative for security reviews and migration readiness checks. Reporting against ICX_PAGES is also common when validating personalized home page configurations ahead of an upgrade from 12.1.1 to 12.2.2, since the structural definition is unchanged and data can be compared directly.

Related Objects

• FND_USER — Referenced through ICX_PAGES.USER_ID. The parent of each page definition; join on USER_ID.
• ICX_PAGES (APPS synonym) — The APPS-owned synonym exposes the table to application code and is listed as a dependent of the base object.
• ICX_PAGES_S — The sequence supplying PAGE_ID values for new page rows.
• ICX_PAGES_U1 — The unique index on PAGE_ID that enforces row identity and supports primary-key lookups.
• ICX_PAGES_N2 and ICX_PAGES_N3 — Supporting non-unique indexes on PAGE_CODE and USER_ID respectively, underpinning the most frequent access paths.
• FND_RESPONSIBILITY — Related through RESPONSIBILITY_ID, the security boundary that determines who may reach the page.

The ETRM documentation notes that ICX_PAGES references no database object other than its foreign key to FND_USER, and that it is referenced by dependents in the APPS schema. This limited dependency footprint confirms its position as a leaf configuration table in the ICX page framework.