Search Results bis_target_levels_v

Overview

BIS_TARGET_LEVELS_V is a reporting and integration view within the Oracle E-Business Suite Applications BIS (Business Intelligence System / Balanced Scorecard) module. It exposes the definition of target levels configured against performance indicators, resolving the dimensional and hierarchical context in which targets are set. A target level associates an indicator with a specific combination of organizational, time, and up to seven additional dimension hierarchies, thereby determining the granularity at which targets are measured, rolled up, and reported. In Oracle EBS 12.1.1 and 12.2.2, this view is primarily consumed by the Balanced Scorecard and Daily Business Intelligence reporting layers, workflow-driven target approval processes, and any custom integration that requires a denormalized, human-readable representation of target-level configuration. The view presents descriptive names for every level identifier so that downstream reports and integrations do not need to perform additional joins against the level hierarchy tables. Note that the ETRM metadata records this object as "Not implemented in this database," indicating that its presence depends on whether the BIS product is licensed and installed in a given environment.

Underlying Base Objects

The view is defined over the following documented base objects:

• BIS_TARGET_LEVELS_VL — the multi-language (translated) base table holding the target-level definitions, aliased as A. This is the driving table of the join.
• BIS_INDICATORS_VL — the translated indicators table, aliased as B, joined on INDICATOR_ID to supply the indicator name.
• BIS_LEVELS — joined eight times (aliases LEVORG, LEVTIME, LEV1 through LEV7) to resolve each stored level identifier into its short name.

All joins to BIS_LEVELS are outer joins (Oracle (+) syntax), meaning a target level is still returned even when one or more dimension level identifiers are null. This preserves the dimensional flexibility of target definitions, where only a subset of the seven dimensions may be populated. The join to BIS_INDICATORS_VL is an inner join, so a target level must reference a valid indicator to appear in the result set.

Key Columns

• TARGET_LEVEL_ID — primary identifier for the target level record.
• INDICATOR_ID / INDICATOR_NAME — the indicator to which the target level applies.
• ORG_LEVEL_ID / ORG_LEVEL_NAME — the organizational hierarchy level at which the target is defined.
• TIME_LEVEL_ID / TIME_LEVEL_NAME — the time dimension level (for example, month, quarter, year) governing target measurement.
• DIMENSION1_LEVEL_ID … DIMENSION7_LEVEL_ID and their corresponding DIMENSIONn_LEVEL_NAME columns — optional additional dimension levels that further qualify the target.
• WF_PROCESS — the workflow process associated with the target level, used for approval or notification flows.
• DEFAULT_ROLE_ID / DEFAULT_ROLE — the role assigned by default for the target level.
• SYSTEM_FLAG — indicates whether the target level is seeded/system-defined.
• NAME / DESCRIPTION — the target level name and description text.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include building target-versus-actual comparisons, validating target configuration before scorecard deployment, and driving workflow-based approvals. The following query lists all target levels with their resolved indicator and dimensional context:

• SELECT target_level_id, indicator_name, short_name, org_level_name, time_level_name, dimension1_level_name, system_flag FROM bis_target_levels_v ORDER BY indicator_name, short_name;
• SELECT indicator_id, COUNT(*) FROM bis_target_levels_v GROUP BY indicator_id; — counts target levels per indicator.
• SELECT * FROM bis_target_levels_v WHERE system_flag = 'Y'; — isolates seeded, system-defined target levels.
• SELECT * FROM bis_target_levels_v WHERE wf_process IS NOT NULL; — identifies target levels participating in a workflow.

Because the view resolves level identifiers into short names, it is well suited for reporting tools and interfaces that must present target configuration without additional lookup joins. Applications should treat it as read-only; target-level maintenance is performed against the underlying BIS_TARGET_LEVELS base tables.