Search Results comment_type

Overview

The BSC_KPI_COMMENTS table is a core data repository within the Oracle E-Business Suite (EBS) Balanced Scorecard (BSC) application. It is designed to store user-generated commentary and assessments associated with Key Performance Indicators (KPIs), also referred to as indicators, across specific time dimensions. This table facilitates collaborative performance analysis by allowing users to document qualitative insights, explanations for trends, and strategic observations directly linked to quantitative KPI results. Its role is to provide essential context to the numerical data, enabling a more comprehensive performance management process within the Oracle EBS framework.

Key Information Stored

The table's structure is organized to uniquely identify a comment's context and its content. The primary key is the COMMENT_ID column. The context of a comment is defined by the combination of the INDICATOR, YEAR, PERIODICITY_ID, and PERIOD_ID columns, which pin the comment to a specific indicator for a precise time period. The COMMENT_TYPE field, central to the user's search, categorizes the nature of the comment, though its specific lookup values (e.g., General Note, Action Item, Root Cause) are defined elsewhere in the application. The qualitative content is stored in COMMENT_SUBJECT and COMMENT_TEXT columns. Additional columns like TREND_FLAG and COLOR_FLAG store user assessments of performance quality, while standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide audit trails.

Common Use Cases and Queries

A primary use case is retrieving all comments for a specific KPI to review historical discussions and assessments. For example, a report showing comments for indicator 1001 in the fiscal year 2023 would use a query filtering on the INDICATOR and YEAR columns. Another critical scenario involves fetching comments of a particular type, such as action items or root cause analyses, by joining the BSC_KPI_COMMENTS table to the relevant lookup table for COMMENT_TYPE. Administrators may also run queries to audit comment activity or identify indicators with the most user engagement. A typical reporting query pattern is:

• SELECT c.COMMENT_SUBJECT, c.COMMENT_TEXT, u.USER_NAME, c.CREATION_DATE
• FROM BSC.BSC_KPI_COMMENTS c, FND_USER u
• WHERE c.INDICATOR = :p_indicator
• AND c.COMMENT_TYPE = :p_comment_type_lookup_code
• AND c.CREATED_BY = u.USER_ID
• ORDER BY c.CREATION_DATE DESC;

Related Objects

According to the provided dependency information, the BSC_KPI_COMMENTS table is referenced by an APPS synonym named BSC_KPI_COMMENTS. This synonym facilitates access to the table from other schemas within the EBS environment, following standard Oracle EBS practices. While the metadata excerpt does not list specific foreign key relationships or dependent views, in a typical BSC implementation, this table would be closely related to the main KPI definition tables (such as BSC_KPIS_B or BSC_SYS_INDICATORS_B) to validate the INDICATOR code. The COMMENT_TYPE column would reference a lookup type (likely BSC_COMMENT_TYPE) to provide its list of valid values. The table is indexed on COMMENT_ID (unique) and on a combination of INDICATOR, LAST_UPDATE_DATE, and LAST_UPDATED_BY for performance.