Results for “xla_event_mappings_b”

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

Overview

The XLA_EVENT_MAPPINGS_B table is a core configuration object within the XLA (Subledger Accounting) schema of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. Its purpose is to store the information required to build reports based on the data available on the base document (the source transaction passed from a subledger such as Payables, Receivables, or Assets). Each row represents a single column name to be printed on those reports, meaning the table acts as a definition store for report layout and content at the event-mapping level. The object is owned by the XLA schema and is classified as VALID.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests that XLA_EVENT_MAPPINGS_B is best treated as an independent satellite or reference structure rather than a hub or link; it holds descriptive, configuration-oriented attributes that do not themselves carry outbound referential dependencies to other tables.

Key Information Stored

The table contains 12 documented columns. The most significant are summarized below.

• EVENT_MAPPING_ID — The surrogate primary key, enforced by XLA_EVENT_MAPPINGS_B_PK. It uniquely identifies each mapping row.
• APPLICATION_ID — Identifies the application (subledger) that owns the event mapping.
• ENTITY_CODE — The transaction entity for which the mapping applies.
• EVENT_CLASS_CODE — The event class within the entity, narrowing the mapping to a specific business event category.
• USER_SEQUENCE — Controls the display or processing order of the mapped columns on the report.
• COLUMN_NAME — The name of the base-document column to be printed.
• ZD_EDITION_NAME — The edition identifier used by the EBS 12.2 online patching (adop) architecture; it participates in all unique constraints.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard WHO columns tracking record history.

Three business-key candidates are documented for the 12.2.2 physical schema: U1 on (EVENT_MAPPING_ID, ZD_EDITION_NAME), U2 on (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, USER_SEQUENCE, ZD_EDITION_NAME), and U3 on (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, COLUMN_NAME, ZD_EDITION_NAME). The U2 and U3 constraints confirm that sequencing and column naming must be unique per entity/event class within an edition.

Common Use Cases and Queries

Typical uses include: building custom subledger reports that reproduce the base-document layout, auditing which columns are configured for a given event class, and validating configuration integrity across editions. A representative query retrieving the ordered report columns for a specific entity and event class is:

• SELECT column_name, user_sequence FROM xla.xla_event_mappings_b WHERE application_id = :app_id AND entity_code = :entity AND event_class_code = :class AND zd_edition_name = 'SET1' ORDER BY user_sequence;
• Joining to XLA_EVENT_MAPPINGS_TL on EVENT_MAPPING_ID to obtain translated report titles and descriptions.
• Comparing rows across ZD_EDITION_NAME values to detect configuration drift introduced during online patching.

Related Objects

Because the metadata describes the object as standalone, no outbound foreign keys are documented. The following are the most significant related objects by convention and business-key overlap.

• XLA_EVENT_MAPPINGS_TL — Translation table, joined on EVENT_MAPPING_ID.
• XLA_EVENT_MAPPINGS_VL — The view that joins the _B and _TL tables for user-facing queries.
• XLA_EVENT_CLASSES_B — Defines the EVENT_CLASS_CODE referenced here.
• XLA_ENTITY_CODE_B (or equivalent entity definition) — Supplies the ENTITY_CODE domain.
• XLA_EVENTS — The accounting events that the base documents flow through.
• Subledger applications (AP, AR, FA) supply APPLICATION_ID values.

Together these objects form the reporting-configuration layer of Subledger Accounting.