Results for “bsc_db_color_kpi_defaults_v”

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

Overview

BSC_DB_COLOR_KPI_DEFAULTS_V is a database view owned by the APPS schema in Oracle E-Business Suite, belonging to the BSC (Balanced Scorecard) product family. It is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view resolves the relationships between KPI indicators, the series they belong to, the dimension sets applied to them, and the datasets that result, but only for those combinations that are flagged as default. Its stated purpose is to return the series id, dimension set, and dataset together with the defaults indicator.

Functionally, the view acts as a reconciliation layer between the color and default configuration views used by the Balanced Scorecard engine. Rather than requiring callers to join the color defaults view and the dataset dimension sets view manually, BSC_DB_COLOR_KPI_DEFAULTS_V performs that join internally and filters down to the rows marked with DEFAULT_VALUE = 1, returning the effective default mapping for each indicator. This makes it the single point of reference when a reporting or integration component needs to know which dataset a KPI resolves to under its default dimension selection.

Underlying Base Objects

The view is defined over two intermediate views rather than base tables. The first is BSC_DB_DATASET_DIM_SETS_V, aliased M, which supplies INDICATOR, SERIES_ID, DIM_SET_ID, DATASET_ID, the A0/A1/A2 attribute values, and DEFAULT_VALUE. The second is BSC_DB_COLOR_AO_DEFAULTS_V, aliased D, which supplies the INDICATOR plus the A0_DEFAULT, A1_DEFAULT, and A2_DEFAULT values. The join is performed on indicator identity across both sources, and then on each attribute slot: M.A0 = D.A0_DEFAULT, M.A1 = D.A1_DEFAULT, and M.A2 = D.A2_DEFAULT. The final predicate M.DEFAULT_VALUE = 1 restricts the output to default-flagged rows.

No base tables are documented directly for this object in the ETRM metadata, and the referenced base objects list is empty. The A0, A1, and A2 columns represent the Balanced Scorecard attribute or dimension slots used to position a KPI within its scorecard structure; the defaults view supplies the authoritative slot values, while the dataset dimension sets view supplies the candidate combinations. The intersection of the two, filtered by the default flag, defines the effective default configuration. Any structural change to the underlying private views will cascade into this object, so dependent customizations should be validated after patching.

Key Columns

• INDICATOR — Identifier of the KPI indicator. It is the principal join key between the two source views and the primary lookup column for consumers.
• SERIES_ID — Identifier of the series to which the indicator belongs, carried from BSC_DB_DATASET_DIM_SETS_V.
• DIM_SET_ID — Identifier of the dimension set associated with the default mapping for the indicator.
• DATASET_ID — Identifier of the dataset resolved for the indicator under its default attribute values.

Note that the A0/A1/A2 attribute values and the DEFAULT_VALUE flag participate in the join and filter but are not exposed in the select list; they are implementation details of the resolution logic.

Common Use Cases and Queries

Typical usage is diagnostic or integration-oriented: confirming the default dataset that a KPI resolves to, populating custom extracts, or validating configuration after migration.

• Retrieve the default mapping for a specific indicator:
  SELECT indicator, series_id, dim_set_id, dataset_id FROM apps.bsc_db_color_kpi_defaults_v WHERE indicator = :p_indicator;
• List all default mappings for reporting reconciliation:
  SELECT indicator, series_id, dim_set_id, dataset_id FROM apps.bsc_db_color_kpi_defaults_v ORDER BY indicator;
• Join to indicator metadata to enrich output:
  SELECT v.indicator, v.series_id, v.dataset_id FROM apps.bsc_db_color_kpi_defaults_v v WHERE v.series_id = :p_series_id;

Because the view is APPS-owned and read-only by nature, it should be queried with the APPS schema or an account holding appropriate grants. Custom code should avoid depending on the internal attribute or default flag columns, as these are not part of the published column list.