Search Results ego_data_level_vl




Overview
Explore in AI Chat

Overview

EGO_DATA_LEVEL_VL is a validated, multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the EGO — Advanced Product Catalog product family. According to the ETRM documentation, the view "gives the complete information of the data level metadata." In ETRM terminology, a data level defines the granularity at which attribute groups and their associated attributes are captured, defaulted, validated, and made subject to view or edit privileges. Data levels form the backbone of the extensibility framework that lets implementers attach descriptive or operational attributes to catalog entities without modifying base tables.

Because the object is a VL view, it externalizes the current session's language setting: it joins the base table to its translation table and filters on USERENV('LANG'), so consumers automatically receive the user-facing name of the data level in the session language while structural metadata remains language-independent. This makes the view a suitable reporting and integration surface for both English and localized deployments.

Underlying Base Objects

The documented base objects referenced by EGO_DATA_LEVEL_VL are two synonyms: EGO_DATA_LEVEL_B and EGO_DATA_LEVEL_TL. Consistent with the standard Oracle EBS "_B/_TL" pattern, EGO_DATA_LEVEL_B holds language-independent columns — identifiers, application context, primary-key column mappings, and feature flags — while EGO_DATA_LEVEL_TL holds the translated, user-facing name. The view text confirms the join predicate B.DATA_LEVEL_ID = TL.DATA_LEVEL_ID, combined with the session-language filter. As a synonym-based view, it exposes no data of its own and is read-only; all maintenance occurs through the underlying tables and the EGO setup/administrative UI that manages data level definitions.

Key Columns

  • DATA_LEVEL_ID — Primary identifier of the data level; the join key across both base tables.
  • APPLICATION_ID — The application that owns the data level, aligning it to the EBS application registry.
  • ATTR_GROUP_TYPE — Classifies the attribute group type associated with the data level.
  • DATA_LEVEL_NAME — Internal, language-independent name of the data level.
  • USER_DATA_LEVEL_NAME — Translated display name sourced from EGO_DATA_LEVEL_TL for the session language.
  • PK1_COLUMN_NAME through PK5_COLUMN_NAME — The key columns that identify a record at this data level, supporting up to five part key segments.
  • PK1_COLUMN_TYPE through PK5_COLUMN_TYPE — The corresponding data types for each key column, used for validation and binding.
  • ENABLE_DEFAULTING — Indicates whether defaulting rules may populate attributes at this level.
  • ENABLE_VIEW_PRIV / ENABLE_EDIT_PRIV — Control whether view and edit privileges apply to the data level.
  • ENABLE_PRE_EVENT / ENABLE_POST_EVENT — Signal whether pre-event and post-event hooks are active for the level.

Common Use Cases and Queries

Typical consumers include data-level administration reports, attribute-group configuration screens, and integration extracts that need to understand the PK structure of a level before reading or writing attribute data. The view is commonly queried to look up the display name for a known ID, or to enumerate the levels that support defaulting or privilege enforcement.

  • Retrieve a localized name: SELECT USER_DATA_LEVEL_NAME FROM APPS.EGO_DATA_LEVEL_VL WHERE DATA_LEVEL_ID = :p_id;
  • List levels with defaulting enabled: SELECT DATA_LEVEL_ID, USER_DATA_LEVEL_NAME, APPLICATION_ID FROM APPS.EGO_DATA_LEVEL_VL WHERE ENABLE_DEFAULTING = 'Y';
  • Inspect PK mappings: SELECT DATA_LEVEL_NAME, PK1_COLUMN_NAME, PK2_COLUMN_NAME, PK1_COLUMN_TYPE FROM APPS.EGO_DATA_LEVEL_VL ORDER BY APPLICATION_ID, DATA_LEVEL_NAME;
  • Identify levels enforcing privileges: filter on ENABLE_VIEW_PRIV = 'Y' or ENABLE_EDIT_PRIV = 'Y'.

Because the view is synonym-based and read-only, standard SELECT privileges on the APPS objects are sufficient; no DML should be directed at the view itself.