Search Results xla_acct_line_types_tl




Overview
Explore in AI Chat

Overview

XLA_ACCT_LINE_TYPES_TL is a translation table in the XLA (Subledger Accounting) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-specific, translated attributes of accounting line type definitions, which drive how individual journal entry lines are classified, generated, and reported within Subledger Accounting. Accounting line types represent the semantic role a line plays in a subledger transaction — for example, a receivable line, a tax line, or a distribution line — and are used throughout the Create Accounting process to determine account derivation, rounding, and posting behavior.

The table is a companion to the base XLA_ACCT_LINE_TYPES_B entity table, holding only translated descriptive text (NAME, DESCRIPTION) keyed by LANGUAGE, following Oracle's standard _B (base) / _TL (translated) multilingual pattern. Per the heuristic Data Vault classification provided in the metadata, this object is modeled as standalone; that is, it has no mined foreign-key dependencies and would typically be treated as an independent satellite of descriptive/translated attributes rather than as a hub or link.

Key Information Stored

The table contains 16 documented columns. The most significant are:

The documented surrogate/primary key is XLA_ACCT_LINE_TYPES_TL_PK (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, AMB_CONTEXT_CODE, ACCOUNTING_LINE_CODE, ACCOUNTING_LINE_TYPE_CODE, LANGUAGE). Two unique indexes act as business-key candidates: XLA_ACCT_LINE_TYPES_TL_U1 (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, AMB_CONTEXT_CODE, ACCOUNTING_LINE_TYPE_CODE, ACCOUNTING_LINE_CODE, LANGUAGE, ZD_EDITION_NAME) and XLA_ACCT_LINE_TYPES_TL_U2 (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, AMB_CONTEXT_CODE, ACCOUNTING_LINE_TYPE_CODE, NAME, LANGUAGE, ZD_EDITION_NAME). U2 additionally enforces uniqueness of the NAME per language, confirming that display names are controlled per context.

Common Use Cases and Queries

The primary use case is multilingual reporting and lookup resolution — returning the correct NAME and DESCRIPTION for a given accounting line type in the user's session language. A typical join reconciles the translated names with the base definitions:

  • Retrieve names in a specific language: SELECT APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, ACCOUNTING_LINE_TYPE_CODE, NAME, DESCRIPTION FROM XLA_ACCT_LINE_TYPES_TL WHERE LANGUAGE = 'US'.
  • Validate uniqueness: query by ACCOUNTING_LINE_TYPE_CODE and LANGUAGE to confirm a single translated name exists.
  • Join to the base table XLA_ACCT_LINE_TYPES_B on the shared context columns (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, ACCOUNTING_LINE_CODE, ACCOUNTING_LINE_TYPE_CODE) and LANGUAGE to combine translated text with base attributes.
  • Reporting on which accounting line types are defined for an application/event class for configuration review and documentation of the accounting method setup.

Related Objects

The most significant related objects, based on the shared key structure and standard XLA relationships, include:

  • XLA_ACCT_LINE_TYPES_B — the base (untranslated) accounting line type definitions, joined on the shared context key columns plus LANGUAGE.
  • XLA_ACCT_LINE_TYPES_VL and similar _VL views — expose base and translated columns together for form and reporting use.
  • XLA_ACCOUNTING_LINES — references accounting line codes and context that these line types describe.
  • XLA_AMB_CONTEXTS — defines the AMB_CONTEXT_CODE scoping.
  • XLA_EVENT_CLASSES — provides EVENT_CLASS_CODE context.
  • FND_APPLICATION — resolves APPLICATION_ID to the owning application.
  • FND_LANGUAGES — validates the LANGUAGE column.

Note that the documented relationship classification is standalone, so no formal foreign keys are mined; joins are driven by the shared context columns rather than enforced FK constraints.