Search Results xla_event_classes_tl




Overview
Explore in AI Chat

Overview

XLA_EVENT_CLASSES_TL is the translation table for event classes within the Oracle Subledger Accounting (XLA) module. It stores language-specific descriptive attributes — primarily the translated NAME and DESCRIPTION — for the event classes defined in the base table XLA_EVENT_CLASSES. An event class represents a business activity category (for example, an invoice, a payment, or a receipt) that Subledger Accounting uses to drive accounting rule evaluation and journal entry creation. Because Oracle E-Business Suite supports multiple installed languages, the "_TL" suffix designates that rows in this table carry a LANGUAGE discriminator and provide the human-readable text that appears in Subledger Accounting setup forms, concurrent program parameters, and reporting outputs in the user's session language.

The ETRM metadata classifies this object, via heuristic FK-structure mining, as standalone in Data Vault terms. That is a modeling suggestion rather than a physical constraint: the table is a descriptive/translation satellite-like object that hangs off the base event-class definition rather than acting as a hub or an associative link between unrelated business entities. It carries no outbound foreign key relationships of its own within the documented schema. Its natural attachment point is the parent key (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE), which it shares with the base table.

Key Information Stored

The documented physical schema contains 13 columns. The most important are:

  • APPLICATION_ID — identifies the owning application of the event class; part of the primary key.
  • ENTITY_CODE — the subledger entity (for example, a specific transaction type grouping) to which the event class belongs; part of the primary key.
  • EVENT_CLASS_CODE — the internal code of the event class; part of the primary key and the stable identifier used in joins and setup.
  • LANGUAGE — the NLS language code of the translated row; part of the primary key and the SOURCE_LANG relationship.
  • NAME — the translated display name of the event class.
  • DESCRIPTION — the translated long description.
  • SOURCE_LANG — the language of the source (usually the base) row from which translations derive.
  • ZD_EDITION_NAME — the editioning column supporting Online Patching in EBS 12.2.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN support standard WHO audit tracking.

The surrogate primary key is XLA_EVENT_CLASSES_TL_PK (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, LANGUAGE). Two unique indexes act as business-key candidates: XLA_EVENT_CLASSES_TL_U1 adds ZD_EDITION_NAME to the PK columns, and XLA_EVENT_CLASSES_TL_U2 enforces uniqueness on the translated NAME alongside the key columns and edition. Note the documented UK variant constrains NAME rather than EVENT_CLASS_CODE, ensuring the display name is unique per language in 12.2.

Common Use Cases and Queries

Typical uses include Subledger Accounting setup validation, multilingual reporting, and diagnosis of missing or incorrect event-class labels. A frequent pattern joins the translation table to the base table on the shared key, filtering by the session language:

  • Retrieve localized names: SELECT EVENT_CLASS_CODE, NAME FROM XLA_EVENT_CLASSES_TL WHERE LANGUAGE = USERENV('LANG') ORDER BY NAME.
  • Find missing translations by comparing installed languages against existing rows for a given EVENT_CLASS_CODE.
  • Report all event classes with their translated names for a specific application and entity, joining XLA_EVENT_CLASSES on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE.
  • Audit changes to translated descriptions using the WHO columns for compliance or SOX reporting.

Related Objects

  • XLA_EVENT_CLASSES — the base (untranslated) table; join on APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE.
  • XLA_EVENTS — references event classes to record accounting-relevant activities.
  • XLA_EVENT_TYPES — event types are scoped within an event class.
  • XLA_ACCOUNTING_RULES — accounting rules are defined per event class.
  • XLA_LEDGER_ACCRUAL_OPTIONS — accrual settings tied to event classes.
  • FND_APPLICATION_TL — resolves the APPLICATION_ID to a translated application name.
  • FND_LANGUAGES — validates LANGUAGE codes used in the translation rows.