Search Results bsc_kpi_analysis_measurestl_pk

Overview

The BSC_KPI_ANALYSIS_MEASURES_TL table is a translation table within the Oracle E-Business Suite Balanced Scorecard (BSC) module. Its primary role is to store translated, language-specific descriptions for key performance indicator (KPI) analysis measures. This enables the application to present measure names and related text in a user's preferred language, supporting global deployments. The table is part of a multi-language architecture common in Oracle EBS, where a base table (BSC_KPI_ANALYSIS_MEASURES_B) holds the language-independent data, and a corresponding "_TL" table holds the translated text. It is critical to note that the metadata explicitly classifies the BSC module as "Obsolete," indicating this table is part of a legacy, potentially unsupported, application component in both the 12.1.1 and 12.2.2 versions.

Key Information Stored

The table stores translated text for uniquely identified analysis measures. Its structure, as defined by its primary and foreign keys, reveals the composite nature of its data. The primary key, BSC_KPI_ANALYSIS_MEASURESTL_PK, is composed of several columns that together uniquely identify a single translation record. These include: ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2, INDICATOR, SERIES_ID, and LANGUAGE. The LANGUAGE column specifies the language code (e.g., 'US' for American English) for the translation. The other key columns serve as foreign keys linking back to the corresponding record in the base table (BSC_KPI_ANALYSIS_MEASURES_B). While the specific content column (e.g., MEASURE_NAME) is not listed in the provided metadata, standard Oracle translation table design dictates it would contain at least one column for the translated text itself, such as a NAME or DESCRIPTION field.

Common Use Cases and Queries

The primary use case is retrieving KPI analysis measure descriptions for a user session's language context within the Balanced Scorecard interface. This is typically handled automatically by the application's multi-language support libraries. For reporting or data extraction purposes, a developer might join this table to its base table to get a complete, language-specific dataset. A common query pattern would utilize the NLS_LANGUAGE session parameter or a specified language code.

• Sample Query for a Specific Language: SELECT b.INDICATOR, tl.NAME FROM BSC_KPI_ANALYSIS_MEASURES_B b, BSC_KPI_ANALYSIS_MEASURES_TL tl WHERE b.ANALYSIS_OPTION0 = tl.ANALYSIS_OPTION0 AND b.ANALYSIS_OPTION1 = tl.ANALYSIS_OPTION1 AND b.ANALYSIS_OPTION2 = tl.ANALYSIS_OPTION2 AND b.INDICATOR = tl.INDICATOR AND b.SERIES_ID = tl.SERIES_ID AND tl.LANGUAGE = 'US';
• Data Integrity Check: Queries to identify base records missing translations for critical languages are also common during implementation support.

Related Objects

The table's relationships are explicitly defined by its foreign key constraints. Its sole and fundamental relationship is with the base table BSC_KPI_ANALYSIS_MEASURES_B. All key columns (ANALYSIS_OPTION0, ANALYSIS_OPTION1, ANALYSIS_OPTION2, INDICATOR, SERIES_ID) reference the primary key of the base table. This enforces referential integrity, ensuring every translation record corresponds to a valid master record. Given the module's obsolete status, this table is unlikely to be referenced by newer APIs or integration points. Any application logic or forms within the BSC module that display analysis measure names will inherently depend on this table when operating in a non-base language environment.