Search Results bsc_kpi_tree_nodes_tl_u1

Overview

BSC.BSC_KPI_TREE_NODES_TL is the translation (language) table that accompanies BSC_KPI_TREE_NODES_B in the Oracle EBS Balanced Scorecard (BSC) module. It stores the language-dependent descriptive attributes of simulation tree nodes organized by indicator — specifically the display Name, contextual Help text, and the Y-Axis Title used when the node is rendered as a chart. In Oracle EBS 12.1.1 and 12.2.2, tables ending in _TL implement multi-language support through the standard MLS (Multi-Lingual Support) pattern, where one row exists per installed language for each base entity row.

From a Data Vault modeling perspective, the mined relationship structure classifies this object as satellite-leaning. It does not introduce new business entities or relationships of its own; instead it hangs off the base table BSC_KPI_TREE_NODES_B and carries descriptive, history-relevant attributes keyed to the parent entity plus a language discriminator. This is the classic shape of a satellite table — a descriptive adjunct to a hub or link, dependent on its parent for identity.

Key Information Stored

The table holds seven documented columns. The composite primary key, BSC_KPI_TREE_NODES_TL_PK, is defined on (INDICATOR, LANGUAGE, NODE_ID), and the unique index BSC_KPI_TREE_NODES_TL_U1 — the index referenced in the user's search — enforces uniqueness on the same business-key triple (INDICATOR, NODE_ID, LANGUAGE). Because both the PK and U1 cover the same columns, the surrogate-versus-business-key distinction collapses here: the identifier is a natural composite key rather than a generated surrogate.

• INDICATOR (NUMBER) — Indicator code; part of the primary key and foreign key to BSC_KPI_TREE_NODES_B.
• NODE_ID (NUMBER) — Tree node identifier; the second identifying component.
• LANGUAGE (VARCHAR2) — Language code for the row, completing the key and driving MLS selection.
• SOURCE_LANG (VARCHAR2) — The language from which the text mirrors; if a translation is not yet provided, edits to the source-language row propagate here.
• NAME (VARCHAR2, 75) — Translated tree node name.
• HELP (VARCHAR2, 240) — Translated tree node help text.
• Y_AXIS_TITLE (VARCHAR2, 90) — Y-axis title for chart rendering, nominally capped at 30 characters.

Common Use Cases and Queries

The principal use case is locale-aware reporting of Balanced Scorecard simulation trees. Application logic joining the base table to this translation table filters on the session language and falls back to SOURCE_LANG where a translation is empty. A canonical extraction pattern is:

• Reporting node labels and axis titles: SELECT INDICATOR, NODE_ID, NAME, Y_AXIS_TITLE FROM BSC.BSC_KPI_TREE_NODES_TL WHERE LANGUAGE = :p_lang;
• Detecting untranslated nodes: compare NAME across LANGUAGE rows for a given INDICATOR/NODE_ID pair to identify gaps.
• Auditing translation drift by joining to BSC_KPI_TREE_NODES_B on INDICATOR (and NODE_ID) to reconcile source and translated values.
• Chart configuration queries that retrieve Y_AXIS_TITLE for dashboard rendering.

Because the table is an MLS satellite, DML should normally be performed through the BSC application or its concurrent/translation APIs rather than direct INSERT/UPDATE, to preserve SOURCE_LANG consistency.

Related Objects

The most significant dependencies follow from the documented foreign key and MLS pairing:

• BSC.BSC_KPI_TREE_NODES_B — the base table; joined on INDICATOR (and NODE_ID). Referenced by this table's foreign key.
• BSC.BSC_KPI_TREE_NODES_TL_U1 — the unique index on (INDICATOR, NODE_ID, LANGUAGE) that backs the business key and the search term queried.
• BSC.KPI_TREE_NODES_VL (view) — the usual MLS view exposing the base and translated columns together for application and reporting access.
• BSC.BSC_KPI_TREE_NODES_T — the interface/staging table typically used to load or update translation rows during setup and patching.
• BSC.BSC_KPIS_B / BSC_KPI_TREE_NODES_B — parent indicator and tree-node tables that supply INDICATOR and NODE_ID values consumed here.

All objects reside in the APPS_TS_TX_DATA tablespace (indexes in APPS_TS_TX_IDX) and are owned by the BSC schema in EBS 12.1.1 and 12.2.2.