Search Results ax_event_types_n1

Overview

AX.AX_EVENT_TYPES is a seed data table in the Oracle E-Business Suite (12.1.1 and 12.2.2) that is owned by the AX (Subledger Accounting / formerly Applications Transaction and Reconciliation) schema. It stores the event type definitions used by the Subledger Accounting (SLA) engine and the ETRM (Event Type and Translation) framework. According to the ETRM documentation, the table "stores the event types" and contains "a row for every event type defined per main set of books and posting set of books." The setup is segmented by both the primary Set of Books and the posting Set of Books, as well as the owning Application, so the same business event (e.g., an invoice or payment) can be translated differently depending on the ledger context that generated it.

Conceptually, each row fully describes how an accounting event should be translated into journal entries. This includes the set of books and application where the event is defined, the event type code, the translation scheme used for the event, the direction of the event type (direct, reverse or offset), the category used to generate the journal sequence, and an optional PL/SQL user exit that is executed before translation.

From a heuristic Data Vault modeling perspective, this object is best classified as a link: its primary key brings together the Set of Books, Application, Posting Set of Books and Event Type into a business relationship that is further qualified by descriptive attributes. The relationship is enforced by the primary key constraint AX_EVENT_TYPES_PK, composed of SET_OF_BOOKS_ID, APPLICATION_ID, POSTING_SET_OF_BOOKS_ID and EVENT_TYPE.

Key Information Stored

The table contains 16 documented columns. The most significant include:

• SET_OF_BOOKS_ID – identifies the primary ledger (Set of Books) in which the event is defined.
• POSTING_SET_OF_BOOKS_ID – identifies the posting Set of Books context.
• APPLICATION_ID – the application that owns the event type.
• EVENT_TYPE – the event type code (VARCHAR2(30)).
• TRANSLATION_SCHEME – the translation scheme name applied to the event.
• DIRECT_FLAG – the direction of the event type (direct, reverse, or offset).
• CATEGORY_CODE – the category used to generate the journal sequence.
• USER_EXIT – an optional PL/SQL user exit (VARCHAR2(1996)) executed before translation.
• INCLUDE_IN_PROGRAM_FLAG – Y/N flag indicating whether the event is included in the Translator Program.
• ENABLED_FLAG – indicates whether the event type is enabled.
• DESCRIPTION – free-text description of the event type.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / CREATION_DATE / CREATED_BY / LAST_UPDATE_LOGIN – standard Who columns for audit tracking.

Two indexes are defined. The unique index AX_EVENT_TYPES_U1 on (SET_OF_BOOKS_ID, APPLICATION_ID, POSTING_SET_OF_BOOKS_ID, EVENT_TYPE) is the primary business-key candidate and mirrors the PK. The non-unique index AX_EVENT_TYPES_N1 on (SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME) supports access by translation scheme. Both reside in the APPS_TS_SEED tablespace.

Common Use Cases and Queries

Typical usage includes reviewing event type configuration, diagnosing translation failures, and reporting on which event types are enabled per ledger. A common pattern selects category, direction and translation scheme for a given event:

• List all enabled event types for a Set of Books and application.
• Find the translation scheme and user exit for a specific event type.
• Identify events flagged for inclusion in the Translator Program.
• Audit recent setup changes using the Who columns.

A representative query is:

SELECT event_type, translation_scheme, category_code,
       direct_flag, user_exit, enabled_flag
FROM   ax.ax_event_types
WHERE  set_of_books_id = :sob
AND    application_id = :app
AND    enabled_flag = 'Y';

For translation troubleshooting, join to AX_TRANS_SCHEMES and AX_TRANS_PROGRAMS on the respective foreign keys.

Related Objects

Documentation references two foreign keys from this table. The most significant related objects are:

• AX.AX_TRANS_SCHEMES – referenced by SET_OF_BOOKS_ID; provides the translation scheme definition.
• AX.AX_TRANS_PROGRAMS – referenced by APPLICATION_ID; provides the translator program definition.
• AX.AX_TRANS_EVENTS – parent event rows that link to event types by Set of Books, posting Set of Books, application and event type.
• AX.AX_TRANS_SCHEDULES – schedule rules that reference translation schemes and event types.
• GL.GL_JE_CATEGORIES – correlates CATEGORY_CODE with the journal entry category used for sequencing.
• FND.FND_APPLICATION – joins on APPLICATION_ID to resolve the application name.
• GL.GL_SETS_OF_BOOKS – joins on SET_OF_BOOKS_ID to resolve the ledger name.