Search Results role_display_name




Overview
Explore in AI Chat

Overview

EGO_ROLE_DETAILS_V is a reporting view owned by the APPS schema within the EGO (Advanced Product Catalog) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes role information by joining Oracle Application Object Library (FND) translation tables that describe menu-based roles and the objects they are associated with. The view surfaces a normalized set of attributes — the role display name, role description, role identifier, and the associated object display name — where the "role" is represented internally as an FND menu (a responsibility-style menu structure).

Because the EGO product relies on role-based access and assignment constructs, this view provides a convenient, language-aware read interface for consumers that need to resolve a role to its display name and description without navigating the underlying FND schema directly. It is particularly relevant to reporting, data extraction, and integration layers that must map internal menu identifiers to user-facing role labels.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

  • FND_MENUS_TL — the translated menu (role) definitions, supplying the role display name, description, and menu identifier.
  • FND_OBJECTS_TL — the translated object definitions, supplying the object display name.
  • FND_MENU_ENTRIES — links menu entries to functions, used to constrain the result set to roles that actually contain function entries.
  • FND_FORM_FUNCTIONS — the form functions referenced by menu entries, used to associate a function with an object via OBJECT_ID.

The view text joins FND_MENUS_TL (aliased MENUS) and FND_OBJECTS_TL (aliased OBJECTS) with a correlated EXISTS subquery over FND_FORM_FUNCTIONS and FND_MENU_ENTRIES. Both translation tables are filtered by LANGUAGE = USERENV('LANG'), ensuring the view returns rows in the session's current language.

Key Columns

  • ROLE_DISPLAY_NAME — sourced from FND_MENUS_TL.USER_MENU_NAME; this is the user-facing role name and is the column most commonly searched (as with the term "role_display_name").
  • ROLE_DESCRIPTION — sourced from FND_MENUS_TL.DESCRIPTION; provides the textual description of the role.
  • ROLE_ID — sourced from FND_MENUS_TL.MENU_ID; the internal identifier for the role/menu.
  • OBJECT_DISPLAY_NAME — sourced from FND_OBJECTS_TL.DISPLAY_NAME; the display name of the object associated with the role's underlying function.

All four columns are exposed in the documented column list and retain the underlying table naming conventions.

Common Use Cases and Queries

Typical uses include resolving a stored ROLE_ID to its display name, searching for roles by name or description, and populating LOV or reporting outputs with human-readable role labels. A simple lookup by role display name follows:

  • SELECT ROLE_ID, ROLE_DISPLAY_NAME, ROLE_DESCRIPTION FROM APPS.EGO_ROLE_DETAILS_V WHERE ROLE_DISPLAY_NAME LIKE '%Catalog%';

A join-style retrieval by internal identifier:

  • SELECT ROLE_DISPLAY_NAME, ROLE_DESCRIPTION, OBJECT_DISPLAY_NAME FROM APPS.EGO_ROLE_DETAILS_V WHERE ROLE_ID = :p_role_id;

Because language filtering is applied internally via USERENV('LANG'), the view returns translated values automatically; no additional language predicate is required. Note that the correlated EXISTS clause restricts output to roles containing function entries tied to an object, so menu structures without matching entries will not appear.

This view is read-only and should be queried rather than modified. It is a valid dictionary-style object in both 12.1.1 and 12.2.2 and is safe to reference from custom reports, concurrent programs, and integration extracts.