Search Results bsc_db_dataset_dim_sets_v




Overview
Explore in AI Chat

Overview

The view BSC_DB_DATASET_DIM_SETS_V belongs to the Balanced Scorecard (BSC) module of Oracle E-Business Suite. In ETRM documentation this module is explicitly flagged as Obsolete, and the object itself is recorded with the note "Not implemented in this database." Within the context of Oracle EBS 12.1.1 and 12.2.2, this view was designed to expose the relationship between KPI analysis measures (identified by indicator and analysis-option combinations) and the dimension sets that qualify those measures for dataset-driven reporting.

The view resolves dimension-set assignments for a given indicator/series context. It joins a "basic" dimension-set source against the KPI analysis measures VL view, allowing reporting and integration layers to determine which dimension set applies to a particular measure and dataset. The presence of the SERIES_ID column is significant for users searching on that term: it is the attribute that links a row to a specific series definition used by the Balanced Scorecard engine.

Because the module is obsolete, the view should be treated as historical metadata rather than an active integration point in a current 12.2.2 instance. It remains relevant for upgrade impact analysis, custom code remediation, and understanding legacy BSC customizations inherited from earlier releases.

Underlying Base Objects

The documented view text defines the object entirely over two BSC views rather than physical base tables:

  • BSC_DB_BASIC_DIM_SETS_V BASIC — supplies the indicator, analysis-option (A0, A1, A2), and dimension-set identifiers used on the right-hand side of the outer join.
  • BSC_KPI_ANALYSIS_MEASURES_VL DATA — supplies the indicator, analysis options, series, dataset, default value, and KPI measure identifiers on the driving side of the query.

The join is an outer join (Oracle (+) syntax), applied on four correlated columns: INDICATOR, ANALYSIS_OPTION0, ANALYSIS_OPTION1, and ANALYSIS_OPTION2. Because the (+) operator sits on the BASIC side in every predicate, BSC_KPI_ANALYSIS_MEASURES_VL is the preserved (driving) table. Consequently, every analysis measure is returned, and DIM_SET_ID is substituted with 0 via NVL when no matching dimension set exists. The ETRM metadata records no separately documented physical base objects, consistent with the "Not implemented in this database" note.

Key Columns

  • INDICATOR — the KPI indicator that anchors the row; also the principal join key to the dimension-set source.
  • SERIES_ID — the series identifier associated with the analysis measure. This is the column most directly relevant to searches on "series_id," linking the view to Balanced Scorecard series definitions.
  • DIM_SET_ID — the resolved dimension-set identifier. It is returned as 0 when no basic dimension set matches the indicator and analysis options, enabling callers to distinguish "unassigned" from genuinely populated values.
  • DATASET_ID — identifies the dataset to which the measure belongs, supporting dataset-scoped dimension resolution.
  • DEFAULT_VALUE — the default value carried from the analysis measure definition.
  • KPI_MEASURE_ID — the unique measure identifier, useful for drill-through to measure-level detail.
  • A0, A1, A2 — aliases for ANALYSIS_OPTION0 through ANALYSIS_OPTION2, the three positional analysis options that form the composite key with INDICATOR.

Common Use Cases and Queries

Typical usage centres on resolving, per indicator and series, which dimension set applies to a KPI measure. A representative query filtering on the searched attribute is:

  • SELECT indicator, series_id, dim_set_id, dataset_id, kpi_measure_id FROM bsc_db_dataset_dim_sets_v WHERE series_id = :p_series_id;
  • SELECT indicator, series_id, dim_set_id FROM bsc_db_dataset_dim_sets_v WHERE dim_set_id = 0; — identifies measures with no assigned dimension set.
  • SELECT dataset_id, COUNT(*) FROM bsc_db_dataset_dim_sets_v GROUP BY dataset_id; — summarises measure coverage per dataset.

Because the module is obsolete and the object is not implemented, these queries are primarily valuable for remediation scripts, historical data extracts, and confirming that a custom report referencing this view can be safely retired in a 12.2.2 environment.