Results for “comment_subject”

5 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC_KPI_COMMENTS is a table within the Balanced Scorecard (BSC) module of Oracle E-Business Suite, historically shipped in releases 12.1.1 and 12.2.2. As the name implies, it stores free-text annotations associated with Key Performance Indicators defined in the scorecard subsystem. Each row captures a comment, note, or qualitative observation tied to a specific indicator, its period, and its periodicity, allowing planners and analysts to record explanations behind KPI values without altering the underlying metric data.

The ETRM metadata explicitly flags this object as “Obsolete,” and it is not implemented in the current database. Consequently, it functions as a legacy artifact retained for upgrade, migration, and data-archaeology purposes rather than an active transactional table. Teams completing a 12.1.1 to 12.2.2 upgrade or a data warehouse migration will encounter BSC_KPI_COMMENTS in the ETRM repository and must decide whether to extract, archive, or discard its contents.

Applying a heuristic Data Vault classification, the FK structure indicates that BSC_KPI_COMMENTS behaves as a link — the metadata itself classifies it as “link” based on the mined foreign-key relationships. Its foreign keys to BSC_KPIS_B and BSC_SYS_PERIODS_TL form the many-to-many association between indicators and time periods, with the descriptive comment attributes riding along on that relationship.

Key Information Stored

The documented physical schema for 12.1.1 lists 15 columns owned by the BSC schema. The most operationally significant columns are:

  • COMMENT_ID — the surrogate identifier for each comment row. It is anchored by the unique index BSC_KPI_COMMENTS_U2, making it the strongest business-key candidate in the table.
  • INDICATOR — the foreign key pointing to BSC_KPIS_B, identifying the KPI to which the comment belongs. It also participates in the primary key BSC_KPI_COMMENTS_PK alongside CREATED_BY and CREATION_DATE.
  • COMMENT_SUBJECT and COMMENT_TEXT — the human-readable heading and body of the annotation, representing the core payload of the table.
  • COMMENT_TYPE — a classifier that distinguishes categories of commentary (for example, explanatory, corrective, or informational).
  • YEAR, PERIODICITY_ID, and PERIOD_ID — the temporal coordinates of the comment. PERIODICITY_ID and PERIOD_ID participate in the composite foreign key to BSC_SYS_PERIODS_TL.
  • TREND_FLAG and COLOR_FLAG — indicator state markers, likely used to communicate directional trend and scorecard color status alongside the comment.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit columns, with the first two forming part of the composite primary key.

Common Use Cases and Queries

Because the object is obsolete and unimplemented, the primary use cases are historical extraction, upgrade validation, and archival reporting. A typical extraction joins comments to their parent indicator and period definitions:

SELECT k.indicator, k.name, c.comment_subject, c.comment_text,
       c.year, c.period_id, c.comment_type, c.trend_flag, c.color_flag
FROM   bsc_kpi_comments c,
       bsc_kpis_b       k,
       bsc_sys_periods_tl p
WHERE  c.indicator       = k.indicator
AND    c.periodicity_id  = p.periodicity_id
AND    c.period_id       = p.period_id
AND    c.year            = :target_year;

Analysts often filter on COMMENT_TYPE to isolate corrective versus explanatory notes, or on TREND_FLAG and COLOR_FLAG to correlate commentary with adverse indicator movement. Migration scripts use BSC_KPI_COMMENTS_U2 (COMMENT_ID) to detect duplicate rows during a re-load, while audit queries group by CREATED_BY and CREATION_DATE to reconstruct who annotated which KPI and when. Because it is not present in active 12.2.2 environments, any remediation effort should first confirm row counts via the ETRM repository before scripting deletes or archival moves.

Related Objects

The following objects are directly implicated by the documented relationships:

  • BSC_KPIS_B — the base indicator definition table; joined via BSC_KPI_COMMENTS.INDICATOR.
  • BSC_SYS_PERIODS_TL — the translated period definitions; joined via PERIODICITY_ID and PERIOD_ID.
  • BSC_KPI_COMMENTS_PK — the composite primary key (CREATED_BY, CREATION_DATE, INDICATOR) enforcing row uniqueness.
  • BSC_KPI_COMMENTS_U2 — the unique index on COMMENT_ID, used as the business-key candidate.
  • Related BSC scorecard tables such as BSC_KPIS_TL, BSC_INDICATORS, and periodicity definitions that share the same schema family and are commonly queried alongside this table during migration and archive work.

No public API is documented for this obsolete object; all access is expected to be read-only via SQL against archived or legacy schemas.