Results for “xla_sources_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_SOURCES_TL is the translation (TL) table for the Subledger Accounting (XLA) source definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. In Oracle EBS, "sources" identify the individual data elements that Subledger Accounting uses when it builds accounting entries from subledger transactions — for example, the distribution amount, the natural account, or the balancing segment. Each source is registered at the application and source-type level, and its user-facing name and description are captured in language-specific rows within XLA_SOURCES_TL. The table therefore provides the multilingual presentation layer for source metadata, while the untranslated definition itself is held in the base XLA_SOURCES table.

From a data-modeling perspective, the metadata classifies this object heuristically as standalone, meaning it carries its own identity and does not sit inside a dependent hub-link-satellite chain in the documented FK structure. If a Data Vault model were constructed around it, the natural suggestion would be to treat the translation row as a descriptive satellite keyed by the combination of application, source type, source code, and language, referencing a source definition hub — but the supplied metadata does not assert a physical FK, so this is offered as a modeling recommendation rather than a documented fact.

Key Information Stored

The table contains 13 documented columns in the 12.2.2 physical schema. The most significant are:

• APPLICATION_ID — identifies the owning application or product (for example, Payables or Receivables) to which the source belongs.
• SOURCE_TYPE_CODE — classifies the kind of source, distinguishing, for instance, system-level and user-defined sources.
• SOURCE_CODE — the internal code that uniquely names the source within its application and type.
• LANGUAGE — the language of the translated name and description in that row.
• NAME — the translated display name of the source, shown to users on Subledger Accounting setup and inquiry screens.
• DESCRIPTION — the translated textual explanation of the source.
• SOURCE_LANG — the language in which the source was originally defined, used by the translation framework.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS who-columns for auditing.
• ZD_EDITION_NAME — the edition identifier used in the 12.2.2 editioning model.

The surrogate/primary key is XLA_SOURCES_TL_PK on (APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, LANGUAGE). Two documented unique indexes act as business-key candidates: XLA_SOURCES_TL_U1 on (APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, LANGUAGE, ZD_EDITION_NAME) and XLA_SOURCES_TL_U2 on (APPLICATION_ID, SOURCE_TYPE_CODE, NAME, LANGUAGE, ZD_EDITION_NAME), the latter enforcing that a translated name is unique within its application, type, and language.

Common Use Cases and Queries

Typical uses include extracting translated source names for reporting or migration, verifying that a source has been translated into the required languages, and joining source metadata to accounting rule definitions. A common pattern retrieves the localized name for a known source:

• SELECT name, description FROM xla_sources_tl WHERE application_id = :app_id AND source_type_code = :type_code AND source_code = :source_code AND language = USERENV('LANG');
• Join to the untranslated base: SELECT b.source_code, t.name FROM xla_sources b, xla_sources_tl t WHERE b.application_id = t.application_id AND b.source_type_code = t.source_type_code AND b.source_code = t.source_code AND t.language = 'US';
• Detect missing translations: SELECT s.application_id, s.source_code FROM xla_sources s WHERE NOT EXISTS (SELECT 1 FROM xla_sources_tl t WHERE t.application_id = s.application_id AND t.source_code = s.source_code AND t.source_type_code = s.source_type_code AND t.language = 'US');

Related Objects

The following objects are most commonly associated with XLA_SOURCES_TL, joined on the shared key columns:

• XLA_SOURCES — the base source definition table; join on APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE.
• XLA_SOURCES_TL_PK / XLA_SOURCES_TL_U1 / XLA_SOURCES_TL_U2 — the primary and unique indexes enforcing translation identity.
• FND_APPLICATION — resolves APPLICATION_ID to an application name and short name.
• FND_LANGUAGES — validates the LANGUAGE and SOURCE_LANG values against installed languages.
• XLA_ACCOUNTING_RULES and related XLA rule tables — consume sources when constructing accounting entries.
• XLA_LOOKUPS / FND_LOOKUPS — supply the meaning of SOURCE_TYPE_CODE and other coded values.

These relationships make XLA_SOURCES_TL the definitive reference for presenting Subledger Accounting sources in the user's chosen language.