Search Results tglv_tl




Overview

APPS.BIS_TARGET_LEVELS_VL is a bilingual (language-specific) database view in Oracle E-Business Suite that presents target level definitions used by the Oracle Balanced Scorecard (BIS) module. The _VL suffix denotes a "view language" construct, a standard EBS pattern in which a base transactional table is joined to its translated (_TL) counterpart so that the descriptive columns (NAME, DESCRIPTION) are returned in the session's current language. The view enables report developers, concurrent programs, and integration components to retrieve target level metadata in a single query without manually joining the base and translation tables or resolving the language environment.

Target levels define the organizational, temporal, and dimensional granularity at which scorecard indicators are measured and targets are set. In this sense the view functions as the descriptive layer over the BIS target-level configuration, and it is the object that forms-based and OAF-based scorecard setup screens implicitly query when populating lists of values.

Underlying Base Objects

The view is defined over two objects, joined on the target level primary key:

  • BIS_TARGET_LEVELS (aliased TGLV) — the base table holding the target level definition, its surrogate key, level identifiers, workflow configuration, and auditing columns.
  • BIS_TARGET_LEVELS_TL (aliased TGLV_TL) — the translation table holding the language-specific NAME and DESCRIPTION.

The join condition is TGLV.TARGET_LEVEL_ID = TGLV_TL.TARGET_LEVEL_ID, combined with the language filter TGLV_TL.LANGUAGE = USERENV('LANG'). Because the language is resolved from the user session environment, the same row identifier returns text in the appropriate installed language. The view also projects TGLV.ROWID as ROW_ID, a convention used to give the translated view a stable, updatable row identifier. Under EBS standards, the corresponding _B (base) and _TL (translation) entities typically support the _VL join; the actual install base and the fully qualified owner are not enumerated in the supplied ETRM metadata.

Key Columns

Common Use Cases and Queries

Typical usages include validating target-level configuration, driving value sets for scorecard setup, and joining target levels to scorecard fact data for reporting. The session language is applied automatically, so no explicit language predicate is required.

  • Listing all target levels for an indicator: SELECT target_level_id, name, short_name FROM bis_target_levels_vl WHERE indicator_id = :p_indicator_id;
  • Retrieving translated text for a specific level: SELECT name, description FROM bis_target_levels_vl WHERE target_level_id = :p_id;
  • Identifying seeded versus user-defined levels: SELECT target_level_id, name FROM bis_target_levels_vl WHERE system_flag = 'Y';
  • Restricting to a management role: SELECT name FROM bis_target_levels_vl WHERE default_role = :p_role;

Because the view applies a USERENV('LANG') filter, queries must run in a session whose language corresponds to an installed translation; otherwise the descriptive columns return no rows even when a base record exists.