Search Results xla_acct_attributes_tl




Overview
Explore in AI Chat

Overview

The XLA_ACCT_ATTRIBUTES_TL table resides in the XLA schema, the repository for Oracle Subledger Accounting (SLA) in Oracle E-Business Suite 12.1.1 and 12.2.2. It is the translation (_TL) companion of the base XLA_ACCT_ATTRIBUTES_B table and stores language-specific, displayable text for accounting attributes. Accounting attributes in SLA are predefined descriptive elements that carry the values needed to complete the accounting process, such as transaction identifiers, distribution references, and source-specific context used by journal line definition rules. Because users view these attributes in multiple installed languages, the translatable text (principally the attribute name) is held separately in this table, keyed by accounting attribute code and language.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone, with no inbound or outbound foreign key relationships mined. It functions most naturally as a reference or lookup satellite: the attribute code acts as the hub-like business key, and the translated NAME plus audit columns form the descriptive satellite payload. The absence of FK evidence means referential integrity is enforced at the application layer rather than through database constraints.

Key Information Stored

The table contains ten documented columns. The composite primary key XLA_ACCT_ATTRIBUTES_TL_PK is defined on ACCOUNTING_ATTRIBUTE_CODE and LANGUAGE, establishing the unique identity of each translated row. The two unique indexes, XLA_ACCT_ATTRIBUTES_TL_U1 and XLA_ACCT_ATTRIBUTES_TL_U2, extend this identity to include ZD_EDITION_NAME and, in the case of U2, the translated NAME, confirming that a given attribute name must be unique within a language and edition. The most significant columns are:

  • ACCOUNTING_ATTRIBUTE_CODE — the business identifier of the accounting attribute; part of the primary key and the join column to the base table.
  • LANGUAGE — the installed language code (for example, US or DE) for which the translation applies; the second component of the primary key.
  • NAME — the translated, user-facing name of the accounting attribute, the principal payload of this table.
  • SOURCE_LANG — the language of the source row from which the translation was derived, supporting the standard MLS translation model.
  • ZD_EDITION_NAME — the edition indicator used in the 12.2 Edition-Based Redefinition (EBR) architecture, participating in both unique indexes.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard audit columns recording who created and last modified each translation row.

Common Use Cases and Queries

Typical usage resolves attribute codes to their translated descriptions for reporting and for validating journal line definition setups. A common pattern joins the translation table to the base table or filters by language:

  • Retrieve translated attribute names: SELECT accounting_attribute_code, name FROM xla_acct_attributes_tl WHERE language = USERENV('LANG');
  • Join to the base definition to present code and description together, joining on ACCOUNTING_ATTRIBUTE_CODE and LANGUAGE.
  • Diagnose missing translations by comparing rows in the _B and _TL tables for a given language.
  • Support EBR-aware queries by filtering on ZD_EDITION_NAME where run against a 12.2.2 environment.

Related Objects