Search Results display_level

Overview

RG_LEVEL_OF_DETAIL_V is a view in the APPS schema within Oracle E-Business Suite, owned by the Application Report Generator (RG) product. It is documented in ETRM as "10SC ONLY," indicating that it is scoped to a specific localization or reporting context rather than being a general-purpose reporting object across all EBS implementations. Functionally, the view supplies report-authoring components — such as Oracle Reports or Oracle Applications report definitions — with a validated list of level-of-detail display values that can be selected when defining report parameters, group breaks, or summary hierarchy levels.

The object is recorded with status VALID in both Oracle EBS 12.1.1 and 12.2.2, and its structure is identical across the two releases; the underlying definition has not changed with the technology stack upgrade. For users searching on the term "display_level," this view is directly relevant because it exposes a column literally named DISPLAY_LEVEL, which is the lookup code that report definitions store or compare against when resolving a level-of-detail selection. The view therefore acts as a lightweight presentation layer over lookup data rather than containing report execution logic itself.

Underlying Base Objects

According to the documented ETRM metadata, RG_LEVEL_OF_DETAIL_V is defined over a single referenced base object: RG_LOOKUPS, which is itself a VIEW. The view text confirms this dependency:

SELECT LK.LOOKUP_CODE DISPLAY_LEVEL, LK.MEANING LEVEL_OF_DETAIL FROM RG_LOOKUPS LK WHERE LK.LOOKUP_TYPE = 'GL_DISPLAY_LEVEL'

The view filters RG_LOOKUPS to the single lookup type GL_DISPLAY_LEVEL, meaning any rows belonging to other RG lookup types (for example, report format or parameter type lookups) are excluded. Because RG_LOOKUPS is a view rather than a base table, the physical rows ultimately trace back to the Applications lookup tables maintained under the RG product. This design keeps the level-of-detail values centrally maintained through the standard lookup maintenance interface, while RG_LEVEL_OF_DETAIL_V exposes only the subset required for this reporting function.

Key Columns

• DISPLAY_LEVEL — Sourced from RG_LOOKUPS.LOOKUP_CODE. This is the stored code value that report definitions and SQL logic would use in comparisons, joins, or parameter validation against the GL_DISPLAY_LEVEL lookup type.
• LEVEL_OF_DETAIL — Sourced from RG_LOOKUPS.MEANING. This is the user-facing, translated description of the level of detail, suitable for displaying in a report parameter list of values or on a printed report header.

Only these two columns are projected. The view does not expose lookup type, description, enabled flags, or date ranges, which confirms its narrow purpose: mapping a display level code to its descriptive meaning for the GL_DISPLAY_LEVEL domain.

Common Use Cases and Queries

The primary use case is populating a level-of-detail selection list in a report or concurrent program parameter, then resolving the selected code back to descriptive text. The most straightforward query lists all available levels:

SELECT display_level, level_of_detail FROM apps.rg_level_of_detail_v ORDER BY display_level;

A common integration pattern joins the view back to report definition data to translate stored codes into readable output:

SELECT r.report_name, v.level_of_detail FROM apps.rg_level_of_detail_v v, apps.rg_report_definitions r WHERE r.display_level = v.display_level;

Administrators troubleshooting a missing or incorrect level-of-detail option can query the view to confirm which lookup codes are currently active for GL_DISPLAY_LEVEL, since the view reflects exactly the rows present in RG_LOOKUPS. Adding a new level of detail therefore requires maintaining the underlying lookup, not altering the view.