Search Results xla_entity_types_tl




Overview
Explore in AI Chat

Overview

The XLA_ENTITY_TYPES_TL table is a core translation table within the Oracle E-Business Suite Subledger Accounting (XLA) module. It stores language-specific, translatable descriptions for Subledger Accounting entities. An entity in XLA represents a business object or transaction source, such as Payables Invoices, Receivables Transactions, or Assets Additions, for which detailed accounting entries are generated. This table enables the multilingual display of entity names within the application interface and reports, supporting global deployments. Its role is critical for ensuring that end-users see descriptive entity information in their preferred language, as defined by the application's language settings.

Key Information Stored

The table's structure is designed to support multilingual data with a key composed of an identifier, a language code, and the application context. The most important columns include:

  • APPLICATION_ID: Identifies the Oracle EBS product (e.g., Payables, Receivables) to which the entity belongs.
  • ENTITY_CODE: The internal code for the specific transaction source or business object.
  • LANGUAGE: The standard Oracle language code (e.g., 'US', 'F') for the translated text.
  • NAME: The translated, user-facing name of the entity (e.g., "Supplier Invoices" in English, "Factures Fournisseur" in French).
  • DESCRIPTION: A longer description of the entity type in the specified language.

The table maintains two unique keys: the primary key (XLA_ENTITY_TYPES_TL_PK) on APPLICATION_ID, ENTITY_CODE, and LANGUAGE, and a unique key (XLA_ENTITY_TYPES_TL_UK) on APPLICATION_ID, NAME, and LANGUAGE to prevent duplicate translated names within an application.

Common Use Cases and Queries

A primary use case is retrieving the user-friendly name of an entity for a given language to display in custom reports or interfaces. For instance, a report listing journal line sources would join to this table to show the entity name instead of its internal code. Another common scenario is during application setup or debugging, where a consultant needs to list all available entities for a specific application in the session language.

Sample query to fetch translated entity names for the Payables application (APPLICATION_ID = 200) in the current session language:

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

Related Objects

This translation table has a direct relationship with its base table, which stores the non-translatable attributes. The primary relationship is:

  • XLA_ENTITY_TYPES_B: The base table containing the core definition of entity types. The tables are joined on the columns APPLICATION_ID and ENTITY_CODE. The XLA_ENTITY_TYPES_TL table provides the translated NAME and DESCRIPTION for the records defined in the base table.

This relationship is fundamental, as the translation table is dependent on the existence of a corresponding record in the base table. The primary key XLA_ENTITY_TYPES_TL_PK (APPLICATION_ID, ENTITY_CODE, LANGUAGE) typically has a foreign key constraint referencing the primary key of XLA_ENTITY_TYPES_B.