Results for “bisfv_target_levels”

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

Overview

BISFV_TARGET_LEVELS is an Oracle EBS Applications (APPS) view owned by the APPS schema and delivered as part of the BIS (Business Intelligence System / Applications BIS) product family. It exposes translated target-level definitions used by the Balanced Scorecard and target-tracking components of the EBS intelligence layer. In Oracle EBS 12.1.1 and 12.2.2, this view is the primary reporting and integration interface for target level configuration, resolving foreign keys held on the base BIS_TARGET_LEVELS table into human-readable short names and translated (MLS) names and descriptions.

The view is a denormalized read-only construct. It joins the base target-level table to its translation table and to a series of dimension, time, and organizational level tables, returning both the numeric level IDs and their corresponding short names and translated display names. Because it presents resolved business labels alongside raw IDs, it is frequently used in concurrent programs, OAF/Forms LOV queries, and downstream BI publisher reports where users need to select a target level by name rather than by internal identifier.

Underlying Base Objects

The documented view text references the following objects:

• BIS_TARGET_LEVELS — the driving base table holding the target level records, workflow mappings, and role/function defaults.
• BIS_TARGET_LEVELS_TL — the translation table supplying NAME and DESCRIPTION by language.
• BIS_INDICATORS and BIS_INDICATORS_TL — the indicator to which each target level is attached.
• BIS_LEVELS_ORG / BIS_LEVELS_ORG_TL, BIS_LEVELS_TIME / BIS_LEVELS_TIME_TL — organizational and time dimension levels.
• BIS_LEVELS_DIM1 through BIS_LEVELS_DIM7 (with corresponding _TL tables) — the seven configurable analytical dimensions.

Note that the ETRM metadata lists no referenced base objects explicitly; the join relationships above are derived from the documented view text. Because the view is defined in the APPS schema, privileges are typically granted through the standard APPS synonym/GRANT pattern.

Key Columns

• TARGET_LEVEL_ID — the primary identifier of the target level record; this is the value most commonly searched, referenced in the user query as the equivalent of "level_id."
• SHORT_NAME, NAME, DESCRIPTION — the code, translated label, and translated description.
• INDICATOR_ID with indicator SHORT_NAME and NAME — links the level to its parent indicator.
• ORG_LEVEL_ID, TIME_LEVEL_ID, DIMENSION1_LEVEL_ID … DIMENSION7_LEVEL_ID — the resolved level identifiers for each analytical axis, each accompanied by a SHORT_NAME and NAME.
• WF_ITEM_TYPE, WF_PROCESS and the resolved full activity name from BIS_UTILITIES_PUB.RESOLVE_FULL_ACTIVITY_NAME.
• DEFAULT_ROLE_ID, DEFAULT_ROLE with resolved role name.
• DEFAULT_COMPUTING_FUNCTION_ID and REPORT_FUNCTION_ID with resolved function names.
• UNIT_OF_MEASURE — the measure unit for the target.

Common Use Cases and Queries

Typical usage includes resolving a level_id to its display label, driving LOVs and DFF value sets, and building target-versus-actual dashboards.

• Look up a target level by ID: SELECT target_level_id, short_name, name FROM bis_target_levels WHERE target_level_id = :p_id;
• List levels for an indicator: SELECT target_level_id, name FROM bisfv_target_levels WHERE indicator_id = :ind_id ORDER BY name;
• JOIN to fact tables in BI Publisher data models on TARGET_LEVEL_ID.
• Extract configured roles and computing functions for security reviews.

All queries should be run against the APPS schema or through an APPS synonym.