Search Results bsc_kpis_b

Overview

The BSC_KPIS_B table is the core base table for storing master definition data for Key Performance Indicators (KPIs) within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It serves as the central repository for the technical and administrative attributes that define a KPI, such as its calculation method, periodicity, and source relationships. As indicated by its product classification, the Balanced Scorecard module is marked as obsolete in the provided ETRM metadata for Oracle EBS releases 12.1.1 and 12.2.2. This status signifies that while the table and its associated data structures exist in the database, Oracle no longer actively develops the module, and its use in new implementations is strongly discouraged. The table's primary key is BSC_KPIS_B_PK on the INDICATOR column.

Key Information Stored

While the specific column list is not detailed in the provided excerpt, the table's description and foreign key relationships imply it holds the fundamental attributes for each KPI. The primary identifier is the INDICATOR column, which is the unique key. Based on standard KPI modeling and the foreign keys present, the table likely stores columns such as PERIODICITY_ID (linking to BSC_SYS_PERIODICITIES to define the measurement frequency), SOURCE_INDICATOR (for defining derived KPIs that source data from another indicator), and other attributes controlling the KPI's behavior, data type, status, and ownership. The table is designed to hold the non-translatable, code-based information, with translatable text (like the KPI name and description) stored in the related BSC_KPIS_TL (Translation) table.

Common Use Cases and Queries

Given the module's obsolete status, primary use cases involve supporting, maintaining, or migrating existing Balanced Scorecard implementations. Common activities include auditing KPI definitions, analyzing dependencies between KPIs, and generating data dictionaries for legacy scorecards. A fundamental query retrieves the list of all active KPIs with their core properties. For dependency analysis, one might query hierarchical relationships using the SOURCE_INDICATOR self-referential foreign key. Furthermore, identifying all KPIs associated with a specific analysis group or calculation rule involves joining to the respective child tables (e.g., BSC_KPI_ANALYSIS_GROUPS, BSC_KPI_CALCULATIONS).

• Basic KPI Listing: SELECT indicator, name, periodicity_id FROM bsc_kpis_b kpi, bsc_kpis_tl tl WHERE kpi.indicator = tl.indicator AND tl.language = USERENV('LANG');
• KPI Dependency Chain: SELECT CONNECT_BY_ROOT indicator AS root_kpi, indicator AS derived_kpi FROM bsc_kpis_b CONNECT BY PRIOR indicator = source_indicator;

Related Objects

The BSC_KPIS_B table is the central hub in a complex schema, with numerous child tables referencing its INDICATOR primary key. As per the metadata, key related objects include: BSC_KPIS_TL for translated names and descriptions; BSC_KPI_CALCULATIONS and BSC_KPI_PROPERTIES for detailed configuration; BSC_KPI_ANALYSIS_MEASURES_B and BSC_KPI_ANALYSIS_GROUPS for grouping and measurement logic; BSC_KPI_CAUSE_EFFECT_RELS for strategy map modeling; and BSC_TAB_INDICATORS for scorecard presentation. The self-referencing foreign key on SOURCE_INDICATOR creates a hierarchical relationship within the same table, allowing for derived KPIs. The extensive foreign key list underscores that BSC_KPIS_B is a foundational table for the obsolete module, and any data manipulation must carefully consider these dependencies.