Search Results dl_vl

Overview

APPS.EGO_PAGES_V is a reporting and integration view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It belongs to the EGO (Enterprise Governance/Product Information Management) schema family, which underpins Oracle Product Hub, Product Data Management, and related attribute and page administration functionality. The view exposes a denormalized, user-facing projection of the flexfield-backed "pages" used by the EGO framework, joining base tables to their translation and data-level definitions so that consumers can retrieve display-ready metadata in a single query.

Crucially, the view resolves codes into user-meaningful descriptions. The most notable example is the DATA_LEVEL_DISP_NAME column, which presents the translatable, user-visible name of the data level (for example, "Item," "Organization," or "Master Organization") rather than the internal code stored in the base table. The view also resolves the DATA_LEVEL code to its internal name as DATA_LEVEL_INT_NAME. This dual exposure of internal code and display name makes the view particularly relevant for reporting where the searched term "data_level_disp_name" is intended to surface readable data-level context.

Underlying Base Objects

According to the documented view text and the ETRM metadata, EGO_PAGES_V is defined over four referenced base objects:

• EGO_PAGES_B (SYNONYM) — the base (non-translated) pages table, supplying PAGE_ID, OBJECT_ID, CLASSIFICATION_CODE, DATA_LEVEL, INTERNAL_NAME, and SEQUENCE.
• EGO_PAGES_TL (SYNONYM) — the translation table, supplying DISPLAY_NAME and DESCRIPTION for the current session language.
• EGO_DATA_LEVEL_VL (VIEW) — the data-level value list, joined through a DISTINCT subquery to map DATA_LEVEL_NAME to USER_DATA_LEVEL_NAME.
• FND_OBJECTS (SYNONYM) — the Oracle Application Object Library registry, supplying OBJ_NAME via OBJECT_ID.

The joins are: B.PAGE_ID = TL.PAGE_ID (base to translation), B.OBJECT_ID = O.OBJECT_ID (page to registered object), and DL_VL.DATA_LEVEL_NAME = B.DATA_LEVEL (page data level to the value-list display name). The translation join is restricted by TL.LANGUAGE = USERENV('LANG'), so only the current session's language rows are returned.

Key Columns

• PAGE_ID — primary identifier of the page.
• OBJECT_ID — the FND_OBJECTS identifier the page is associated with.
• OBJECT_NAME — object name resolved from FND_OBJECTS.
• CLASSIFICATION_CODE — classification of the page.
• DATA_LEVEL_INT_NAME — the internal data-level code (aliased from B.DATA_LEVEL).
• DATA_LEVEL_DISP_NAME — the translatable, user-facing data-level name resolved from EGO_DATA_LEVEL_VL.
• INTERNAL_NAME — the internal name of the page.
• DISPLAY_NAME and DESCRIPTION — translated display text from EGO_PAGES_TL.
• SEQUENCE — ordering value for the page.

Common Use Cases and Queries

The view is typically used for inventory/reporting of configured pages and for joining to EGO data-level metadata in custom reports, concurrent programs, and integrations. A typical query returns readable data levels for a given object:

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

To focus on data-level display labels, the DATA_LEVEL_DISP_NAME column is selected directly. Because the view honors USERENV('LANG'), callers automatically receive translated values for the current EBS language session, requiring no additional join. Consumers should note that the DATA_LEVEL resolved is confined to values present in EGO_DATA_LEVEL_VL, so pages referencing unmapped data levels will not appear in the result set.