Search Results bsc_sys_images_map_tl_u1

Overview

BSC.BSC_SYS_IMAGES_MAP_TL is a translation-enabled (TL) table in the Oracle EBS Balanced Scorecard (BSC) product family. It stores the relationship between BSC levels — described in the documentation as system or tab level — and the image files associated with them. The _TL suffix indicates that the table holds language-specific rows, allowing the same logical image mapping to be rendered in multiple installed languages. Its documented role is to map a source object (identified by SOURCE_TYPE and SOURCE_CODE) and a tab view identifier (TYPE) to an IMAGE_ID, with translation semantics managed through LANGUAGE and SOURCE_LANG.

The dependency metadata records that the table does not reference any other database object, and it is referenced only by the APPS synonym BSC_SYS_IMAGES_MAP_TL. From a heuristic Data Vault modeling perspective, this object is classified as standalone. That classification should be treated as a suggestion only: because the table carries descriptive attributes such as IMAGE_ID, SOURCE_LANG, and standard Who columns alongside its composite key, it behaves more like a reference or lookup entity than a true hub, link, or satellite.

Key Information Stored

The table contains eleven documented columns. The most significant are:

• SOURCE_TYPE (NUMBER) — identifies the type of the source object; part of both the primary key and the unique index.
• SOURCE_CODE (NUMBER) — the identifier of the source record; part of both the primary key and the unique index.
• TYPE (NUMBER, length 15) — documented as the tab view id when SOURCE_TYPE equals 1; part of both the primary key and the unique index.
• LANGUAGE (VARCHAR2) — the language code for the row; part of both the primary key and the unique index.
• SOURCE_LANG (VARCHAR2) — the language the text mirrors; if the text has not been translated into LANGUAGE, changes to the source-language row are reflected here as well.
• IMAGE_ID (NUMBER, length 15) — the image identifier assigned to the mapping, and the principal descriptive payload of the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns used for audit and concurrency tracking.

The surrogate primary key is documented as BSC_SYS_IMAGES_MAP_TL_PK over (SOURCE_TYPE, LANGUAGE, TYPE, SOURCE_CODE). The business-key candidate is the unique index BSC_SYS_IMAGES_MAP_TL_U1 over (SOURCE_TYPE, SOURCE_CODE, TYPE, LANGUAGE). Both keys comprise the same four columns in a different order, so BSC_SYS_IMAGES_MAP_TL_U1 is effectively the language-aware business key that the user searched for and is the index most likely to be used to resolve a specific mapping lookup.

Common Use Cases and Queries

The primary functional use is resolving which image file should be displayed for a given BSC level and tab view in a given language. Reporting and diagnostic queries typically filter on the four key columns and return IMAGE_ID. A representative pattern is:

• Look up a mapping: SELECT IMAGE_ID FROM BSC.BSC_SYS_IMAGES_MAP_TL WHERE SOURCE_TYPE = :p_type AND SOURCE_CODE = :p_code AND TYPE = :p_tab AND LANGUAGE = USERENV('LANG');
• Detect untranslated rows: SELECT SOURCE_TYPE, SOURCE_CODE, TYPE, LANGUAGE, SOURCE_LANG FROM BSC.BSC_SYS_IMAGES_MAP_TL WHERE LANGUAGE <> SOURCE_LANG;
• Audit changes: filter on LAST_UPDATE_DATE or LAST_UPDATED_BY to identify recent modifications to image mappings.
• Reconcile images: group by IMAGE_ID to find image files referenced by multiple source/tab combinations.

Because BSC_SYS_IMAGES_MAP_TL_U1 leads with SOURCE_TYPE and SOURCE_CODE, queries that supply those two predicates will use the index most efficiently; queries that supply only IMAGE_ID or only LANGUAGE are less selective and should be avoided in high-volume reporting.

Related Objects

The documented dependency metadata is sparse. The table does not reference any other database object, so no outbound foreign keys are recorded. It is referenced by the APPS synonym BSC_SYS_IMAGES_MAP_TL, which is the standard runtime access path for application code and reports. In practice, join activity occurs on the shared BSC level identifiers:

• APPS.BSC_SYS_IMAGES_MAP_TL — the APPS synonym through which the table is queried at runtime.
• BSC scorecard level and tab definitions — joined on SOURCE_TYPE, SOURCE_CODE, and TYPE, since TYPE represents the tab view id when SOURCE_TYPE = 1.
• The base (non-TL) image mapping object, joined on SOURCE_TYPE, SOURCE_CODE, and TYPE, with LANGUAGE used to select the translated row.
• BSC image/file repository objects referenced indirectly through IMAGE_ID.
• FND language and territory reference data, joined on LANGUAGE and SOURCE_LANG to resolve language names.

Where additional relationships are required, they should be verified against the actual BSC schema in the target instance, as the ETRM dependency extract for this object lists no explicit foreign keys.