Search Results ego_pages_v




Overview
Explore in AI Chat

Overview

EGO_PAGES_V is a reporting and integration view owned by the APPS schema within the EGO – Advanced Product Catalog product module. Its status is VALID in both Oracle E-Business Suite 12.1.1 and 12.2.2. The view exposes the set of user-defined pages configured against objects registered in the catalog framework, combining each page's technical identity, its owning object, its classification and data-level assignments, and its language-specific display attributes into a single denormalized result set.

The view abstracts the base/translation table split that characterizes the EGO schema's multilingual design. Consumers query one object without needing to join the base table (EGO_PAGES_B), the translation table (EGO_PAGES_TL), the data-level lookup, and FND_OBJECTS manually. It therefore functions as the canonical read interface for page definitions used by concurrent programs, custom reports, and integration extracts that need to enumerate pages or resolve a page's display name in the session language.

Because the view resolves display text through USERENV('LANG'), its output is session-dependent. Any consumer requiring deterministic, language-independent output must account for this behavior or join the underlying translation table directly.

Underlying Base Objects

The documented base objects referenced by EGO_PAGES_V are EGO_PAGES_B and EGO_PAGES_TL (both exposed as synonyms in the APPS schema), EGO_DATA_LEVEL_VL, and FND_OBJECTS. Structurally, EGO_PAGES_B supplies the primary page record: page identifier, owning object, classification code, data level, internal name, and sequence. EGO_PAGES_TL supplies language-specific display name and description, joined on PAGE_ID and filtered to the session language.

FND_OBJECTS is joined on OBJECT_ID to resolve the object's internal name (OBJ_NAME) into the OBJECT_NAME column. The inline distinct query over EGO_DATA_LEVEL_VL maps the stored data level name to its user-facing name, yielding DATA_LEVEL_DISP_NAME. The view therefore has a many-to-one relationship with FND_OBJECTS and a one-to-one relationship with the translation row for the active language.

Key Columns

  • PAGE_ID – Primary identifier of the user-defined page, sourced from EGO_PAGES_B.
  • OBJECT_ID – Identifier of the catalog object to which the page belongs.
  • OBJECT_NAME – Internal name of that object, resolved through FND_OBJECTS.
  • CLASSIFICATION_CODE – Classification assigned to the page, used to group or categorize page definitions.
  • DATA_LEVEL_INT_NAME – Internal data-level name as stored on the page record.
  • DATA_LEVEL_DISP_NAME – User-facing data-level name derived from EGO_DATA_LEVEL_VL.
  • INTERNAL_NAME – Developer-facing page name.
  • DISPLAY_NAME – Translated page name for the session language.
  • DESCRIPTION – Translated page description.
  • SEQUENCE – Ordering value controlling page presentation.

Common Use Cases and Queries

Typical scenarios include auditing which pages exist for a given object, validating that translations are populated for all required languages, and feeding page metadata into custom catalog or integration processes.

List all pages for a specific object:

  • SELECT page_id, internal_name, display_name, sequence FROM apps.ego_pages_v WHERE object_name = :object_name ORDER BY sequence;

Locate the display name for a known page identifier:

  • SELECT display_name, description FROM apps.ego_pages_v WHERE page_id = :page_id;

Audit pages by classification and data level:

  • SELECT object_name, classification_code, data_level_disp_name, COUNT(*) FROM apps.ego_pages_v GROUP BY object_name, classification_code, data_level_disp_name;

Detect pages lacking a translation in the current session language:

  • SELECT b.page_id FROM apps.ego_pages_b b WHERE NOT EXISTS (SELECT 1 FROM apps.ego_pages_v v WHERE v.page_id = b.page_id);