Results for “bsc_responsibility_tl”

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

Overview

BSC_RESPONSIBILITY_TL is the translated (language-specific) table for BSC responsibilities within the Oracle E-Business Suite Balanced Scorecard module (BSC). As the "_TL" suffix indicates, it stores the language-dependent, translatable attributes of a responsibility record so that the same logical responsibility can present different display text across installed languages. Every functional record in the base table BSC_RESPONSIBILITY is accompanied by one or more rows here, one per language in which the responsibility is defined, keeping all descriptive text segregated from language-independent data.

The table resides in the BSC schema, is marked VALID in the ETRM 12.1.1 data model, and carries 12 documented columns. Under the heuristic Data Vault classification mined from its foreign-key structure, this object is satellite-leaning. In Data Vault modeling terms, BSC_RESPONSIBILITY functions as the parent (hub-like) record, while BSC_RESPONSIBILITY_TL acts as the satellite that hangs off it, holding descriptive and contextual attributes keyed back to the parent. This classification is a modeling suggestion rather than a rigid architectural rule.

Key Information Stored

The table is keyed by a three-column composite: APPLICATION_ID, LANGUAGE, and RESPONSIBILITY_ID (constraint BSC_RESPONSIBILITY_TL_PK). The most significant columns are:

• APPLICATION_ID — identifies the owning application context; part of both the primary key and the unique indexes.
• RESPONSIBILITY_ID — the surrogate identifier linking each translated row back to its parent record in BSC_RESPONSIBILITY.
• LANGUAGE — the language code; distinguishes the translated row for one language from all others.
• RESPONSIBILITY_NAME — the translated display name; a business-key candidate via index BSC_RESPONSIBILITY_TL_U2 (APPLICATION_ID, RESPONSIBILITY_NAME, LANGUAGE).
• DESCRIPTION — the translated descriptive text for the responsibility.
• TRANSLATED — flag indicating whether the row's text has been translated.
• SOURCE_LANG — the source language from which the translation was derived.
• CREATED_BY, CREATION_DATE — audit columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification.

Note that the surrogate primary key columns (APPLICATION_ID, LANGUAGE, RESPONSIBILITY_ID) are distinct from the business-key candidates exposed through the unique indexes BSC_RESPONSIBILITY_TL_U1 and BSC_RESPONSIBILITY_TL_U2, which additionally surface RESPONSIBILITY_NAME as a natural identifier.

Common Use Cases and Queries

Typical scenarios include reporting responsibility names in a user's session language, resolving translated labels for a given responsibility, and auditing translation completeness. A common pattern joins the translated row to its parent and restricts output by language:

• Lookup by parent: SELECT t.RESPONSIBILITY_NAME, t.DESCRIPTION FROM BSC.BSC_RESPONSIBILITY_TL t WHERE t.RESPONSIBILITY_ID = :id AND t.LANGUAGE = USERENV('LANG');
• Detect untranslated rows: SELECT RESPONSIBILITY_ID FROM BSC.BSC_RESPONSIBILITY_TL WHERE TRANSLATED = 'N';
• Cross-language comparison: join rows for the same RESPONSIBILITY_ID across different LANGUAGE values to compare names.
• Report generation: pivot translated text per language for a responsibility catalogue.

Because the table is narrow and indexed on APPLICATION_ID, RESPONSIBILITY_ID, and LANGUAGE, these queries resolve efficiently against the primary key and unique indexes.

Related Objects

The principal relationship is with the parent table BSC_RESPONSIBILITY, joined on RESPONSIBILITY_ID (foreign key BSC_RESPONSIBILITY_TL.RESPONSIBILITY_ID → BSC_RESPONSIBILITY). Other significant objects include:

• BSC_RESPONSIBILITY — the base, language-independent responsibility definition; the hub in the satellite relationship.
• BSC_RESPONSIBILITY_TL_PK / _U1 / _U2 — the primary key and unique indexes enforcing row identity and business keys.
• FND_LANGUAGES — the standard reference for LANGUAGE code validation.
• FND_APPLICATION — reference for APPLICATION_ID context.

Together these objects let applications resolve a responsibility's translated name and description at runtime from its base identifier.