Search Results comp_disp_name




Overview

BSC.BSC_SYS_DIM_LEVELS_TL is a translation (TL) table in the Oracle E-Business Suite Balanced Scorecard (BSC) schema, which underpins the Enterprise Performance Foundation and Enterprise Planning and Budgeting dimension model. The table stores the language-specific descriptive attributes of dimension levels — the named hierarchical positions such as "Year," "Quarter," or "Product Category" that organize dimensions within BSC analytic and scorecard structures. As a "_TL" companion to the base table BSC.BSC_SYS_DIM_LEVELS_B, it follows the standard EBS multilingual pattern: structurally identical rows are held per installed language, keyed by the combination of the entity identifier and the LANGUAGE code, with SOURCE_LANG tracking the originating language row from which translations are derived.

The ETRM metadata classifies this object heuristically as satellite-leaning within a Data Vault model. This is an appropriate modeling suggestion: BSC_SYS_DIM_LEVELS_TL holds descriptive, language-dependent attributes that hang off the dimension level business key defined in the base table, while the foreign key to BSC_SYS_DIM_LEVELS_B anchors it to the parent entity. In Oracle EBS 12.1.1 and 12.2.2, storage resides in the APPS_TS_TX_DATA tablespace with a unique index (BSC_SYS_DIM_LEVELS_TL_U1) in APPS_TS_TX_IDX; the object is a synonym exposed to the APPS schema.

Key Information Stored

The table carries seven documented columns. The most important include:

  • DIM_LEVEL_ID — Numeric dimension level identifier; together with LANGUAGE it forms the composite primary key (BSC_SYS_DIM_LEVELS_TL_PK). This is a foreign key to BSC_SYS_DIM_LEVELS_B.DIM_LEVEL_ID, not a generated surrogate.
  • LANGUAGE — The language code for the row, forming the second half of the composite primary key and the unique index BSC_SYS_DIM_LEVELS_TL_U1 (DIM_LEVEL_ID, LANGUAGE). This pair constitutes the business-key candidate for the translation row.
  • SOURCE_LANG — The language the text mirrors; if the target language (LANGUAGE) is not yet translated, changes to the source-language row propagate here.
  • NAME — The translated dimension level name (up to 255 characters); the primary user-facing label.
  • HELP — Extended 1024-character help/description text for the level.
  • TOTAL_DISP_NAME — A 45-character caption used for the TOTAL item when the level is displayed in reports.
  • COMP_DISP_NAME — A 45-character caption for the COMPARISON item. This is the column most relevant to the search term "comp_disp_name."

Common Use Cases and Queries

Typical usage centers on multilingual reporting, level label resolution, and scorecard presentation for a specific locale. The COMP_DISP_NAME and TOTAL_DISP_NAME columns are commonly consumed by BI Publisher reports and OBIEE/EPM dashboards to render aggregated ("Total") and comparative ("Comparison") captions in the user's language without invoking translations in the front-end application.

A representative query retrieving level labels for a given identifier:

  • SELECT dl.DIM_LEVEL_ID, dl.LANGUAGE, dl.NAME, dl.TOTAL_DISP_NAME, dl.COMP_DISP_NAME FROM BSC.BSC_SYS_DIM_LEVELS_TL dl WHERE dl.DIM_LEVEL_ID = :dim_level_id AND dl.LANGUAGE = USERENV('LANG');

Reporting patterns frequently join the translation table to its base table by DIM_LEVEL_ID and LANGUAGE to expose both structural and translated attributes, and filter on SOURCE_LANG to identify rows still awaiting localization.

Related Objects

  • BSC.BSC_SYS_DIM_LEVELS_B — The base (non-translated) dimension level table; joined on DIM_LEVEL_ID and provides the parent business entity referenced by this table's foreign key.
  • BSC.BSC_SYS_DIM_LEVELS_TL_U1 — The unique index on (DIM_LEVEL_ID, LANGUAGE) enforcing translation uniqueness.
  • BSC.BSC_SYS_DIM_LEVELS_TL_PK — The primary key constraint defining row identity.
  • APPS.BSC_SYS_DIM_LEVELS_TL — The APPS-schema synonym through which application code and reports access the table.
  • BSC_SYS_DIM_LEVELS_TL (ETRM view/reference) — The documented query layer exposing the seven columns for ad hoc extraction.

These objects together form the dimension-level metadata layer leveraged by Balanced Scorecard, EPB, and Enterprise Performance Foundation analytical configurations.