Search Results ax_events




Overview
Explore in AI Chat

Overview

AX_EVENTS is a core table in the AX (Global Accounting Engine) product module of Oracle E-Business Suite, documented as valid in both release 12.1.1 and 12.2.2. It stores accounting events information — the discrete, registerable business transactions that the Global Accounting Engine recognizes and processes before they are transformed into subledger accounting entries. In the AX architecture, an event is the semantic anchor that carries the originating transaction's context (source application, event classification, set of books, and a set of descriptive flexfield-style payload fields) so that downstream accounting programs can generate and post the corresponding accounting lines.

The table is physically owned by the AX schema and exposes 48 documented columns in the 12.2.2 physical schema. From a modeling perspective, the FK structure suggests a hub-leaning Data Vault classification: the table is identified by a single surrogate key and is referenced by dependent tables, but it also carries a foreign key to a document sequence reference table, which is characteristic of a hub with a small outbound link. This classification is a heuristic suggestion mined from the foreign key topology rather than an Oracle-prescribed design.

Key Information Stored

Common Use Cases and Queries

The principal use case is event tracing: identifying which business events have been captured by the Global Accounting Engine and whether they have been successfully translated into accounting entries. A typical query joins AX_EVENTS to AX_SLE_HEADERS on EVENT_ID to return the subledger accounting header generated for each event:

  • SELECT e.EVENT_ID, e.EVENT_TYPE, e.EVENT_DATE, e.TRANSLATION_STATUS, h.SLE_HEADER_ID FROM AX_EVENTS e, AX_SLE_HEADERS h WHERE e.EVENT_ID = h.EVENT_ID.
  • Filtering by SET_OF_BOOKS_ID, ORG_ID, and EVENT_DATE range supports period-close reconciliation reporting.
  • Querying rows with TRANSLATION_STATUS not yet complete identifies events pending accounting generation, a common subledger reconciliation and troubleshooting pattern.
  • Joining DOC_SEQUENCE_ID to FND_DOCUMENT_SEQUENCES resolves the assigned document sequence name for audit reporting.
  • Joining APPLICATION_ID to FND_APPLICATION identifies the originating product for cross-application event volume analysis.

Related Objects

  • AX_SLE_HEADERS — references AX_EVENTS via EVENT_ID; holds the subledger accounting header produced from the event.
  • AX_SLE_HEADERS_ARCH — the archived counterpart, also referencing AX_EVENTS.EVENT_ID for historical event accounting.
  • FND_DOCUMENT_SEQUENCES — referenced by AX_EVENTS.DOC_SEQUENCE_ID, supplying the document sequence definition for the event.
  • AX_EVENTS_PK / AX_EVENTS_U1 — the primary key constraint and unique index over EVENT_ID, essential for join performance.
  • FND_APPLICATION — resolves APPLICATION_ID to the source application name.
  • GL_SETS_OF_BOOKS / GL_LEDGERS — resolves SET_OF_BOOKS_ID to the accounting ledger.