Search Results gl_display_level

Overview

APPS.RG_LEVEL_OF_DETAIL_V is a lightweight reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases. It exposes the set of valid "level of detail" values used by the Oracle General Ledger (GL) reporting and inquiry infrastructure. The view is owned by the APPS schema and serves as a denormalized, presentation-friendly projection of an internal lookup repository, shielding consuming code and report definitions from the physical structure of the lookup table.

The view is most commonly encountered in the context of GL account inquiry, drill-down, and financial reporting components where a numeric or coded display level must be translated into a user-readable meaning. In practice, the view returns one row per defined level of detail, pairing the internal lookup code (the display level) with its descriptive meaning. Because the object is a view rather than a table, it contains no data of its own and is always resolved at runtime against its single underlying base object.

Underlying Base Objects

Per the documented ETRM metadata for release 12.2.2, the view is defined over a single referenced base object: RG_LOOKUPS (itself exposed as an APPS view over the underlying lookup table). The view text is fixed and consists of a filtered, projected query against that lookup source:

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

The relationship to the base object is therefore one of dependency and filtering: the view inherits the entire lookup row population of RG_LOOKUPS but restricts it to those rows whose LOOKUP_TYPE is exactly GL_DISPLAY_LEVEL. No outer joins, unions, or additional tables participate in its definition. This narrow dependency means the view carries no independent storage, index, or maintenance overhead, and its results change only when the underlying lookup rows are maintained.

Key Columns

• DISPLAY_LEVEL — The lookup code drawn from RG_LOOKUPS.LOOKUP_CODE. This is the stored, coded value that identifies a particular level of detail and is the value typically held on transaction or reporting records that reference a display level.
• LEVEL_OF_DETAIL — The lookup meaning drawn from RG_LOOKUPS.MEANING. This is the descriptive text that conveys the human-readable significance of the display level, suitable for display on reports, inquiry screens, and integration payloads.

The view exposes only these two columns. The filtering predicate on LOOKUP_TYPE is applied internally and is not surfaced as a column, so every row returned is implicitly scoped to the GL_DISPLAY_LEVEL lookup type.

Common Use Cases and Queries

The primary use case is translation: converting stored display-level codes into meaningful labels for GL inquiry and financial reporting output. The view is also used to populate selection lists and validation sets where a valid level of detail must be offered or verified.

Retrieving the complete set of levels:

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

Resolving a single coded value to its meaning:

SELECT level_of_detail FROM apps.rg_level_of_detail_v WHERE display_level = :p_level;

Joining the view to a reporting or inquiry source to decorate records with descriptive text:

SELECT t.level_code, v.level_of_detail FROM my_reporting_source t, apps.rg_level_of_detail_v v WHERE t.level_code = v.display_level;

Because the view is a simple, low-cost projection over lookup data, it is safe to reference repeatedly within reporting queries. Callers should nevertheless observe standard APPS-schema access conventions and rely on the view rather than querying RG_LOOKUPS directly, ensuring that the GL_DISPLAY_LEVEL filter remains consistently applied across all consumers.