Search Results cause_indicator

Overview

The BSC_KPI_CAUSE_EFFECT_RELS table is a core data structure within the Oracle E-Business Suite Balanced Scorecard (BSC) module, versions 12.1.1 and 12.2.2. It is designed to store and manage the cause-and-effect relationships between Key Performance Indicators (KPIs). This table formally models the strategic linkages and dependencies between different metrics, enabling the analysis of how performance in one area (the cause) influences performance in another (the effect). It is a foundational element for building strategic maps and performing driver-based analysis within the now-obsolete Balanced Scorecard application. The table's existence is critical for understanding the propagation of performance impacts across a business scorecard.

Key Information Stored

The table's structure is relatively simple, focusing on the relationship between two KPIs. The primary data elements are the identifiers for the related indicators, which together form the table's primary key. According to the provided metadata, the key columns are:

• CAUSE_INDICATOR: Stores the identifier (typically matching the INDICATOR column in BSC_KPIS_B) for the KPI that acts as the driver or causal factor in the relationship.
• EFFECT_INDICATOR: Stores the identifier for the KPI that is influenced or impacted by the cause indicator.

This design ensures that each cause-and-effect pairing is unique within the system. The table's integrity is enforced by a primary key constraint (BSC_KPI_CAUSE_EFFECT_RELS_PK) on these two columns and by foreign key constraints linking each column back to the base KPI definition table.

Common Use Cases and Queries

The primary use case for this table is to query the network of KPI relationships for analytical and reporting purposes. A common requirement is to retrieve all downstream effects of a particular KPI to assess the potential ripple effect of its performance. Conversely, one might query all upstream causes of a KPI to diagnose root factors affecting its results. Sample SQL patterns include finding all effects for a given cause:

SELECT EFFECT_INDICATOR FROM BSC_KPI_CAUSE_EFFECT_RELS WHERE CAUSE_INDICATOR = :p_cause_kpi;

Or, to generate a full relationship map for reporting:

SELECT cause.NAME cause_name, effect.NAME effect_name FROM BSC_KPI_CAUSE_EFFECT_RELS rel JOIN BSC_KPIS_B cause ON rel.CAUSE_INDICATOR = cause.INDICATOR JOIN BSC_KPIS_B effect ON rel.EFFECT_INDICATOR = effect.INDICATOR;

These relationships would be visually represented in strategic map components of the BSC application.

Related Objects

The BSC_KPI_CAUSE_EFFECT_RELS table has a direct and exclusive dependency on the base KPI definition table. As per the foreign key metadata:

• BSC_KPIS_B: This is the primary related object. Two foreign key constraints are defined, both referencing BSC_KPIS_B. One constraint links the CAUSE_INDICATOR column to the INDICATOR column in BSC_KPIS_B, and a separate constraint links the EFFECT_INDICATOR column to the same key in BSC_KPIS_B. This ensures that only valid, defined KPIs can participate in a cause-and-effect relationship.

It is important to note the metadata states this table is "Not implemented in this database," which may indicate it was part of a documented data model but not physically instantiated in some deployments, or that it is part of the obsolete module's legacy structure.