Search Results bsc_kpi_analysis_options_tl

Overview

The BSC_KPI_ANALYSIS_OPTIONS_TL table is a core translation table within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It stores the multilingual, user-facing descriptions for the analysis options defined in the system. This table supports the global deployment of the Balanced Scorecard application by enabling the display of analysis option names and descriptions in a user's preferred language (NLS). Its role is to provide the translated textual content that populates analysis trees and selection lists within the application's user interface, while the base, non-translatable data is stored in its corresponding base table, BSC_KPI_ANALYSIS_OPTIONS_B.

Key Information Stored

The table's structure is designed to support a hierarchical tree of analysis options while accommodating multiple languages. Its primary key is a composite of several columns that uniquely identify a specific translation for a node within the analysis hierarchy. The critical columns include OPTION_ID, PARENT_OPTION_ID, and GRANDPARENT_OPTION_ID, which define the hierarchical position of the analysis option. The INDICATOR and ANALYSIS_GROUP_ID columns link the option to its associated Key Performance Indicator (KPI) and analysis group context. The LANGUAGE column holds the language code (e.g., 'US' for American English) for the translation. The most significant user-facing column is typically NAME, which stores the translated label for the analysis option as it appears to end-users in forms and reports.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to render localized content. Common technical and reporting use cases involve retrieving the full descriptive hierarchy for a KPI in a specific language or auditing translation coverage. A typical query to fetch the analysis tree for a given indicator would join the translation (TL) table with its base (B) table, filtered by language and indicator ID. For example:

• SELECT tl.name, tl.option_id, tl.parent_option_id FROM bsc_kpi_analysis_options_tl tl WHERE tl.indicator = :p_indicator_id AND tl.language = USERENV('LANG') ORDER BY tl.option_id;

Another common pattern is to check for missing translations by comparing records across installed languages for critical analysis options, which is vital for implementation support and upgrade validation.

Related Objects

The BSC_KPI_ANALYSIS_OPTIONS_TL table has a mandatory and integral relationship with its base table, as defined by its foreign key constraints. All key columns reference the BSC_KPI_ANALYSIS_OPTIONS_B table, establishing it as the single source of non-translatable data. The specific foreign key relationships, with the columns in the TL table that reference the B table, are:

• BSC_KPI_ANALYSIS_OPTIONS_TL.OPTION_ID
• BSC_KPI_ANALYSIS_OPTIONS_TL.PARENT_OPTION_ID
• BSC_KPI_ANALYSIS_OPTIONS_TL.GRANDPARENT_OPTION_ID
• BSC_KPI_ANALYSIS_OPTIONS_TL.INDICATOR
• BSC_KPI_ANALYSIS_OPTIONS_TL.ANALYSIS_GROUP_ID

This structure ensures that every translated record is anchored to a valid entity in the base table. The table is also central to any views or APIs within the BSC module that present analysis option data to end-users or integration points.