Search Results bsc_sys_images_map_tl




Overview
Explore in AI Chat

Overview

The BSC_SYS_IMAGES_MAP_TL table resides in the BSC schema (Balanced Scorecard module) and stores translated image map information used by the Oracle EBS Balanced Scorecard application. In Oracle EBS 12.1.1 and 12.2.2, Balanced Scorecard provides strategic performance management by rendering scorecards, strategy maps, and dashboards that incorporate graphical image maps. Each image map associates a source object (for example, a strategy element, scorecard, or perspective) with a stored image, and this table holds the language-specific descriptive layer for those mappings. Because the "_TL" suffix denotes a translation table, it holds one row per language for a given image map definition, allowing the application to display localized image map content to users based on their session language.

The ETRM metadata classifies this object heuristically as "standalone" from a Data Vault modeling perspective, meaning it does not participate in any enforced foreign key relationships. In Data Vault terms, the table functions most naturally as a satellite carrying descriptive, language-dependent attributes keyed to a parent image map definition; absent a documented hub relationship, the standalone classification should be treated as a modeling suggestion rather than a structural constraint.

Key Information Stored

The table contains 11 documented columns. The most functionally significant are:

  • SOURCE_TYPE — Identifies the category of the source object to which the image map applies; part of both the primary key and the unique business key.
  • SOURCE_CODE — The identifier of the specific source object; also part of the primary key and unique index.
  • TYPE — Further qualifies the nature of the image map entry; part of the primary and unique keys.
  • LANGUAGE — The language code for the translated row; part of the primary key and unique index and the discriminator that makes this a translation table.
  • SOURCE_LANG — The base or source language from which the translation derives, following standard EBS _TL conventions.
  • IMAGE_ID — References the actual image content associated with this map entry.
  • Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS "Who" columns capturing row provenance.

The surrogate-style primary key is defined by BSC_SYS_IMAGES_MAP_TL_PK on (SOURCE_TYPE, LANGUAGE, TYPE, SOURCE_CODE). A unique index, BSC_SYS_IMAGES_MAP_TL_U1 on (SOURCE_TYPE, SOURCE_CODE, TYPE, LANGUAGE), serves as the business-key candidate, differing from the primary key only in column ordering.

Common Use Cases and Queries

Typical usage centers on retrieving the localized image map entry for a given source object in the user's language, and on auditing which image maps have translations in which languages.

  • Fetch a specific translated mapping: 
    SELECT image_id, source_lang
FROM   bsc.bsc_sys_images_map_tl
WHERE  source_type = :p_source_type
AND    source_code = :p_source_code
AND    type        = :p_type
AND    language    = userenv('LANG');
  • List all language variants of an image map: 
    SELECT language, image_id
FROM   bsc.bsc_sys_images_map_tl
WHERE  source_type = :p_source_type
AND    source_code = :p_source_code;
  • Detect missing translations by comparing languages present against the set of installed languages.
  • Report on image map inventory by TYPE and SOURCE_TYPE for administrative review.

Because the table is primarily read by the Balanced Scorecard rendering engine, direct DML is uncommon and should generally be performed through supported BSC configuration rather than manual inserts.

Related Objects

Given the standalone classification, no documented foreign keys exist, but the following objects are functionally related:

  • BSC_SYS_IMAGES_MAP_B — the base (non-translated) image map definition table, joined on SOURCE_TYPE, SOURCE_CODE, and TYPE.
  • BSC_SYS_IMAGES_B / BSC_SYS_IMAGES_TL — hold the image content referenced by IMAGE_ID.
  • BSC_SYS_IMAGES_MAP_TL_PK / _U1 — the primary key constraint and unique index enforcing row identity.
  • FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG values against installed EBS languages.
  • BSC Scorecard and Strategy Map UI components — consume these rows to render localized image maps on dashboards.