Results for “xla_line_definitions_tl”

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

Overview

XLA_LINE_DEFINITIONS_TL is the translation (language) table for journal line definitions in Oracle Subledger Accounting (XLA). It stores the language-dependent descriptive attributes — the name and description of each line definition — for every installed language, while the base, language-independent attributes are held in the corresponding transaction table XLA_LINE_DEFINITIONS_B. The object resides in the XLA schema and is classified VALID in Oracle E-Business Suite 12.1.1 and 12.2.2.

A line definition identifies the individual debit and credit lines that Subledger Accounting generates when it creates journal entries for a given accounting event. Because the same line definition is presented to users in multiple languages, the translated text is separated into this table and joined back to the base row through the composite primary key. From a Data Vault modeling perspective, the metadata's heuristic classification is standalone; the table is not modeled as a hub, link, or satellite, since it carries descriptive translations and no foreign-key relationships were mined. This classification is a modeling suggestion only and does not reflect a physical constraint.

Key Information Stored

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

• AMB_CONTEXT_CODE — the accounting methods builder context that scopes the line definition.
• APPLICATION_ID — the subledger application that owns the definition.
• EVENT_CLASS_CODE and EVENT_TYPE_CODE — the accounting event class and event type to which the line definition applies.
• LINE_DEFINITION_OWNER_CODE — identifies the owner of the definition (for example, Oracle versus user-defined).
• LINE_DEFINITION_CODE — the code identifying the journal line definition.
• LANGUAGE — the language for the translated row.
• NAME and DESCRIPTION — the translated, user-facing text of the line definition.
• SOURCE_LANG — the source language of the original definition text.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the application.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• ZD_EDITION_NAME — the edition identifier used by EBS online patching in Release 12.2.

The surrogate primary key is XLA_LINE_DEFINITIONS_TL_PK, defined on AMB_CONTEXT_CODE, APPLICATION_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, LINE_DEFINITION_OWNER_CODE, LINE_DEFINITION_CODE, and LANGUAGE. Two unique indexes act as business-key candidates: XLA_LINE_DEFINITIONS_TL_U1 adds ZD_EDITION_NAME to the primary key columns, while XLA_LINE_DEFINITIONS_TL_U2 substitutes NAME for LINE_DEFINITION_CODE, enforcing uniqueness of the translated name within the same context, application, event, owner, and language.

Common Use Cases and Queries

Typical use cases include reporting the user-visible names of Subledger Accounting line definitions, diagnosing missing translations, and auditing translations after a patch or language installation.

A common pattern joins the translation table to its base table to retrieve the definition text alongside base attributes:

• SELECT b.line_definition_code, t.name, t.description FROM xla_line_definitions_b b, xla_line_definitions_tl t WHERE b.amb_context_code = t.amb_context_code AND b.application_id = t.application_id AND b.event_class_code = t.event_class_code AND b.event_type_code = t.event_type_code AND b.line_definition_owner_code = t.line_definition_owner_code AND b.line_definition_code = t.line_definition_code AND t.language = USERENV('LANG');
• Query by application and event: filter on APPLICATION_ID and EVENT_CLASS_CODE to list all line definitions and their translated names for a specific subledger event.
• Identify missing translations by comparing base rows against translation rows for a given LANGUAGE value.

Because the table is language-keyed, every query should constrain LANGUAGE to avoid returning duplicate rows for the same definition.

Related Objects

• XLA_LINE_DEFINITIONS_B — the base table holding language-independent attributes; joined on the composite key columns (AMB_CONTEXT_CODE, APPLICATION_ID, EVENT_CLASS_CODE, EVENT_TYPE_CODE, LINE_DEFINITION_OWNER_CODE, LINE_DEFINITION_CODE).
• XLA_LINE_DEFINITION_DETAILS — defines the detail lines belonging to each line definition.
• XLA_LINE_DEFINITIONS_VL — the view that combines base and translation rows for user-facing display.
• XLA_ACCOUNTING_METHODS_TL — translated descriptions of the parent accounting method.
• XLA_LINE_DEFINITION_DTLS_TL — translated text for line definition details.
• FND_LANGUAGES — supplies valid LANGUAGE values used in the translated rows.