Search Results bm_id

Overview

The BSC_SYS_BENCHMARKS_B table is a core repository for benchmark definitions within the now-obsolete Balanced Scorecard (BSC) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Benchmarks serve as critical reference points or targets against which Key Performance Indicators (KPIs) and strategic objectives are measured, enabling performance comparison and gap analysis. As a base or transactional table, it stores the fundamental, non-translatable attributes of each benchmark. Its primary role is to act as a master data source for benchmark entities, which are subsequently referenced by various scorecard components for performance tracking and reporting. The metadata explicitly notes this table is "Not implemented in this database," indicating it may exist in the data dictionary but is not populated or actively used in standard deployments, consistent with the module's obsolete status.

Key Information Stored

The table's structure centers on a unique identifier for each benchmark record. The most critical column is BM_ID, which serves as the primary key. This numeric identifier uniquely defines each benchmark entry within the system and is the column referenced by all related foreign key constraints. Another significant column is PERIODICITY_ID, a foreign key linking to the BSC_SYS_PERIODICITIES table. This defines the time frequency (e.g., monthly, quarterly) associated with the benchmark's measurement or target values. While the full column list is not detailed in the excerpt, typical attributes for such a table would include creation dates, last update dates, and other system-level audit columns.

Common Use Cases and Queries

In an active BSC implementation, this table would be queried to retrieve benchmark master data for configuration, reporting, and integration. Common operational scenarios include listing all defined benchmarks for administration, fetching specific benchmark details for a KPI setup, or extracting benchmark metadata for data loads. A fundamental query pattern involves joining with its corresponding translation table, BSC_SYS_BENCHMARKS_TL, to retrieve the name and description in a specific language. A sample SQL to retrieve benchmark basics would be:

• SELECT b.BM_ID, t.NAME, b.PERIODICITY_ID FROM BSC_SYS_BENCHMARKS_B b, BSC_SYS_BENCHMARKS_TL t WHERE b.BM_ID = t.BM_ID AND t.LANGUAGE = USERENV('LANG');

Reporting use cases would involve joining this table to fact or measurement tables (not explicitly listed in the metadata) to analyze actual performance against defined benchmark targets.

Related Objects

The BSC_SYS_BENCHMARKS_B table maintains defined relationships with several other BSC module objects, primarily through its primary key column, BM_ID. The documented foreign key relationships are as follows:

• BSC_SYS_BENCHMARKS_TL: The translation table. Joined on BSC_SYS_BENCHMARKS_TL.BM_ID = BSC_SYS_BENCHMARKS_B.BM_ID to provide multilingual names and descriptions.
• BSC_KPI_SERIES_COLORS: Likely stores display formatting (e.g., chart colors) for benchmark series. Joined on BSC_KPI_SERIES_COLORS.BM_ID = BSC_SYS_BENCHMARKS_B.BM_ID.
• BSC_SYS_BM_GROUPS: Presumably allows for the categorization or grouping of benchmarks. Joined on BSC_SYS_BM_GROUPS.BM_ID = BSC_SYS_BENCHMARKS_B.BM_ID.

Furthermore, this table references the BSC_SYS_PERIODICITIES table via its foreign key column, PERIODICITY_ID, to define the benchmark's time frequency.