Search Results bsc_tab_view_kpi_tl_pk




Overview
Explore in AI Chat

Overview

BSC_TAB_VIEW_KPI_TL is a translation (TL) table within the Oracle Balanced Scorecard (BSC) module, which is documented in Oracle E-Business Suite 12.1.1 and 12.2.2 as obsolete. The table stores translated indicator-by-tab-view information, meaning it holds language-specific display attributes and textual characteristics for Key Performance Indicators (KPIs) as they appear on Balanced Scorecard tab views. The "_TL" suffix follows the standard EBS multilingual convention: a base table stores language-independent data, while its _TL companion stores the same business rows once per installed language, keyed in part by the LANGUAGE column.

Under the heuristic Data Vault classification mined from its foreign-key structure, this object is characterized as standalone. As a modeling suggestion, this means it does not behave as a classic hub, link, or satellite in a Data Vault sense, because no FK relationships to parent hubs were detected. In practice, however, its composite key of TAB_ID, TAB_VIEW_ID, LANGUAGE, and INDICATOR strongly suggests it functions as a descriptive satellite attached to the combination of a scorecard tab, a tab view, and an indicator, with LANGUAGE acting as an additional qualifier for translation semantics.

The metadata explicitly documents that the table is "Not implemented in this database" in the ETRM reference environment, which indicates that in many EBS 12.1.1/12.2.2 instances the Balanced Scorecard product is either not installed or not licensed. This status should be confirmed in any target environment before developing dependent objects.

Key Information Stored

The table contains 23 documented physical columns. The most significant of these fall into three groupings: keys, translation controls, and presentation attributes.

  • TAB_ID – Identifier of the Balanced Scorecard tab to which the indicator display belongs.
  • TAB_VIEW_ID – Identifier of the specific tab view within the scorecard.
  • INDICATOR – The KPI/indicator identified in the tab view context.
  • LANGUAGE – The language in which the translated display data is stored; distinguishes one _TL row from another for the same business key.
  • SOURCE_LANG – The source language from which the translation was derived.
  • TEXT_FLAG – Flag governing textual display behavior for the translated indicator.
  • LEFT_POSITION, TOP_POSITION – Horizontal and vertical coordinates positioning the indicator on the tab view.
  • WIDTH, HEIGHT – Dimensions of the indicator's display region.
  • FONT_SIZE, FONT_STYLE, FONT_COLOR – Typography attributes controlling how the indicator label renders.
  • COLOR_LEFT_POSITION, COLOR_TOP_POSITION, COLOR_WIDTH, COLOR_HEIGHT, COLOR_SIZE – Geometry and sizing for the color-coded indicator region.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS auditing (WHO) columns tracking row creation and modification.

The surrogate primary key, BSC_TAB_VIEW_KPI_TL_PK, is defined over TAB_ID, TAB_VIEW_ID, LANGUAGE, and INDICATOR. A separate unique index, BSC_TAB_VIEW_KPI_TL_U1, is defined over TAB_ID, TAB_VIEW_ID, INDICATOR, and LANGUAGE — the same column set in different order. This U1 index represents the documented business-key candidate enforcing uniqueness of a translated indicator per tab view per language.

Common Use Cases and Queries

Because the table is translated, queries typically resolve a specific language or join to the base BSC table to obtain default-language values. A representative reporting query retrieves the positioned indicator display for a given tab view and language:

  • SELECT TAB_ID, TAB_VIEW_ID, INDICATOR, LANGUAGE, LEFT_POSITION, TOP_POSITION, WIDTH, HEIGHT, FONT_SIZE, FONT_COLOR FROM BSC_TAB_VIEW_KPI_TL WHERE TAB_ID = :p_tab_id AND TAB_VIEW_ID = :p_tab_view_id AND LANGUAGE = USERENV('LANG');
  • Comparing translations against the base language: filter on SOURCE_LANG to audit which rows derive from the primary language.
  • Layout auditing: aggregate on FONT_SIZE, WIDTH, and HEIGHT to detect inconsistent indicator sizing across tab views.
  • Metadata inventory: query ALL_TAB_COLUMNS or FND_TABLES for BSC_TAB_VIEW_KPI_TL to confirm installation before use.

Typical scenarios include custom Balanced Scorecard reporting, multilingual dashboard validation, and migration checks when assessing whether BSC data exists in an instance.

Related Objects

Given the documented standalone classification, no foreign keys were mined, so related objects are inferred from the BSC tab-view domain rather than from explicit FK metadata:

  • BSC_TAB_VIEW_KPI_B – The base (non-translated) counterpart holding language-independent indicator-by-tab-view data; joins on TAB_ID, TAB_VIEW_ID, and INDICATOR.
  • BSC_TABS_B / BSC_TABS_TL – Define the scorecard tabs referenced by TAB_ID.
  • BSC_TAB_VIEWS_B – Define tab views referenced by TAB_VIEW_ID.
  • BSC_KPI_B / BSC_KPI_TL – Define the indicators referenced by INDICATOR.
  • FND_LANGUAGES – Provides valid values and descriptions for LANGUAGE and SOURCE_LANG.
  • FND_TABLES / FND_COLUMNS – EBS metadata repository describing this table and its columns.

Because the BSC product is documented as obsolete, integrators should verify object existence in the target database and treat any dependency as legacy.