Search Results bsc_sys_datasets_tl_pk

Overview

The BSC_SYS_DATASETS_TL table is a core data object within the Balanced Scorecard (BSC) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. As a translation table (indicated by the "_TL" suffix), its primary role is to store multilingual, user-facing descriptions for datasets. A dataset in the Balanced Scorecard context is a defined collection of data used for analysis and performance measurement. This table enables the global deployment of the BSC module by allowing the dataset names and descriptions to be presented in the language of the end-user, supporting the application's internationalization features. It functions as the child table in a master-detail relationship with its base table, BSC_SYS_DATASETS_B.

Key Information Stored

The table stores translated text for datasets, with each record uniquely identified by a composite primary key. The critical columns include DATASET_ID, which is a foreign key linking the translation to a specific dataset defined in the base table BSC_SYS_DATASETS_B. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'KO' for Korean) for the translation. The most significant user-facing column is typically DATASET_NAME, which holds the translated name of the dataset as it should appear in reports and user interfaces. Additional columns may exist to store a longer description or other translatable attributes, though the provided metadata confirms the core structure of the primary and foreign keys.

Common Use Cases and Queries

The primary use case is retrieving a dataset's name in a user's session language for display within BSC screens, reports, and analytics. A common query pattern involves joining this table with its base table and filtering by the desired language. For instance, to list all active datasets with their English names, a developer might write:

• SELECT b.DATASET_CODE, tl.DATASET_NAME FROM BSC_SYS_DATASETS_B b, BSC_SYS_DATASETS_TL tl WHERE b.DATASET_ID = tl.DATASET_ID AND tl.LANGUAGE = USERENV('LANG');

Another critical scenario is during the implementation of additional languages, where data from this table is populated or updated via Oracle's translation tools. Reporting on translation completeness (checking for missing translations for key datasets) is also a frequent administrative task.

Related Objects

The table has a direct and documented dependency on the BSC_SYS_DATASETS_B table, which stores the non-translatable, base information for datasets. The relationship is enforced by a foreign key constraint where BSC_SYS_DATASETS_TL.DATASET_ID references BSC_SYS_DATASETS_B.DATASET_ID. This is a classic EBS Translation Table architecture. The primary key constraint BSC_SYS_DATASETS_TL_PK on (DATASET_ID, LANGUAGE) ensures uniqueness of translations. Other application objects, such as BSC views, forms, and APIs, will reference this table indirectly through its base table to present localized content.