Results for “bsc_kpi_analysis_options_tl”

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

Overview

BSC_KPI_ANALYSIS_OPTIONS_TL is the translation (language-dependent) child table of the Balanced Scorecard KPI Analysis Options entity in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It stores multilingual text—display name and help text—for each analysis option defined at the base (untranslated) level in BSC_KPI_ANALYSIS_OPTIONS_B. The "_TL" suffix follows the standard Oracle EBS naming convention for translatable tables, in which each row is uniquely identified by the base entity key combined with a LANGUAGE code. Within BSC, analysis options drive how key performance indicators are grouped, parented, and rolled up in the Balanced Scorecard analysis hierarchy.

The metadata identifies product BSC - Balanced Scorecard and flags the module as Obsolete. The ETRM record further notes "Not implemented in this database," indicating that this specific table is not present in the referenced environment and may exist only in older or customized installations. Organizations running current 12.1.1 or 12.2.2 instances should not assume it is deployed simply because the definition exists in the data model.

Under the heuristic Data Vault classification supplied with the metadata, this object leans toward a satellite: it carries descriptive, language-scoped attributes (NAME, HELP) keyed back to a parent base table, rather than acting as an independent hub or a pure relationship link.

Key Information Stored

The table contains nine documented columns. Their roles are as follows:

• ANALYSIS_GROUP_ID, INDICATOR, OPTION_ID, PARENT_OPTION_ID, GRANDPARENT_OPTION_ID, LANGUAGE — These six columns together form the primary key, BSC_KPI_ANALYSIS_OPTIONS_TL_PK. They identify the specific option within its analysis group and three-level hierarchy, qualified by language.
• OPTION_ID — The foreign key to BSC_KPI_ANALYSIS_OPTIONS_B; it is the surrogate link from the translated row back to the base entity.
• PARENT_OPTION_ID and GRANDPARENT_OPTION_ID — Define the option's position in the hierarchical analysis tree, supporting roll-up and drill-down behavior.
• INDICATOR — Associates the option with a specific KPI indicator.
• ANALYSIS_GROUP_ID — Groups options for analytical presentation.
• LANGUAGE and SOURCE_LANG — LANGUAGE is the translation language; SOURCE_LANG records the language of origin from which the row was translated.
• NAME and HELP — The translated display name and help text presented to users in the selected language.

The unique index BSC_KPI_ANALYSIS_OPTIONS_TL_U1 (INDICATOR, ANALYSIS_GROUP_ID, OPTION_ID, PARENT_OPTION_ID, GRANDPARENT_OPTION_ID, LANGUAGE) is the documented business-key candidate, confirming that this combination uniquely identifies a logical record independent of row-level surrogates.

Common Use Cases and Queries

Typical usage is to join the translated table to its base table and filter by language for reporting or user-interface display:

• Retrieve localized option names for a given language: SELECT t.OPTION_ID, t.NAME, t.HELP FROM BSC_KPI_ANALYSIS_OPTIONS_TL t WHERE t.LANGUAGE = 'US'.
• Report option hierarchies with translations: join BSC_KPI_ANALYSIS_OPTIONS_TL to BSC_KPI_ANALYSIS_OPTIONS_B on OPTION_ID and select NAME, PARENT_OPTION_ID, and GRANDPARENT_OPTION_ID to reconstruct the analysis tree.
• Audit multilingual coverage: compare SOURCE_LANG against LANGUAGE to detect untranslated or stale rows.
• Resolve indicator-level reporting: filter by INDICATOR and ANALYSIS_GROUP_ID to produce KPI analysis listings per language.

Related Objects

• BSC_KPI_ANALYSIS_OPTIONS_B — The base table; joined via OPTION_ID (and the composite business key). This is the primary parent and the only foreign-key relationship documented.
• BSC_KPI_ANALYSIS_OPTIONS_TL_PK — Primary key constraint enforcing row uniqueness.
• BSC_KPI_ANALYSIS_OPTIONS_TL_U1 — Unique index serving as the business-key candidate.
• Associated BSC indicator and analysis-group definition tables referenced conceptually by INDICATOR and ANALYSIS_GROUP_ID, though no explicit FK is documented in this metadata.