Results for “event_mapping_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The XLA_EVENT_MAPPINGS_TL table resides in the XLA schema and forms part of the Subledger Accounting (XLA) product within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store translated information related to event mappings. In the XLA architecture, event mappings define how a subledger event type and event class are associated with an accounting method, thereby controlling which journal line types, account derivation rules, and application accounting definitions apply when a transaction is accounted. Because Subledger Accounting supports multilingual deployments, the descriptive attributes of these event mappings require language-specific storage, and XLA_EVENT_MAPPINGS_TL provides exactly this translated layer.

The table follows the standard EBS convention of a base table (XLA_EVENT_MAPPINGS_B) paired with a translation table (the "_TL" suffix), where the translation table holds the user-facing text in each installed language while the base table holds language-independent attributes. The heuristic Data Vault classification mined from the foreign key structure is "standalone," meaning the object carries no hard foreign key dependencies to other entities. From a modeling perspective, this suggests the table is best treated as a descriptive satellite attached to the event mapping entity, rather than as a hub or link in its own right.

Key Information Stored

The table is documented with 10 columns. The most significant are described below.

• EVENT_MAPPING_ID — Surrogate identifier of the parent event mapping. Together with LANGUAGE this forms the primary key XLA_EVENT_MAPPINGS_TL_PK.
• LANGUAGE — The language code identifying the translation row. Combined with EVENT_MAPPING_ID, it uniquely identifies a translated record for a given mapping.
• COLUMN_TITLE — The translated text label associated with the event mapping, representing the language-specific descriptive content that distinguishes this table from its base counterpart.
• SOURCE_LANG — The source language from which the translation was derived, following standard EBS MLS conventions.
• ZD_EDITION_NAME — The edition identifier used by the EBS online patching (adop) architecture introduced in 12.2. This column participates in the unique index XLA_EVENT_MAPPINGS_TL_U1 (EVENT_MAPPING_ID, LANGUAGE, ZD_EDITION_NAME), which serves as the business-key candidate.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard who-column audit information.

The distinction between the surrogate primary key (EVENT_MAPPING_ID, LANGUAGE) and the business-key candidate unique index (EVENT_MAPPING_ID, LANGUAGE, ZD_EDITION_NAME) is important: the PK enforces uniqueness per language, while the unique index additionally scopes rows by patch edition in 12.2 environments.

Common Use Cases and Queries

Typical usage centers on reporting and troubleshooting translated event mapping labels. A common query retrieves the translated title for a specific mapping and language:

• SELECT event_mapping_id, language, column_title FROM xla_event_mappings_tl WHERE event_mapping_id = :id AND language = USERENV('LANG');
• Joining to the base table to obtain both language-independent and translated attributes: SELECT b.*, t.column_title FROM xla_event_mappings_b b, xla_event_mappings_tl t WHERE b.event_mapping_id = t.event_mapping_id AND t.language = USERENV('LANG');

Reporting use cases include auditing which event mappings have translations available for each installed language, identifying missing translations, and validating label consistency across a multi-language implementation. During upgrades or patching, the ZD_EDITION_NAME column is relevant for diagnosing edition-scoped data.

Related Objects

• XLA_EVENT_MAPPINGS_B — Base table joined on EVENT_MAPPING_ID, holding language-independent event mapping attributes.
• XLA_EVENT_MAPPINGS_VL — The MLS view that presents translated and base data transparently, typically joining on EVENT_MAPPING_ID and LANGUAGE.
• XLA_EVENT_TYPES_B / _TL — Defines the event type referenced by event mappings; related through the application and event type context.
• XLA_EVENT_CLASSES_B / _TL — Defines event classes associated with event mappings.
• XLA_ACCOUNTING_METHODS_B / _TL — Accounting methods that event mappings associate to an event.
• FND_LANGUAGES — Reference table validating LANGUAGE values.