Search Results xla_event_class_grps_tl_pk

Overview

XLA_EVENT_CLASS_GRPS_TL is the translation (language-dependent) table for event class groups within the XLA schema, the Subledger Accounting product of Oracle E-Business Suite. Event class groups provide a grouping mechanism for event classes used by the Subledger Accounting Engine, and this table stores the translated display name and description associated with each group in each installed language. Because the base table XLA_EVENT_CLASS_GRPS holds the language-independent attributes, the _TL suffix indicates that XLA_EVENT_CLASS_GRPS_TL is the multi-language companion table following the standard Oracle EBS MLS (Multi-Language Support) pattern. Its role is therefore presentational rather than transactional: it allows the Create Accounting, accounting method, and subledger setup forms and reports to render event class group names and descriptions in the session language of the user.

From a data-modeling perspective, the metadata classifies this object heuristically as standalone. In Data Vault terms, it behaves most like a satellite attached to the event class group hub/keyed by APPLICATION_ID and EVENT_CLASS_GROUP_CODE plus LANGUAGE. Because it carries descriptive, non-key attributes that hang off the core event class group identity, the satellite interpretation is a reasonable modeling suggestion, though no formal FK relationships are documented.

Key Information Stored

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

• APPLICATION_ID — Identifies the owning application (for example, the subledger application) to which the event class group belongs. Part of both the primary key and the unique keys.
• EVENT_CLASS_GROUP_CODE — The short, internal code that identifies the event class group. Part of the primary key and the business-key unique index.
• LANGUAGE — The NLS language code for this translated row. Part of every key.
• NAME — The translated user-facing name of the event class group. Included in the unique index XLA_EVENT_CLASS_GRPS_TL_U2, so a name must be unique within an application and language.
• DESCRIPTION — The translated free-text description of the event class group.
• SOURCE_LANG — The source language from which the row was derived; supports MLS source-language tracking.
• ZD_EDITION_NAME — The editioning column used in the EBS 12.2 online patching (edition-based redefinition) architecture; part of both unique indexes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update context.

Regarding key structure: the surrogate primary key is XLA_EVENT_CLASS_GRPS_TL_PK on (APPLICATION_ID, EVENT_CLASS_GROUP_CODE, LANGUAGE). Two documented unique indexes serve as business-key candidates: XLA_EVENT_CLASS_GRPS_TL_U1 on (APPLICATION_ID, EVENT_CLASS_GROUP_CODE, LANGUAGE, ZD_EDITION_NAME) and XLA_EVENT_CLASS_GRPS_TL_U2 on (APPLICATION_ID, LANGUAGE, NAME, ZD_EDITION_NAME). Note the distinction: the surrogate key enforces uniqueness of the group plus language, while U2 enforces uniqueness of the translated NAME within the application and language.

Common Use Cases and Queries

This table is typically joined to the base table on APPLICATION_ID and EVENT_CLASS_GROUP_CODE, filtered by LANGUAGE, to return a translated name for a given session language. A representative query is:

• SELECT t.name, t.description FROM xla_event_class_grps_tl t WHERE t.application_id = :app_id AND t.event_class_group_code = :code AND t.language = USERENV('LANG');
• Reporting on configured event class groups by name when reviewing Subledger Accounting setup.
• Verifying that translated names exist for all required languages by comparing rows per LANGUAGE against the base table.
• Detecting MLS translation gaps, where a base row exists but no matching _TL row is present for a given language.

Because the table is small (one row per event class group per language), queries are inexpensive, but they should always be constrained by APPLICATION_ID and LANGUAGE to avoid ambiguous duplicate names across applications.

Related Objects

The metadata documents no foreign keys, but the natural relationships and EBS patterns imply the following significant related objects:

• XLA_EVENT_CLASS_GRPS (base table) — Join on APPLICATION_ID and EVENT_CLASS_GROUP_CODE; holds the language-independent definition.
• XLA_EVENT_CLASSES — Event classes grouped by the event class group, joined via the group code referencing the event class group context.
• FND_APPLICATION — Join on APPLICATION_ID to resolve the owning application name.
• FND_LANGUAGES — Join on LANGUAGE to obtain the language display name.
• XLA_EVENT_CLASS_GRP_B — Where present in earlier 11i-style structures, the bilingual base table variant.

These objects collectively support the event class grouping configuration used throughout the Subledger Accounting setup and accounting rule creation process.