Results for “bsc_kpis_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BSC_KPIS_TL is the translation (MLS) table for Key Performance Indicators within the Oracle E-Business Suite Balanced Scorecard (BSC) module. It belongs to the BSC schema and holds language-specific, translated attributes for each KPI defined in the base table BSC_KPIS_B. In Oracle EBS 12.1.1 and 12.2.2, the BSC module provides scorecarding, strategy management, and performance measurement capabilities, and this table enables KPI names and descriptive help text to be presented in multiple installed languages.

The object is documented as VALID with owner BSC, and it carries a primary key BSC_KPIS_TL_PK on the columns (INDICATOR, LANGUAGE). Based on the mined foreign key structure — a single FK from INDICATOR to BSC_KPIS_B — the heuristic Data Vault classification is satellite-leaning. This suggests the table behaves as a descriptive satellite attached to the BSC_KPIS_B hub, where the hub's business key is the indicator identifier and LANGUAGE acts as an additional qualifier of the descriptive context.

Key Information Stored

The documented physical schema for 12.1.1 contains five columns. The most significant are:

• INDICATOR — The business identifier of the KPI. This is the foreign key referencing BSC_KPIS_B and forms part of the composite primary key.
• LANGUAGE — The language code for the translated row. Together with INDICATOR it constitutes the primary key BSC_KPIS_TL_PK and the unique index BSC_KPIS_TL_U1.
• SOURCE_LANG — Indicates the source language from which the translation was derived, supporting the MLS translation workflow.
• NAME — The translated display name of the KPI shown to users in the selected language.
• HELP — The translated help or descriptive text associated with the KPI.

The composite primary key (INDICATOR, LANGUAGE) is the surrogate/qualified key, while the unique index BSC_KPIS_TL_U1 on the same columns serves as the business-key candidate, ensuring one translated row per KPI per language. The base, non-translated attributes reside in BSC_KPIS_B; only the language-dependent text is stored here.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and displaying KPI definitions in the user's session language. A common query joins the translation table to its base table to retrieve the localized name and help text:

• Retrieve translated KPI details: SELECT b.indicator, t.name, t.help FROM bsc.bsc_kpis_b b, bsc.bsc_kpis_tl t WHERE b.indicator = t.indicator AND t.language = USERENV('LANG');
• Audit available translations for a KPI: SELECT indicator, language, name FROM bsc.bsc_kpis_tl WHERE indicator = :indicator;
• Identify KPIs missing a translation in a target language by outer-joining the base and translation tables and filtering on NULL NAME.
• Feed localized KPI labels into custom Balanced Scorecard reports, dashboards, or extracts that must conform to a specific LANGUAGE value.

Because the table is MLS-enabled, direct DML should generally be avoided in favor of the standard translation maintenance UI, ensuring SOURCE_LANG and LANGUAGE remain consistent.

Related Objects

• BSC_KPIS_B — The base (non-translated) KPI table. Joined on BSC_KPIS_TL.INDICATOR = BSC_KPIS_B.INDICATOR via the documented foreign key.
• BSC_KPIS_TL_PK / BSC_KPIS_TL_U1 — The primary key constraint and unique index on (INDICATOR, LANGUAGE).
• BSC scorecard and strategy tables — KPI definitions referenced through BSC_KPIS_B are consumed by scorecard objective and measurement objects in the BSC module.
• FND_LANGUAGES — The EBS language reference used to validate and interpret the LANGUAGE and SOURCE_LANG values.
• BSC KPI maintenance forms and concurrent programs — Application-tier components that read and write translated KPI text through the MLS framework.