Search Results csf_id




Overview
Explore in AI Chat

Overview

The BSC_TAB_IND_GROUPS_TL table is a core data object within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It functions as a translation table, storing multilingual descriptions and names for indicator groups. Indicator groups are logical collections of performance metrics (indicators) organized within specific tabs (TAB_ID) and strategic perspectives or cause-and-effect chains (CSF_ID) on a Balanced Scorecard. This table enables the global deployment of the BSC application by allowing user-facing text for these groups to be presented in the language specified by a user's session (NLS_LANGUAGE). Its role is to support the translatable seed data for the BSC module's configuration, separating language-specific text from the base transactional data stored in its parent table, BSC_TAB_IND_GROUPS_B.

Key Information Stored

The table's structure is defined by a composite primary key and columns for translated text. The primary key uniquely identifies a translation record by combining the following foreign key columns: CSF_ID, TAB_ID, and IND_GROUP_ID, along with the LANGUAGE code (e.g., 'US', 'DE'). The most critical data columns include IND_GROUP_NAME, which holds the translated name of the indicator group displayed to end-users, and potentially a DESCRIPTION field for further elaboration. The LANGUAGE column is a standard Oracle EBS column that stores the ISO language code for the translation. The CSF_ID, TAB_ID, and IND_GROUP_ID columns maintain referential integrity with the base table, ensuring every translation corresponds to a valid indicator group entity.

Common Use Cases and Queries

A primary use case is generating user interface labels or reports in a user's preferred language. Developers and report writers join this table with its base table to retrieve localized content. A common query pattern involves filtering by the session language and specific scorecard components. For example, to retrieve all translated indicator group names for a specific tab and perspective in the current session language, one might use:

  • SELECT t.ind_group_name, b.* FROM bsc_tab_ind_groups_b b, bsc_tab_ind_groups_tl t WHERE b.csf_id = t.csf_id AND b.tab_id = t.tab_id AND b.ind_group_id = t.ind_group_id AND t.language = USERENV('LANG');

Another critical scenario is during implementation or upgrade, where administrators may need to verify or audit the completeness of translations for all configured indicator groups across supported languages.

Related Objects

The table has a direct and fundamental relationship with its base transactional table, as documented in the provided metadata. The foreign key relationship is explicitly defined:

  • BSC_TAB_IND_GROUPS_B: This is the base table referenced by BSC_TAB_IND_GROUPS_TL. The translation table's columns CSF_ID, IND_GROUP_ID, and TAB_ID form a foreign key that references the corresponding composite primary key in BSC_TAB_IND_GROUPS_B. This ensures every translation record is tied to a valid base entity. The relationship is essential for any query requiring both the operational data from the base table and the translated text from this table.