Search Results refresh_rate

Overview

ICX_PAGES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the ICX product family, which underpins Oracle iProcurement and the broader Oracle iStore/Internet Computing Architecture framework. The view presents page definitions used by the framework to render self-service pages, regions, and portal-style layouts. As a "_VL" (view language) object, it is a language-aware view: it joins the base transactional table to its translation table and filters the translation rows by the session's current language, so that PAGE_NAME and PAGE_DESCRIPTION are returned in the user's selected language rather than in the base language only.

In practice, ICX_PAGES_VL is queried when administrators, implementers, or diagnostic reports need to inspect which pages are defined in the system, the order in which they appear, and how frequently each page is refreshed. Because it is a view rather than a table, it carries no storage of its own and simply projects columns from its underlying objects, making it safe for read-only reporting and integration queries.

Underlying Base Objects

According to the ETRM metadata, the view is defined over two referenced base objects, both accessed through APPS synonyms:

• ICX_PAGES — the base (non-translated) table holding the page definition rows, aliased as IP in the view text.
• ICX_PAGES_TL — the translation table holding language-specific page names and descriptions, aliased as IPT.

The two objects are joined on PAGE_ID. A filter predicate constrains ICX_PAGES_TL to the language returned by USERENV('LANG'), the environment function that reports the current session language. This join-and-filter pattern is standard for _VL views across EBS and ensures a single translated row per page for the active language.

Key Columns

The view exposes the following documented columns:

• PAGE_ID — primary key identifying the page; the join key between ICX_PAGES and ICX_PAGES_TL.
• PAGE_CODE — the internal code used by the framework to reference the page programmatically.
• REFRESH_RATE — the interval at which the page is refreshed; the column most relevant to the user's search term "refresh_rate". It governs how frequently the page content is regenerated or reloaded by the framework.
• SEQUENCE_NUMBER — determines the display or processing order of the page relative to others.
• PAGE_TYPE — classifies the page (for example standard versus personalized), influencing how the framework renders it.
• MAIN_REGION_ID — identifies the primary region associated with the page, linking pages to their region definitions.
• USER_ID and RESPONSIBILITY_ID — indicate the user or responsibility to which a page definition is scoped; null values typically denote pages available to all users or responsibilities.
• PAGE_NAME and PAGE_DESCRIPTION — the translated display name and description drawn from ICX_PAGES_TL and filtered by session language.

Common Use Cases and Queries

Typical use cases include auditing page refresh settings, verifying translated page names, and troubleshooting page sequencing or scope. A simple listing of all pages follows:

• SELECT page_id, page_code, refresh_rate, sequence_number FROM apps.icx_pages_vl ORDER BY sequence_number;
• SELECT page_code, refresh_rate FROM apps.icx_pages_vl WHERE refresh_rate IS NOT NULL; — isolates pages with a defined refresh interval.
• SELECT page_id, page_name, page_description FROM apps.icx_pages_vl WHERE user_id = :p_user_id; — reviews pages scoped to a specific user.
• SELECT page_code, responsibility_id FROM apps.icx_pages_vl WHERE responsibility_id = :p_resp_id; — identifies pages bound to a responsibility.

For integration and reporting, the view can be joined to region or function tables on PAGE_ID or MAIN_REGION_ID. Because translation is filtered by USERENV('LANG'), reports run under a different language session automatically return the corresponding translated names, without additional joins.