Search Results xla_sources_tl_u2

Overview

XLA.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. The XLA schema underpins the Subledger Accounting Engine, which transforms raw subledger transactions into accounting entries. Sources represent the discrete data elements (for example, distribution amounts, supplier identifiers, or segment values) that feed the accounting derivation rules and journal line definitions. The _TL suffix indicates that this object stores language-specific, translatable descriptive text rather than the base transactional definition, which resides in the base XLA_SOURCES table. Each row supplies a translated NAME and DESCRIPTION for a given source code in a specific language.

The object carries a warning that it is for Oracle Internal Use Only, meaning supported access is expected through standard Oracle Applications programs rather than custom SQL wherever possible. Its tablespace is APPS_TS_TX_DATA with PCT Free 10. The heuristic Data Vault classification mined from the foreign key structure is standalone. Interpreted as a modeling suggestion, this indicates the table has no outgoing foreign keys to other hubs or links; it functions effectively as a descriptive satellite supplying multilingual attribute text that logically belongs to the source definition. It does not act as a hub or a link in its own right.

Key Information Stored

Of the thirteen documented columns, the following are the most operationally significant:

• APPLICATION_ID – Internal numeric identifier of the owning application; participates in both unique indexes and the primary key.
• SOURCE_TYPE_CODE – Classifies the source type; part of the primary key and unique keys.
• SOURCE_CODE – The source definition code; part of the primary key and of unique index U1.
• LANGUAGE – Standard language code identifying the translation locale; part of the primary key.
• NAME – User-facing translated source name (80 characters); the discriminator in unique index U2.
• DESCRIPTION – Long translated source description (240 characters).
• SOURCE_LANG – Standard source language code indicating the original language of the text.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO columns capturing audit lineage, with foreign keys to FND_USER.USER_ID and FND_LOGINS.LOGIN_ID.

The documented primary key is XLA_SOURCES_TL_PK (APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, LANGUAGE). Two unique indexes serve as business-key candidates: XLA_SOURCES_TL_U1 (APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, LANGUAGE, ZD_EDITION_NAME) and XLA_SOURCES_TL_U2 (APPLICATION_ID, SOURCE_TYPE_CODE, NAME, LANGUAGE, ZD_EDITION_NAME). The U2 index is the physical constraint referenced in the user search term "xla_sources_tl_u2"; in 12.2.2 it additionally includes ZD_EDITION_NAME. The surrogate key itself is the composite primary key, distinguished from these business-key candidates by the absence of NAME and ZD_EDITION_NAME from U1's equivalent column set.

Common Use Cases and Queries

The table is most often joined to XLA_SOURCES or XLA_SOURCE to retrieve human-readable names for source codes when building accounting-rule reports, source-to-journal-line traceability listings, or subledger setup documentation. A representative query filters on a specific language to return translated names:

SELECT APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, LANGUAGE, NAME, DESCRIPTION, SOURCE_LANG FROM XLA.XLA_SOURCES_TL WHERE LANGUAGE = :p_language AND APPLICATION_ID = :p_app_id;

Typical reporting scenarios include auditing which sources are defined per application, confirming translation coverage across installed languages, and validating that business-key uniqueness (the U2 constraint) holds after data migration. Because of the internal-use warning, read-only joins are preferable, and any DML should be routed through supported Oracle subledger setup or concurrent programs.

Related Objects

• XLA.XLA_SOURCES – The base (non-translated) source definition table; joined on APPLICATION_ID, SOURCE_TYPE_CODE, and SOURCE_CODE.
• APPS.XLA_SOURCE – The documented dependent object that references XLA_SOURCES_TL, forming the primary parent relationship in the dependency metadata.
• FND_USER – Referenced via CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS – Referenced via LAST_UPDATE_LOGIN.
• FND_APPLICATION – Associates APPLICATION_ID with an application short name for readable reporting.
• FND_LANGUAGES – Provides validation and descriptions for the LANGUAGE and SOURCE_LANG codes.

These relationships position XLA_SOURCES_TL as a dependent translation satellite within the XLA source-definition cluster, supporting the broader Subledger Accounting Engine configuration.