Results for “bsc_kpi_shell_cmds_tl”

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

Overview

BSC_KPI_SHELL_CMDS_TL is a translation table within the Oracle E-Business Suite Balanced Scorecard (BSC) module, identified in the ETRM metadata as belonging to the obsolete Balanced Scorecard product family. Its documented purpose is to "link command information," and it functions as the language-dependent child of the shell command definitions associated with Balanced Scorecard KPIs. The _TL suffix follows the standard Oracle Applications convention: the base (non-translated) definition is stored in a companion table, while this object holds the multilingual attributes (specifically NAME and COMMAND) keyed by LANGUAGE.

In Oracle EBS 12.1.1, the table is owned by the BSC schema and comprises six documented columns. In 12.2.2 the object remains part of the legacy BSC schema, though the module itself is obsolete and superseded by later Hyperion-based scorecard functionality. Under the heuristic Data Vault classification derived from its foreign-key structure, this table is satellite-leaning: it carries descriptive, language-variant attributes that hang off the shared key defined by INDICATOR and SHELL_CMD_ID, rather than acting as an independent hub or a pure relationship link.

Key Information Stored

The table stores translated command definitions tied to a KPI. Its principal columns are:

• INDICATOR — identifies the Balanced Scorecard KPI to which the shell command belongs; a foreign key to BSC_KPIS_B and part of the composite primary key.
• SHELL_CMD_ID — the shell command identifier, the second component of the primary key, distinguishing multiple commands attached to the same indicator.
• LANGUAGE — the installation language code (US, D, ZHS, etc.) that determines the translated row returned for a given session.
• SOURCE_LANG — the language from which the translated values were derived, used by the translation-maintenance utilities.
• NAME — the display name of the shell command for the given language.
• COMMAND — the executable or script text invoked by the scorecard engine for the KPI.

The surrogate composite primary key is BSC_KPI_SHELL_CMDS_TL_PK over (INDICATOR, SHELL_CMD_ID), with a unique business-key index BSC_KPI_SHELL_CMDS_TL_U1 over (INDICATOR, SHELL_CMD_ID, LANGUAGE). The unique index is the true natural key: it guarantees exactly one translated NAME/COMMAND row per command per language, and should always be supplied in multilingual joins to avoid duplicate-row multiplication.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve extracting the command text and display name for a KPI, usually restricted to the runtime language.

• Retrieve commands for a KPI: SELECT indicator, shell_cmd_id, name, command FROM bsc_kpi_shell_cmds_tl WHERE indicator = :p_indicator AND language = USERENV('LANG');
• Detect missing translations: compare counts in the base table against this table grouped by LANGUAGE to identify languages lacking a COMMAND row.
• Audit command content: search COMMAND for shell operators or file paths to inventory executable hooks registered against KPIs.
• Cross-language reconciliation: join on the unique index columns (INDICATOR, SHELL_CMD_ID) and pivot by LANGUAGE to compare translations, using SOURCE_LANG to trace derived rows.

All queries should be qualified by LANGUAGE; omitting it returns every installed language and inflates result sets.

Related Objects

The following objects participate in the documented foreign-key relationships:

• BSC_KPIS_B — parent KPI definition table; joined via BSC_KPIS_B.INDICATOR = BSC_KPI_SHELL_CMDS_TL.INDICATOR.
• BSC_KPI_SHELL_CMDS_USER — user-level command assignments; joined via the composite (INDICATOR, SHELL_CMD_ID) reference back to this table.
• BSC_KPI_SHELL_CMDS_B — the base-language shell command definition table (inferred companion to this _TL object).
• BSC_KPI_INDICATORS / BSC_KPIS_B-related views — KPI reporting layer that exposes translated names.
• BSC scorecard administrative concurrent programs and the translation upload utilities, which maintain rows keyed by LANGUAGE and SOURCE_LANG.

Because the module is obsolete and the table is documented as "not implemented" in the reference database, it may be absent or empty in many instances. Confirm existence via ALL_TABLES before building dependencies against it.