Search Results bis_levels_tl




Overview
Explore in AI Chat

Overview

BIS_LEVELS_TL is the translation (TL) table for level definitions within the BIS (Applications BIS) product module of Oracle E-Business Suite. In the Oracle EBS multilingual data model, a base table stores language-independent attributes while its corresponding _TL table stores the language-dependent, translatable text attributes — principally NAME and DESCRIPTION — keyed by both the entity identifier and a LANGUAGE code. BIS_LEVELS_TL therefore holds the translated names and descriptions of levels that are defined in the base levels table and referenced across the BIS schema.

In the documented physical schema for ETRM 12.2.2, the table is owned by the BIS schema and contains 11 columns. The metadata's heuristic Data Vault classification, mined from the foreign-key structure, identifies this object as standalone. As a modeling suggestion, this classification reflects that the table's only documented foreign key (LEVEL_ID → MSD_LEVELS) points outward to a parent entity, and no other table is shown referencing it. In Data Vault terms this pattern is most consistent with a satellite carrying descriptive, language-qualified attributes attached to the level hub; because the mined structure is minimal, the standalone label should be treated as an advisory hint rather than a definitive classification.

Key Information Stored

The table's 11 documented columns separate the entity identifier, the language discriminator, the translatable text, and standard Oracle WHO audit columns.

  • LEVEL_ID — Surrogate identifier for the level. It is the join key back to the parent entity and is documented as a foreign key to MSD_LEVELS.
  • LANGUAGE — Language code identifying which translation row applies. Together with LEVEL_ID it forms the primary business uniqueness constraint.
  • NAME — The translated name or label of the level in the row's language. This is the attribute most often surfaced in reports and LOVs.
  • DESCRIPTION — The translated long description of the level.
  • TRANSLATED — Flag indicating whether the NAME and DESCRIPTION values in this row have been translated from the source language.
  • SOURCE_LANG — The language from which the current row's text was translated, or the source language of the base record.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO audit columns recording insert and update provenance.

Two unique indexes are documented as business-key candidates. BIS_LEVELS_TL_U1 covers (LEVEL_ID, LANGUAGE), enforcing one translation per level per language. BIS_LEVELS_TL_U2 covers (LANGUAGE, NAME, LEVEL_ID), supporting lookup and uniqueness of level names within a language. Note that the column inventory does not document a separate surrogate primary key column beyond LEVEL_ID, which functions as the entity identifier in combination with LANGUAGE.

Common Use Cases and Queries

The most frequent requirement is retrieving the level name in a specific language for display. A typical pattern joins the translation table to the base level table and filters on LANGUAGE:

  • Language-specific lookup: SELECT l.level_id, t.name, t.description FROM bis_levels l, bis_levels_tl t WHERE l.level_id = t.level_id AND t.language = :p_lang.
  • LOV population: query BIS_LEVELS_TL filtered by LANGUAGE and ordered by NAME to populate a level list of values.
  • Translation completeness reporting: SELECT level_id, language, translated FROM bis_levels_tl WHERE translated = 'N' identifies rows still requiring translation.
  • Multi-language reporting: concatenate or pivot NAME across LANGUAGE values using the (LEVEL_ID, LANGUAGE) uniqueness to guarantee one row per level per language.
  • Join to parent entity: join BIS_LEVELS_TL.LEVEL_ID to MSD_LEVELS to obtain level attributes alongside their translated text.

Because the base translatable text resides here rather than in the base table, reports that omit a LANGUAGE filter risk returning multiple rows per level. Always constrain on LANGUAGE or aggregate explicitly.

Related Objects

  • MSD_LEVELS — Referenced through the documented foreign key BIS_LEVELS_TL.LEVEL_ID → MSD_LEVELS; the parent level definition carrying language-independent attributes.
  • BIS_LEVELS — The base (non-TL) level table conventionally paired with this translation table, joined on LEVEL_ID.
  • BIS_LEVELS_TL_U1 and BIS_LEVELS_TL_U2 — The unique indexes enforcing business-key uniqueness on (LEVEL_ID, LANGUAGE) and (LANGUAGE, NAME, LEVEL_ID) respectively.
  • BIS_LOOKUPS / BIS_LOOKUPS_TL — Related BIS reference-data translation tables that follow the same TL design pattern and are frequently queried alongside level data.
  • FND_LANGUAGES — The language reference table supplying valid LANGUAGE codes and installed-language context for joins and filters.

Together these objects support consistent, multilingual presentation of BIS level definitions throughout the E-Business Suite.