Search Results xla_mapping_sets_tl_u1




Overview
Explore in AI Chat

Overview

XLA.XLA_MAPPING_SETS_TL is the translation (TL) table for the Oracle Subledger Accounting (XLA) Mapping Set entity within the E-Business Suite 12.1.1 and 12.2.2 data model. It stores the language-dependent descriptive attributes of a Mapping Set — its translated name and description — keyed by a language code, in addition to the language-independent identifying columns (MAPPING_SET_CODE and AMB_CONTEXT_CODE). Mapping Sets are configuration artifacts used by the Accounting Methods Builder (AMB) to derive ledger accounting combinations from source transaction attributes; the TL table provides the multilingual, presentation-facing representation of each mapping set definition, while XLA_MAPPING_SETS_B (the base table) holds the operational, non-translatable attributes.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. Under a Data Vault modelling convention this suggests the object does not participate as a hub, link, or satellite through explicit foreign-key constraints to other XLA entities; it should be treated as a descriptive, language-scoped reference table whose business keys are composed of the context, mapping set code, and language.

Key Information Stored

The most significant columns are:

  • MAPPING_SET_CODE (VARCHAR2(30), mandatory) — the mapping set code; part of the primary key and of both unique indexes.
  • AMB_CONTEXT_CODE (VARCHAR2(30)) — the Accounting Methods Builder context under which the mapping set is defined.
  • LANGUAGE — the standard language code identifying the translation.
  • NAME (VARCHAR2(80)) — the translated mapping set name; a business-key candidate via XLA_MAPPING_SETS_TL_U2.
  • DESCRIPTION (VARCHAR2(240)) — the translated mapping set description.
  • SOURCE_LANG — the standard source language code from which the row was derived.
  • CREATION_DATE, CREATED_BY — standard WHO columns capturing creation audit.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns capturing mutation audit.
  • ZD_EDITION_NAME — the edition/partition discriminator included in the 12.2.2 unique indexes.

The surrogate primary key is XLA_MAPPING_SETS_TL_PK (MAPPING_SET_CODE, LANGUAGE). Two unique indexes act as business-key candidates: XLA_MAPPING_SETS_TL_U1 (AMB_CONTEXT_CODE, MAPPING_SET_CODE, LANGUAGE, ZD_EDITION_NAME) — the queried target of the search term xla_mapping_sets_tl_u1 — and XLA_MAPPING_SETS_TL_U2 (AMB_CONTEXT_CODE, NAME, LANGUAGE, ZD_EDITION_NAME). The table is stored in APPS_TS_TX_DATA with its indexes in APPS_TS_TX_IDX.

Common Use Cases and Queries

Typical usage is read-only reporting of translated mapping set metadata for a given AMB context and session language. Analysts join the TL table to its base counterpart to retrieve both operational and descriptive attributes. A representative query is:

  • SELECT m.mapping_set_code, t.name, t.description FROM xla.xla_mapping_sets_tl t WHERE t.amb_context_code = :ctx AND t.language = userenv('LANG');
  • Multilingual reporting: filter on LANGUAGE to retrieve name/description in the desired locale.
  • Configuration auditing: reconcile NAME uniqueness against XLA_MAPPING_SETS_TL_U2 to detect duplicate translated names within a context.
  • Data extraction / migration: select all translatable rows by AMB_CONTEXT_CODE and MAPPING_SET_CODE for loading into staging tables.

Because Oracle classifies this object as internal use only, direct DML is discouraged; queries should be limited to read access and Oracle-supported APIs.

Related Objects

The base table XLA_MAPPING_SETS_B shares the business key (MAPPING_SET_CODE) and holds the non-translatable columns; TL and B are joined on MAPPING_SET_CODE and AMB_CONTEXT_CODE. The ETRM dependency section indicates XLA_MAPPING_SETS_TL does not reference other database objects and is referenced by the APPUSER/indexes and by the application XLA_MAPPING package, which services Mapping Set configuration. Related XLA entities include XLA_MAPPING_SETS_B, XLA_MAPPING_SET_VALUES, the AMB context tables (XLA_AMB_CONTEXTS), and FND_LANGUAGES (referenced via LANGUAGE/SOURCE_LANG). Standard language-independent joins should always carry the AMB_CONTEXT_CODE and LANGUAGE predicates to satisfy the U1/U2 index paths.