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
- ROW_ID — The standard EBS row identifier (typically the concatenation of the primary key parts), used by the framework for row-level operations.
- LEVEL_ID — The primary key of the level; the link between BIS_LEVELS and BIS_LEVELS_TL.
- SHORT_NAME — The internal short identifier for the level, referenced by other BIS configuration objects.
- DIMENSION_ID — The dimension to which the level belongs, tying the level into the BIS dimensional hierarchy.
- NAME / DESCRIPTION — The language-specific display text drawn from BIS_LEVELS_TL; these are the columns most end users see.
- LEVEL_VALUES_VIEW_NAME, WHERE_CLAUSE, VIEW_OBJECT_NAME — Metadata that defines the database view or filtering used to resolve the valid values of the level.
- SOURCE, COMPARISON_LABEL_CODE, ATTRIBUTE_CODE, APPLICATION_ID, DEFAULT_SEARCH, LONG_LOV, MASTER_LEVEL, ENABLED, DEFAULT_VALUES_API, DRILL_TO_FORM_FUNCTION, HIDE_IN_DESIGN — Behavior and configuration flags governing search, LOV presentation, master/detail relationships, drill-down navigation, and design-time visibility.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns inherited from BIS_LEVELS.
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.
-
View: BIS_LEVELS_VL 12.1.1
APPS.BIS_LEVELS_VL·↳ BIS_LEVELS·↳ BIS_LEVELS_TL·Explore BIS module →
-
View: BIS_LEVELS_VL 12.2.2
APPS.BIS_LEVELS_VL·↳ BIS_LEVELS·↳ BIS_LEVELS_TL·Explore BIS module →
-
VIEW: APPS.BIS_LEVELS_VL 12.2.2
-
VIEW: APPS.BIS_LEVELS_VL 12.1.1
-
APPS.BIS_DIMENSION_LEVELS_RPTS_V·↳ BIS_LEVELS_VL·Explore BIS module →
-
View: BIS_DIMENSIONS_RPTS_V 12.1.1
APPS.BIS_DIMENSIONS_RPTS_V·↳ BIS_DIMENSIONS_VL·↳ BIS_LEVELS_VL·Explore BIS module →
-
APPS.BIS_FLEX_SEG_MAPPINGS_V·↳ BIS_DIMENSIONS_VL·↳ BIS_FLEX_SEG_MAPPING_LINES·↳ BIS_LEVELS_VL·Explore BIS module →
-
View: BSC_BIS_DIM_LEVELS_V 12.1.1
View of the BIS/BSC dimension levels for IBUILDER
APPS.BSC_BIS_DIM_LEVELS_V·↳ BIS_LEVELS_VL·↳ BSC_SYS_DIM_LEVELS_B·Explore BSC module →
-
View: BSC_BIS_DIM_LEVELS_V 12.1.1
APPS.BSC_BIS_DIM_LEVELS_V·↳ BIS_LEVELS_VL·↳ BSC_SYS_DIM_LEVELS_B·Explore FND module →
-
View: BSC_BIS_DIM_OBJS_VL 12.1.1
APPS.BSC_BIS_DIM_OBJS_VL·↳ BIS_LEVELS_VL·↳ BSC_SYS_DIM_LEVELS_VL·Explore BIS module →
-
APPS.BIS_FLEX_SEG_MAPPING_LINES_V·↳ BIS_DIMENSIONS_VL·↳ BIS_FLEX_SEG_MAPPING_LINES·↳ BIS_LEVELS_VL·Explore BIS module →
-
View: BIS_FLEX_MAPPINGS_V 12.1.1
APPS.BIS_FLEX_MAPPINGS_V·↳ BIS_DIMENSIONS_VL·↳ BIS_FLEX_FIELDS_V·↳ BIS_FLEX_SEG_MAPPING_LINES·Explore BIS module →
-
View: BIS_FLEX_MAPPINGS_V 12.2.2
APPS.BIS_FLEX_MAPPINGS_V·↳ BIS_DIMENSIONS_VL·↳ BIS_FLEX_FIELDS_V·↳ BIS_FLEX_SEG_MAPPING_LINES·Explore BIS module →
-
12.2.2 DBA Data 12.2.2
-
View: BIS_DIMENSIONS_RPTS_V 12.2.2
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
SYNONYM: APPS.BIS_LEVELS 12.2.2
-
SYNONYM: APPS.BIS_LEVELS_TL 12.2.2
-
View: BSC_BIS_DIM_LEVELS_V 12.2.2
Not implemented in this database·Explore FND module →
-
View: BSC_BIS_DIM_OBJS_VL 12.2.2
Not implemented in this database·Explore BIS module →
-
Not implemented in this database·Explore BIS module →
-
SYNONYM: APPS.BIS_LEVELS_TL 12.1.1
-
View: BSC_BIS_DIM_LEVELS_V 12.2.2
View of the BIS/BSC dimension levels for IBUILDER
Not implemented in this database·Explore BSC module →