Search Results xla_event_classes_tl_u2

Overview

XLA.XLA_EVENT_CLASSES_TL is the translation (TL) table for event class definitions in the Oracle E-Business Suite Subledger Accounting (XLA) module. Event classes represent the logical business events — such as invoice creation, payment, or adjustment — that a subledger application can generate against an accounting entity. This table stores the language-dependent attributes of those event classes, principally the display name and description, keyed by language so that the same event class can be presented in multiple installed languages.

Because the table holds only descriptive attributes associated with the base event class definition, the metadata's heuristic Data Vault classification is standalone. In Data Vault modeling terms this object is best treated as a satellite attached to the underlying event class hub rather than as an independent hub or link; it carries no foreign key relationships of its own and exists solely to qualify the parent entity by language.

The table resides in the APPS_TS_TX_DATA tablespace and is documented as valid at 12.1.1 and 12.2.2. The warning accompanying the object — Oracle Internal Use Only — indicates that it should be accessed through standard Oracle Applications programs and supported views rather than directly.

Key Information Stored

The primary key is defined as XLA_EVENT_CLASSES_TL_PK over (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, LANGUAGE). The surrogate-level columns and the language qualifier together identify a single translated row:

• APPLICATION_ID — internal identifier of the owning application, part of the composite primary key.
• ENTITY_CODE — the accounting entity (for example, a transaction type grouping) that the event class belongs to.
• EVENT_CLASS_CODE — the internal code for the event class itself.
• LANGUAGE — the language code for which the NAME and DESCRIPTION values are supplied.
• NAME — the user-facing event class name in the given language.
• DESCRIPTION — the translated description of the event class (up to 240 characters).
• SOURCE_LANG — the original language of the translation source.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns recording who created and last modified each row.
• ZD_EDITION_NAME — editioning column used by the EBS online patching architecture (12.2.x), included in both unique indexes.

Two business-key candidates are documented as unique indexes. XLA_EVENT_CLASSES_TL_U1 covers (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, LANGUAGE, ZD_EDITION_NAME) and enforces that a given event class has at most one translation per language. XLA_EVENT_CLASSES_TL_U2 covers (APPLICATION_ID, ENTITY_CODE, NAME, LANGUAGE, ZD_EDITION_NAME), preventing duplicate names within the same entity and language.

Common Use Cases and Queries

Typical reporting and configuration queries retrieve the English (or session-language) name of event classes for a given application and entity, often joined to the base event class table and to the application's registered entity information. A representative pattern is:

• Listing all event classes for an entity: SELECT event_class_code, name FROM xla.xla_event_classes_tl WHERE application_id = :app AND entity_code = :entity AND language = USERENV('LANG');
• Reporting localization coverage: counting how many languages each event_class_code has been translated into, using GROUP BY on EVENT_CLASS_CODE.
• Validation queries that verify uniqueness of names by language, mirroring the U2 index definition.
• Constructing display prompts in custom subledger accounting reports where the standard translated views are insufficient.

Because translation tables are frequently queried through the corresponding _V or _VL views, direct access should be reserved for diagnostic and reconciliation purposes.

Related Objects

The most significant related objects may be summarized as follows:

• XLA_EVENT_CLASSES_B — the base (B) counterpart holding language-independent event class attributes; joins on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE.
• XLA_EVENT_CLASSES_VL / XLA_EVENT_CLASSES_V — translated views that union the _B and _TL tables and are the supported access path.
• XLA_ENTITY_CLASSES_B — defines the accounting entities and their event class associations.
• XLA_EVENTS — subledger events generated against event classes, referencing them by application, entity, and event class code.
• FND_APPLICATION — the application registry supplying the APPLICATION_ID reference.
• FND_LANGUAGES / FND_USER / FND_LOGINS — provide the LANGUAGE and standard WHO column lookups.

Consultation of these objects through their supported views is recommended for all production reporting and integration work.