Search Results ax_event_mappings




Overview
Explore in AI Chat

Overview

AX_EVENT_MAPPINGS is a reference table within the AX – Global Accounting Engine product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the mappings of primary key columns belonging to the base event tables used by the Global Accounting Engine's translation schemes. In the AX architecture, translation schemes define how subledger or feeder system events are transformed into accounting entries that flow into the general ledger. Because the source events reside in heterogeneous base tables, AX requires a metadata layer that identifies, for each translation scheme, which column or columns constitute the primary key of the underlying event table. AX_EVENT_MAPPINGS serves precisely this purpose: it binds a translation scheme to the set of columns that uniquely identify a row in its base event table.

From a dimensional modeling perspective, the heuristic Data Vault classification for this object is satellite-leaning. It holds descriptive attributes that qualify the relationship between a translation scheme and its event table, attached to the natural key formed by set of books, application, and scheme. Modelers should treat this as a suggestion only; the table is best understood as configuration metadata rather than a transactional fact or hub.

Key Information Stored

The table contains ten documented columns. The most consequential are described below.

  • SET_OF_BOOKS_ID — Identifies the ledger (set of books) to which the translation scheme belongs. This is part of the composite primary key and is the column through which AX_EVENT_MAPPINGS joins to AX_TRANS_SCHEMES.
  • APPLICATION_ID — The application owning the base event table (for example, the subledger application identifier). It scopes the mapping to a specific feeder application.
  • TRANSLATION_SCHEME — The translation scheme name or identifier for which the primary key column mappings are defined.
  • PRIMARY_KEY_COLUMN — The name of the column in the base event table that participates in the primary key. A scheme with a composite key produces multiple rows, one per key column.
  • EVENT_FIELD — The event field associated with the mapping, tying the key column to the AX event structure used during translation.
  • Standard audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — record who created and last modified each row and from which login session.

The surrogate primary key is AX_EVENT_MAPPINGS_PK, composed of SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, and PRIMARY_KEY_COLUMN. The unique index AX_EVENT_MAPPINGS_U1 covers the same four columns and is therefore the business-key candidate: it enforces that a given key column is mapped at most once per scheme, application, and ledger.

Common Use Cases and Queries

Typical usage centers on diagnosing translation scheme behavior and validating configuration. Support analysts list the key columns defined for a particular scheme:

SELECT set_of_books_id, application_id, translation_scheme, primary_key_column, event_field FROM ax.ax_event_mappings WHERE set_of_books_id = :ledger AND translation_scheme = :scheme;

A second pattern identifies schemes that map composite keys, useful when reconciling event volumes between a feeder table and AX:

SELECT translation_scheme, COUNT(*) key_col_count FROM ax.ax_event_mappings GROUP BY translation_scheme HAVING COUNT(*) > 1;

Because the table carries full audit columns, change history reporting is straightforward, and joins back to AX_TRANS_SCHEMES establish which schemes are properly defined against a ledger.

Related Objects

  • AX_TRANS_SCHEMES — The referenced parent table. The foreign key maps AX_EVENT_MAPPINGS.SET_OF_BOOKS_ID, APPLICATION_ID, and TRANSLATION_SCHEME to the corresponding scheme definition.
  • AX_EVENT_MAPPINGS_PK — Primary key constraint enforcing row uniqueness across ledger, application, scheme, and key column.
  • AX_EVENT_MAPPINGS_U1 — Unique index reinforcing the business-key candidate on the same four columns.
  • Base event tables referenced implicitly through PRIMARY_KEY_COLUMN values — these are the feeder tables whose primary keys the mappings describe.
  • General Ledger interface and journal import objects consumed by the Global Accounting Engine during posting.
  • AX schema metadata views used to enumerate translation configuration for a given ledger.