Results for “bsc_sys_benchmarks_tl”

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

Overview

BSC_SYS_BENCHMARKS_TL is the translation table for the Oracle Balanced Scorecard (BSC) benchmarks entity. In Oracle EBS 12.1.1 and 12.2.2, it stores the language-dependent, translated attributes of benchmark definitions whose language-independent structure is persisted in BSC_SYS_BENCHMARKS_B. The "_TL" suffix identifies it as a translated table managed through the standard Oracle Applications multilingual (MLS) architecture, in which each row is keyed by both the entity identifier and a LANGUAGE code.

The benchmarks feature supports Balanced Scorecard performance measurement by defining targets and comparison baselines against which scorecard metrics are evaluated. Because benchmark names must be presented in each user's session language, the translatable text is isolated in this table while numeric and structural attributes remain in the base table. Under the heuristic Data Vault classification supplied in the ETRM metadata, BSC_SYS_BENCHMARKS_TL is satellite-leaning: it carries descriptive, language-scoped context that hangs off the BSC_SYS_BENCHMARKS_B hub key rather than defining new business entities or relationships.

Key Information Stored

The documented physical schema for ETRM 12.1.1 lists four columns under the BSC schema:

• BM_ID — The benchmark identifier. This is the surrogate primary key component and the foreign key to BSC_SYS_BENCHMARKS_B, linking each translated row to its base entity record. It carries no independent meaning and is system-generated.
• LANGUAGE — The Oracle language code (for example, US for American English) indicating the locale in which the translated text is valid. It is the second component of the composite primary key.
• SOURCE_LANG — The language from which the row's text was derived, supporting the MLS translation-tracking convention used across Oracle Applications.
• NAME — The translated display name of the benchmark, and the principal business-facing attribute of this table. It is the value surfaced in Balanced Scorecard setup screens and reports.

The composite primary key BSC_SYS_BENCHMARKS_TL_PK is defined on (BM_ID, LANGUAGE). A unique index, BSC_SYS_BENCHMARKS_TL_U1, is also defined on (BM_ID, LANGUAGE), mirroring the primary key. Taken together, BM_ID plus LANGUAGE constitute the business-key candidate, since no separate natural key is documented; the surrogate key is BM_ID paired with the language discriminator.

Common Use Cases and Queries

Translation tables are queried principally for reporting and interface purposes. A typical pattern retrieves the benchmark name in the session language, falling back to the base language when no translation exists:

• Join BSC_SYS_BENCHMARKS_TL to BSC_SYS_BENCHMARKS_B on BM_ID to combine structural benchmark attributes with translated names.
• Filter on LANGUAGE to list all benchmark names in a specific locale, useful for translation audits and completeness checks against SOURCE_LANG.
• Detect missing translations by identifying base-table rows having no corresponding TL row for a required language.
• Feed benchmark labels into Balanced Scorecard scorecard, objective, and metric reporting extracts.

A representative query is: SELECT b.bm_id, t.name FROM bsc_sys_benchmarks_b b, bsc_sys_benchmarks_tl t WHERE b.bm_id = t.bm_id AND t.language = 'US';

Related Objects

The following objects are most significant in relation to this table:

• BSC_SYS_BENCHMARKS_B — The base table referenced through the foreign key BSC_SYS_BENCHMARKS_TL.BM_ID; it holds the language-independent benchmark definition.
• BSC_SYS_BENCHMARKS_TL_PK — The primary key constraint on (BM_ID, LANGUAGE) enforcing uniqueness.
• BSC_SYS_BENCHMARKS_TL_U1 — The unique index on (BM_ID, LANGUAGE) supporting business-key lookups.
• FND_LANGUAGES — The Oracle Applications language reference table against which LANGUAGE and SOURCE_LANG values are interpreted.
• Balanced Scorecard benchmark setup pages — The application forms and OAF pages that read and maintain translated NAME values.

Together these objects form the benchmark master-detail structure within the BSC module.