Search Results xla_event_class_grps_tl_u2

Overview

XLA.XLA_EVENT_CLASS_GRPS_TL is the translation (TL) table for the Subledger Accounting (XLA) Event Class Group entity in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the language-dependent descriptive attributes—NAME and DESCRIPTION—for event class groups defined in the base table, XLA.XLA_EVENT_CLASS_GRPS_B. An event class group is a logical container that groups related event classes so that Subledger Accounting, Create Accounting, and accounting program setups can be configured and processed at a coarser granularity than individual event classes. The base table holds the language-independent key and administrative columns; this table holds the corresponding short name and description displayed in the Accounting Methods Builder (AMB) and related setup pages.

The object resides in the XLA schema, is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and carries a status of VALID. It is flagged as Oracle Internal Use Only, meaning direct DML should not be performed; changes should flow through standard Oracle Applications programs such as the AMB setup forms and the underlying XLA setup APIs. Based on the FK/PK relationship data, the heuristic Data Vault classification is standalone; from a dimensional modeling perspective, this object is best treated as a descriptive satellite attached to the event class group hub, with language acting as a multi-active discriminator.

Key Information Stored

The physical table comprises twelve documented columns. The most significant are:

• APPLICATION_ID — Internal identifier of the application owning the event class group; part of every unique index and the primary key.
• EVENT_CLASS_GROUP_CODE — The language-independent business code for the event class group; joins back to the base table.
• LANGUAGE — Standard language code; distinguishes the translated rows for each group.
• NAME — The displayed event group name (80 characters), the key user-facing translated attribute.
• DESCRIPTION — The event group description (240 characters).
• SOURCE_LANG — The source language from which the translation was derived.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema supporting Online Patching (adopeditioning).

The surrogate/business primary key is XLA_EVENT_CLASS_GRPS_TL_PK (APPLICATION_ID, EVENT_CLASS_GROUP_CODE, LANGUAGE). Two unique indexes act as business-key candidates: XLA_EVENT_CLASS_GRPS_TL_U1 (APPLICATION_ID, EVENT_CLASS_GROUP_CODE, LANGUAGE, ZD_EDITION_NAME) — the value the user searched for — and XLA_EVENT_CLASS_GRPS_TL_U2 (APPLICATION_ID, LANGUAGE, NAME, ZD_EDITION_NAME), which enforces that no two groups share the same name within a language.

Common Use Cases and Queries

Typical use cases include enumerating event class groups for a given language, joining translated names to base setup rows for reporting, and diagnosing uniqueness errors raised against the U2 index when a duplicate name is defined in the same language.

• Retrieve all event class groups in English:
  SELECT APPLICATION_ID, EVENT_CLASS_GROUP_CODE, NAME, DESCRIPTION
FROM XLA.XLA_EVENT_CLASS_GRPS_TL
WHERE LANGUAGE = USERENV('LANG');
• Join base and translation rows:
  SELECT b.EVENT_CLASS_GROUP_CODE, t.NAME, t.DESCRIPTION
FROM XLA.XLA_EVENT_CLASS_GRPS_B b, XLA.XLA_EVENT_CLASS_GRPS_TL t
WHERE b.APPLICATION_ID = t.APPLICATION_ID
AND b.EVENT_CLASS_GROUP_CODE = t.EVENT_CLASS_GROUP_CODE
AND t.LANGUAGE = USERENV('LANG');
• Diagnose a U2 duplicate-name violation by grouping on APPLICATION_ID, LANGUAGE, NAME.
• Confirm which languages a specific group is translated into by filtering on EVENT_CLASS_GROUP_CODE and APPLICATION_ID.

Related Objects

The table participates in the following principal relationships:

• XLA.XLA_EVENT_CLASS_GRPS_B — the base (non-translated) table; joined on APPLICATION_ID and EVENT_CLASS_GROUP_CODE.
• XLA.XLA_EVENT_CLASSES_B and XLA.XLA_EVENT_CLASSES_TL — event classes assigned to each group.
• XLA_EVENT_TYPES_B / XLA_EVENT_TYPES_TL — event types associated with the event classes within a group.
• XLA_ACCOUNTING_METHODS_B / XLA_ACCOUNTING_METHODS_TL — accounting methods configured against event class groups.
• FND_APPLICATION / FND_APPLICATION_TL — application name resolution via APPLICATION_ID.
• FND_USER and FND_LOGINS — resolving CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Because the object is documented as standalone, no direct foreign keys are declared against it; all joins are performed logically through the composite business key of application, code, and language.