Search Results bsc_kpi_comments_pk

Overview

The BSC_KPI_COMMENTS table is a data object within the Oracle E-Business Suite (EBS) module for Balanced Scorecard (BSC), which is documented as obsolete. This table serves as a repository for user-generated textual commentary associated with specific Key Performance Indicators (KPIs). Its primary role is to capture contextual notes, explanations, or qualitative assessments related to an indicator's performance, supplementing the quantitative data stored elsewhere. This functionality supports collaborative performance analysis and audit trails within the Balanced Scorecard framework. The provided metadata explicitly states this table is "Not implemented in this database," indicating it may not be present or populated in all EBS 12.1.1 or 12.2.2 instances, a critical consideration for any technical analysis or customization.

Key Information Stored

The table's structure is designed to link comments directly to specific KPIs and time periods. While a full column list is not provided in the excerpt, the primary and foreign key relationships reveal its core data elements. The composite primary key (BSC_KPI_COMMENTS_PK) consists of CREATED_BY, CREATION_DATE, and INDICATOR, ensuring a unique record for each comment tied to its creator and timestamp. The INDICATOR column is the foreign key linking to the BSC_KPIS_B table, identifying the relevant KPI. Additional key columns include PERIODICITY_ID and PERIOD_ID, which, along with YEAR, form foreign keys to the BSC_SYS_PERIODS_TL table, anchoring the comment to a specific reporting period (e.g., "Q1 2023"). This structure allows for period-specific commentary on each KPI.

Common Use Cases and Queries

The primary use case is retrieving all comments for a given KPI to provide a full historical context during performance reviews. A developer might also query for comments made within a specific date range or by a particular user for audit purposes. Given the table's likely obsolete status, direct operational use in newer implementations is rare; however, understanding its schema remains important for data migration, historical reporting, or supporting legacy customizations. A typical query pattern would join BSC_KPI_COMMENTS to BSC_KPIS_B to fetch KPI names alongside the comments.

SELECT kpi.NAME, comm.COMMENTS, comm.CREATED_BY, comm.CREATION_DATE
FROM BSC_KPI_COMMENTS comm,
     BSC_KPIS_B kpi
WHERE comm.INDICATOR = kpi.INDICATOR
AND comm.INDICATOR = :p_indicator_id
ORDER BY comm.CREATION_DATE DESC;

Related Objects

The table maintains defined foreign key relationships with core Balanced Scorecard tables, as documented in the ETRM metadata.

• BSC_KPIS_B: This is the base table for Key Performance Indicators. The BSC_KPI_COMMENTS.INDICATOR column references BSC_KPIS_B, establishing that every comment must be associated with a valid, existing indicator.
• BSC_SYS_PERIODS_TL: This table defines the periodicity and time periods for scorecard reporting. The relationship is defined through the columns BSC_KPI_COMMENTS.PERIODICITY_ID and BSC_KPI_COMMENTS.PERIOD_ID (and implied through YEAR) referencing BSC_SYS_PERIODS_TL, ensuring comments are linked to the correct fiscal calendar period.