Search Results bsc_kpi_analysis_measures_vl




Overview
Explore in AI Chat

Overview

The BSC_KPI_ANALYSIS_MEASURES_VL view is a seeded, APPS-owned database object within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It is a "VL" (view with language) construct, a standard EBS pattern in which a base ("_B") table holding language-independent attributes is joined to a translation ("_TL") table holding language-dependent text. The view presents the KPI analysis measures that drive Balanced Scorecard charts and analytics, exposing both the measure configuration and its translated display name and help text for the session's current language. Reported Status is VALID, and the object is available in both Oracle EBS 12.1.1 and 12.2.2. Because it is owned by APPS and is a view, it serves as a read-only reporting and integration surface rather than a storage object.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the preserved view text identifies the two source objects explicitly:

The two are joined on the composite key of INDICATOR, ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2, and SERIES_ID, with the additional filter TL.LANGUAGE = USERENV('LANG'). This language predicate restricts each row to the translation matching the caller's EBS session language, so consumers of the view see exactly one NAME/HELP pair per measure series. The view therefore behaves as a convenience layer, collapsing a five-column composite join and the language restriction into a single queryable object.

Key Columns

  • INDICATOR — identifies the KPI or scorecard indicator to which the measure belongs; part of the composite key.
  • ANALYSIS_OPTION0 / 1 / 2 — the analysis dimension/option identifiers positioning the measure within a specific KPI analysis; together with INDICATOR and SERIES_ID they form the join key.
  • SERIES_ID — the identifier of the data series being plotted for the measure.
  • NAME — the translated display label for the series (from the TL table).
  • HELP — the translated help or descriptive text for the series (from the TL table).
  • DATASET_ID — links the measure to the dataset from which values are sourced.
  • AXIS — indicates the chart axis (for example primary versus secondary) on which the series is rendered.
  • SERIES_TYPE — the rendering behavior/type of the series.
  • STACK_SERIES_ID — identifies a related series for stacking purposes.
  • BM_FLAG and BUDGET_FLAG — flags indicating whether the series represents a benchmark or a budget measure.
  • DEFAULT_VALUE — a default value applied when no measure data is available.
  • SERIES_COLOR and BM_COLOR — color attributes used to render the series and its benchmark.
  • PROTOTYPE_FLAG — marks the measure as a prototype or template definition.
  • KPI_MEASURE_ID — the unique identifier for the KPI measure record.

Common Use Cases and Queries

The view is typically consumed to enumerate configured analysis measures for reporting, dashboard construction, or data extraction. Because the language is resolved automatically, callers need not re-implement the TL join.

List all measures for a given indicator:

SELECT indicator, series_id, name, series_type, bm_flag, budget_flag
FROM   apps.bsc_kpi_analysis_measures_vl
WHERE  indicator = :indicator
ORDER  BY series_id;

Identify benchmark and budget series for charting:

SELECT kpi_measure_id, name, bm_flag, budget_flag, series_color, bm_color
FROM   apps.bsc_kpi_analysis_measures_vl
WHERE  bm_flag = 'Y' OR budget_flag = 'Y';

Because it is a view over seeded BSC tables, it should be queried rather than modified; changes to measure configuration are performed through the Balanced Scorecard application, not through DML against this object.