Results for “xla_entity_types_tl”

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

Overview

XLA_ENTITY_TYPES_TL is the translation (TL) table for the Subledger Accounting entity types setup in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the XLA schema and stores the language-dependent attributes of each entity type registered with the Subledger Accounting Engine, most notably the descriptive NAME and DESCRIPTION shown to users. Entity types identify the kind of subledger transaction being accounted — for example an invoice, a payment, a receipt, or a journal entry source — and are referenced throughout the accounting program, journal line, and drill-down infrastructure.

The base (non-translated) definition lives in XLA_ENTITY_TYPES_B, while XLA_ENTITY_TYPES_TL carries the multilingual text for each supported language. Any query joining the two must key on APPLICATION_ID and ENTITY_CODE plus LANGUAGE.

From a Data Vault modeling perspective, the mined FK structure classifies this table as standalone. In practice this object is best treated as a descriptive satellite attached to the entity type hub represented by XLA_ENTITY_TYPES_B, since it holds attributes keyed to the parent entity and varies by language rather than expressing an independent business relationship.

Key Information Stored

• APPLICATION_ID — Identifies the owning application (subledger) that registered the entity type; part of both the primary key and the alternate unique keys.
• ENTITY_CODE — The internal code (short name) of the entity type; the primary business identifier for the entity.
• LANGUAGE — The NLS language of the translated row; part of the primary key.
• NAME — The user-visible entity type name translated into the given language. Constitutes the second business-key candidate via XLA_ENTITY_TYPES_TL_UK.
• DESCRIPTION — The translated long description of the entity type.
• SOURCE_LANG — The source language from which the row was derived, used by the translation framework.
• CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard "WHO" audit columns capturing the last modification.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (Edition-Based Redefinition) in 12.2.x.

The surrogate primary key is XLA_ENTITY_TYPES_TL_PK, defined on (APPLICATION_ID, ENTITY_CODE, LANGUAGE). Two business-key candidates are documented: the _UK unique index — the object the user searched for — on (APPLICATION_ID, NAME, LANGUAGE), which enforces that a translated name is unique within an application and language; and the edition-aware _U1/_U2 indexes that add ZD_EDITION_NAME in 12.2.2.

Common Use Cases and Queries

Typical uses include: building LOVs and reports that display entity type names instead of codes; auditing which subledger entity types are enabled per application; and developing drill-down or reconciliation reporting joining journal headers to entity types.

Because the table is translated, queries must restrict LANGUAGE to avoid duplicate rows. A common pattern is a join to the base table filtered to the session language:

SELECT b.entity_code, t.name, t.description
FROM xla_entity_types_b b, xla_entity_types_tl t
WHERE b.application_id = t.application_id
AND b.entity_code = t.entity_code
AND t.language = USERENV('LANG');

The same logic can be applied using a join to FND_LANGUAGES or the :LANG parameter in a report. Rather than hard-coding the session language, many reports select rows where LANGUAGE equals the base language or the current NLS setting.

Related Objects

• XLA_ENTITY_TYPES_B — Base table; join on APPLICATION_ID and ENTITY_CODE, using the TL row for language-specific text.
• XLA_ENTITY_TYPES_TL_UK — Unique index on (APPLICATION_ID, NAME, LANGUAGE), enforcing unique translated names.
• XLA_ENTITY_TYPES_TL_PK — Primary key on (APPLICATION_ID, ENTITY_CODE, LANGUAGE).
• XLA_ENTITY_TYPES_TL_U1 / _U2 — Edition-aware unique indexes supporting Online Patching in 12.2.2.
• FND_APPLICATION — Resolves APPLICATION_ID to the owning subledger application.
• FND_LANGUAGES — Validates LANGUAGE and supports translation lookups.

These objects together allow consistent, language-aware reporting on Subledger Accounting entity types.