Search Results bsc_oaf_analysys_opt_comb_v




Overview

The BSC_OAF_ANALYSYS_OPT_COMB_V view is an Oracle E-Business Suite database object owned by the APPS schema within the Balanced Scorecard (BSC) product family. It is a valid, deployed view in both EBS 12.1.1 and 12.2.2 environments. The view exposes the combination of analysis options, KPI measures, and dataset metadata that underpin the Oracle Analytics Foundation (OAF) layers of Balanced Scorecard. Its principal function is to publish a flattened, report-ready representation of each KPI's analysis option series alongside associated display, default, and sharing attributes.

Rather than storing data independently, the view assembles its result set dynamically by joining base KPI tables and invoking packaged PL/SQL functions from BSC_OAF_VIEWS_PVT, which resolve human-readable series names, dataset source identifiers, display flags, and default flags. This design is characteristic of BSC configuration views: the physical data lives in the underlying KPI tables, while the view layers business logic on top so that reports and integrations can consume analytics metadata without joining multiple tables or duplicating function calls.

Underlying Base Objects

The documented view text defines three base tables, all in the APPS schema:

The view also depends on the PL/SQL package BSC_OAF_VIEWS_PVT, which provides the functions GET_AOPTS_SERIES_NAMES, GET_DATASET_SOURCE, GET_AOPTS_DISPLAY_FLAG, and GET_AOPTS_DEFAULT_FLAG. The ETRM metadata records no separately documented base objects beyond these, so the object's lineage is defined entirely by its view text.

Key Columns

  • INDICATOR — the KPI identifier that anchors the record.
  • ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2 — the analysis option dimensions for the series.
  • SERIES_ID and KPI_MEASURE_ID — the measure series identity and its parent KPI measure.
  • FULL_NAME — resolved by GET_AOPTS_SERIES_NAMES; the concatenated display name of the option series.
  • SOURCE — resolved by GET_DATASET_SOURCE from DATASET_ID; identifies the data source feeding the series.
  • DISPLAY_FLAG — resolved by GET_AOPTS_DISPLAY_FLAG; indicates whether the series is displayed.
  • MASTER_FLAG — aliased from BSC_KPIS_B.SHARE_FLAG; this is the column a user searching for "master_flag" would encounter. It signals whether the KPI's analysis options are shared or treated as the master configuration.
  • DATASET_ID — the underlying dataset identifier.
  • DEFAULT_FLAG — resolved by GET_AOPTS_DEFAULT_FLAG; marks the default series for the option combination.
  • MEASURE_COLOR — appears in the documented column list and carries the measure's presentation color.
  • PROTOTYPE_FLAG — flags prototype KPI configurations.

Note that MASTER_FLAG is not a physical column of any base table; it is a derived alias of SHARE_FLAG, which is significant when tracing it in SQL or metadata tools.

Common Use Cases and Queries

Typical uses include auditing which KPI analysis option combinations are marked as master/shared, driving Balanced Scorecard dashboards, and diagnosing missing series names or datasets. A representative query follows:

  • SELECT indicator, series_id, full_name, source, display_flag, master_flag, default_flag FROM apps.bsc_oaf_analysys_opt_comb_v WHERE master_flag = 'Y'; — locates master-configured KPI series.
  • SELECT indicator, full_name, dataset_id FROM apps.bsc_oaf_analysys_opt_comb_v WHERE display_flag = 'Y' ORDER BY indicator; — reports active display series and their sources.
  • SELECT indicator, analysis_option0, analysis_option1, analysis_option2, default_flag FROM apps.bsc_oaf_analysys_opt_comb_v WHERE indicator = :kpi; — inspects the option matrix for a specific KPI.

Because the view calls PL/SQL functions per row, large unfiltered queries can be resource-intensive; filtering on INDICATOR or MASTER_FLAG is recommended in production environments. The object name itself contains the spelling "ANALYSYS," which must be preserved exactly in any SQL or dependency query against ALL_VIEWS or DBA_DEPENDENCIES.