Search Results bis_target_levels_vl




Overview
Explore in AI Chat

Overview

BIS_TARGET_LEVELS_VL is a translatable (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the BIS (Applications BIS / Business Intelligence System) product. The view exposes target level definitions used by Oracle's balanced scorecard and performance management framework, where a "target level" represents a specific analytical slice of a business indicator: a defined organizational level, a time level, and up to seven additional dimension levels against which targets are set and reported. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and carries no separate business description beyond the implementation metadata, so its role is best understood through its structure.

Because the object name carries the "_VL" suffix, it is a language-sensitive view that joins a base table to its translation table and filters on the session language. It therefore presents target level data to the application in the language of the current user session, making it suitable for concurrent program output, OBIEE/XML Publisher data sources, forms, and custom integrations that require language-specific names and descriptions.

Underlying Base Objects

The view is defined over two BIS tables:

  • BIS_TARGET_LEVELS (aliased TGLV) — the base transaction entity table holding the target level identifier, indicator association, level assignments, workflow process, default role, system flag, and standard WHO audit columns.
  • BIS_TARGET_LEVELS_TL (aliased TGLV_TL) — the translation table holding the NAME and DESCRIPTION columns in multiple installed languages.

The join condition is TGLV.TARGET_LEVEL_ID = TGLV_TL.TARGET_LEVEL_ID AND TGLV_TL.LANGUAGE = USERENV('LANG'). USERENV('LANG') returns the language code of the current database session, so a rowset for a given target level resolves to exactly one translation row matching the session language. Practically, this means a query against BIS_TARGET_LEVELS_VL returning an unexpectedly empty or partial result may indicate missing translation rows for the session language rather than missing base data; querying BIS_TARGET_LEVELS directly bypasses that dependency. The view text uses the legacy TGLV/TGLV_TL aliases inherited from the original view definition.

Key Columns

  • ROW_ID — the ROWID of the BIS_TARGET_LEVELS row; used by the framework for optimistic locking and updates through the view.
  • TARGET_LEVEL_ID — primary identifier of the target level, and the join key to the translation table.
  • INDICATOR_ID — foreign key to the indicator (KPI) to which the target level belongs.
  • SHORT_NAME — internal short identifier for the target level.
  • ORG_LEVEL_ID, TIME_LEVEL_ID — the organizational hierarchy level and time hierarchy level that define the slice being targeted.
  • DIMENSION1_LEVEL_ID … DIMENSION7_LEVEL_ID — up to seven optional dimension level references extending the slice beyond organization and time.
  • WF_PROCESS, DEFAULT_ROLE_ID, DEFAULT_ROLE — the workflow process and default responsibility/role associated with the target level.
  • SYSTEM_FLAG — distinguishes seeded/system-owned target levels from user-defined ones.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit (WHO) columns.
  • NAME, DESCRIPTION — language-specific translatable attributes contributed by BIS_TARGET_LEVELS_TL.

Common Use Cases and Queries

Typical uses include identifying the target levels defined against a given indicator, reporting target level setups with their translated names, and joining to related BIS scorecard configuration objects. A minimal query returning the fully described target levels is:

SELECT target_level_id, indicator_id, short_name, name, description, org_level_id, time_level_id, system_flag FROM apps.bis_target_levels_vl WHERE indicator_id = :p_indicator_id;

To list all target levels with organization and time context, constrain by ORG_LEVEL_ID or TIME_LEVEL_ID, or filter SYSTEM_FLAG = 'Y' to isolate seeded definitions. Because NAME and DESCRIPTION are language dependent, reports intended for multiple locales should either run under the correct session language or join BIS_TARGET_LEVELS to BIS_TARGET_LEVELS_TL directly and supply the LANGUAGE predicate explicitly. When target levels appear with null NAME values, verify that translation rows exist in BIS_TARGET_LEVELS_TL for the session language before investigating the base table.