Search Results bsc_kpis_tl




Overview
Explore in AI Chat

Overview

The BSC_KPIS_TL table is a core data object within the Oracle E-Business Suite (EBS) Balanced Scorecard (BSC) module. It functions as a translation table, storing multilingual text for Key Performance Indicators (KPIs). In a global deployment, where EBS is used across multiple regions with different languages, this table enables the display of KPI names, descriptions, and other textual attributes in a user's preferred language. Its role is to support the internationalization features of the BSC module by separating translatable text from the base transactional data, which resides in its parent table, BSC_KPIS_B. This design is a standard Oracle Applications pattern for handling multilingual support.

Key Information Stored

The table's structure is designed to map translated text to a specific base record and language. The primary key, BSC_KPIS_TL_PK, is a composite key consisting of two critical columns: INDICATOR and LANGUAGE. The INDICATOR column is a foreign key that links each translated row to a unique KPI identifier in the base BSC_KPIS_B table. The LANGUAGE column holds the language code (e.g., 'US' for American English, 'KO' for Korean) for the translation. While the specific translatable columns are not detailed in the provided metadata, typical TL tables in Oracle EBS contain columns such as NAME, DESCRIPTION, and potentially other user-facing text fields associated with the KPI entity. These columns hold the actual translated strings.

Common Use Cases and Queries

The primary use case is retrieving KPI information in a user's session language for display in BSC reports, dashboards, and configuration screens. Application logic automatically queries this table based on the user's profile option NLS_LANGUAGE. A common reporting query involves joining the translation table with its base table to present a complete, language-specific view of KPI data. A typical SQL pattern is:

  • SELECT kpb.INDICATOR, kpt.NAME, kpt.DESCRIPTION, kpb.other_base_columns FROM BSC_KPIS_B kpb, BSC_KPIS_TL kpt WHERE kpb.INDICATOR = kpt.INDICATOR AND kpt.LANGUAGE = USERENV('LANG');

This ensures that the textual components of the KPI are presented correctly. Data maintenance for this table is typically performed via the BSC module's application screens, which manage the underlying translation mechanics, rather than through direct SQL manipulation.

Related Objects

The BSC_KPIS_TL table has a direct and dependent relationship with several key BSC objects. Its most critical relationship is defined by a foreign key constraint to the BSC_KPIS_B table, which is the base table for all KPI definitions, holding non-translatable attributes like numeric IDs, configuration flags, and creation metadata. In application code, this table is accessed via views that perform the necessary joins and language filtering, such as BSC_KPIS_VL (where "VL" typically denotes a View, Localized). For programmatic access and data integrity, Oracle EBS provides PL/SQL APIs within the BSC product's package hierarchy (e.g., packages prefixed with BSC_) that handle create, update, and delete operations for KPI data, including its translations.