Results for “bis_levels_vl”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_LEVELS_VL is a bilingual (translated) view owned by the APPS schema in Oracle E-Business Suite. In the Applications BIS product family, a "level" represents a defined analytical dimension slice used by Business Intelligence System (BIS) reporting, drill-down, and dimensional modeling components. The view exposes level configuration metadata alongside its language-specific descriptive text, allowing reports and forms to present level definitions in the session's active language. The _VL suffix follows the standard Oracle EBS convention for a view that joins a base (non-translated) table to its translation table and filters the translation row by USERENV('LANG'), thus returning a single, correctly localized record per entity. In 12.1.1 and 12.2.2 this object is documented as VALID and serves primarily as a read-only reporting and integration interface rather than a transactional table.

Underlying Base Objects

Per the documented ETRM metadata, BIS_LEVELS_VL is defined over two objects:

  • BIS_LEVELS (referenced as a SYNONYM) — the base table holding language-independent level attributes such as identifiers, the dimension to which the level belongs, view names, and functional behavior flags.
  • BIS_LEVELS_TL (referenced as a SYNONYM) — the translation table holding the language-specific NAME and DESCRIPTION, keyed by LEVEL_ID and LANGUAGE.

The join is performed on LEV.LEVEL_ID = LEV_TL.LEVEL_ID with the additional predicate LEV_TL.LANGUAGE = USERENV('LANG'). This ensures exactly one translated row per level, matching the current runtime language of the session, which is the defining behavior of an EBS "_VL" view.

Key Columns

Common Use Cases and Queries

This view is commonly queried to enumerate available levels for a given dimension, to build LOVs, or during BIS report and drill-down configuration. A typical lookup returns enabled levels with their localized names:

SELECT level_id, short_name, name
FROM   bis_levels_vl
WHERE  dimension_id = :p_dimension_id
AND    enabled = 'Y';

Administrators validating configuration may also inspect the view and value-source metadata:

SELECT lev.short_name, lev.name, lev.level_values_view_name, lev.where_clause
FROM   bis_levels_vl lev
WHERE  lev.dimension_id = :p_dimension_id;

Because the view is governed by USERENV('LANG'), NAME and DESCRIPTION reflect the session language automatically, eliminating the need for application-layer translation joins. All access is read-only; changes to levels must be made against the underlying BIS_LEVELS and BIS_LEVELS_TL tables.