Search Results bsc_sys_labels_tl




Overview
Explore in AI Chat

Overview

BSC_SYS_LABELS_TL is the translation table for the Oracle Balanced Scorecard (BSC) module, which is part of the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 distributions. The table stores translated (language-specific) label text used throughout the Balanced Scorecard application, allowing descriptive names and captions for scorecard objects to be presented in the user's preferred language. It resides in the BSC schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the mined foreign-key structure classifies BSC_SYS_LABELS_TL as satellite-leaning. This suggests that the table is best understood as a descriptive, context-dependent complement to a base (hub-like) entity. In practice, BSC_SYS_LABELS_B serves as the base table holding the language-independent label definition, while BSC_SYS_LABELS_TL holds the per-language descriptive attributes attached to that definition.

Key Information Stored

The documented physical schema for 12.1.1 contains six columns: SOURCE_TYPE, SOURCE_CODE, LABEL_ID, LANGUAGE, SOURCE_LANG, and NAME. The most important of these are:

  • LABEL_ID — Surrogate identifier for the label record; part of the composite primary key and the join key back to the base table.
  • LANGUAGE — The language code for which the translated text applies; part of the primary key.
  • SOURCE_CODE and SOURCE_TYPE — Identify the originating Balanced Scorecard object or label source, and are both part of the composite primary key and the foreign key to BSC_SYS_LABELS_B.
  • NAME — The translated label text displayed to end users; this is the primary descriptive payload of the table.
  • SOURCE_LANG — The source language from which the translation was derived, used for translation lineage and fallback logic.

The composite primary key BSC_SYS_LABELS_TL_PK is defined over (LABEL_ID, LANGUAGE, SOURCE_CODE, SOURCE_TYPE). A unique index, BSC_SYS_LABELS_TL_U1, is defined over (SOURCE_TYPE, SOURCE_CODE, LABEL_ID, LANGUAGE) and represents the documented business-key candidate, ensuring one translation row per label per language.

Common Use Cases and Queries

Typical usage centers on multilingual reporting and label resolution. A frequent pattern joins the translation table to the base table to retrieve localized label text:

  • Retrieving a translated label for a specific object and language: SELECT NAME FROM BSC_SYS_LABELS_TL WHERE LABEL_ID = :id AND LANGUAGE = :lang;
  • Auditing which labels have translations missing for a target language by comparing against BSC_SYS_LABELS_B.
  • Joining on SOURCE_CODE and SOURCE_TYPE to associate translations with their originating scorecard definitions.
  • Reporting on translation coverage, listing all languages in which a given label is defined.

Because the table is language-segmented, reporting queries should always constrain or group by LANGUAGE to avoid duplicate rows per label.

Related Objects

  • BSC_SYS_LABELS_B — The base label table; BSC_SYS_LABELS_TL joins to it via SOURCE_CODE and SOURCE_TYPE (LABEL_ID relationship). This is the documented foreign-key target and the primary related object.
  • BSC_SYS_LABELS_TL_PK — The composite primary key constraint over LABEL_ID, LANGUAGE, SOURCE_CODE, SOURCE_TYPE.
  • BSC_SYS_LABELS_TL_U1 — The unique index over SOURCE_TYPE, SOURCE_CODE, LABEL_ID, LANGUAGE.
  • BSC_SCORECARD / BSC_* definition tables — Application objects that reference labels through their label identifiers.
  • FND_LANGUAGES — Provides the installed language definitions against which the LANGUAGE and SOURCE_LANG columns are interpreted.

Together these objects support the Balanced Scorecard's multilingual label infrastructure within the BSC schema.