Search Results bsc_kpi_calculations_user




Overview
Explore in AI Chat

Overview

The BSC_KPI_CALCULATIONS_USER table is a core data object within the Oracle E-Business Suite Balanced Scorecard (BSC) module, versions 12.1.1 and 12.2.2. It functions as a junction or mapping table that establishes a relationship between Key Performance Indicator (KPI) calculations and system users. Its primary role is to store user-specific associations with calculation instances for performance indicators, enabling personalized tracking, access control, and responsibility assignment within the scorecard framework. This table is essential for implementing user-centric views and security on calculated KPI data.

Key Information Stored

The table's structure is defined by a composite primary key, which uniquely identifies each record by combining three critical foreign key columns. The data stored is primarily referential, linking entities rather than holding extensive transactional details.

  • CALCULATION_ID: References a specific calculation instance from the BSC_KPI_CALCULATIONS table.
  • USER_ID: References a user defined in the BSC_USERS table, linking the calculation to a specific individual.
  • INDICATOR: References the KPI indicator code from the BSC_KPI_CALCULATIONS table, identifying the performance metric involved.

Together, these columns record which user is associated with a particular calculation for a given indicator, forming the basis for user-level calculation management.

Common Use Cases and Queries

This table is central to queries that filter or report on KPI calculations for specific users or user groups. A common administrative use case is auditing which calculations are assigned to a particular user or identifying all users responsible for a specific indicator's calculations. For reporting, it enables the generation of user-specific scorecard dashboards by joining calculation results with user context.

A typical SQL pattern retrieves calculation details for a known user:

SELECT calc.*
FROM bsc_kpi_calculations calc,
     bsc_kpi_calculations_user usr
WHERE usr.user_id = :p_user_id
  AND usr.indicator = calc.indicator
  AND usr.calculation_id = calc.calculation_id;

Conversely, to list all users associated with a specific KPI calculation, one would query:

SELECT u.user_name
FROM bsc_users u, bsc_kpi_calculations_user cu
WHERE cu.indicator = :p_indicator
  AND cu.calculation_id = :p_calc_id
  AND cu.user_id = u.user_id;

Related Objects

The BSC_KPI_CALCULATIONS_USER table maintains defined foreign key relationships with two primary tables in the BSC schema, as documented in the ETRM metadata.

  • BSC_USERS: The table references BSC_USERS via the USER_ID column. This join provides access to the user's name and other profile information within the Balanced Scorecard context.
  • BSC_KPI_CALCULATIONS: The table references BSC_KPI_CALCULATIONS via a composite foreign key on the INDICATOR and CALCULATION_ID columns. This is the critical link to the underlying calculation data, including results, status, and period information.

These relationships ensure referential integrity and are fundamental for any join operation to retrieve meaningful user-calculation data. The table itself is primarily a supporting object for these core BSC entities.