Search Results user_exit

Overview

AX_EVENT_TYPES_V is a reporting and inquiry view in the Oracle E-Business Suite Global Accounting Engine (AX) module. The Global Accounting Engine serves as the accounting derivation and subledger transfer engine for EBS, converting Subledger Accounting events into journal entries. This view exposes the configured event types that the engine recognizes and processes, together with their descriptive attributes. In Oracle EBS 12.1.1 and 12.2.2, the view is documented under the AX product but is not implemented in every database; installations that do not use the Global Accounting Engine will not contain this object. Where present, it presents event type definitions in a denormalized, human-readable form by joining the base table to lookups for the application name, set of books names, and event category name. The view is read-only from a functional standpoint and is typically consumed for diagnostics, configuration audits, and integration queries rather than for transaction processing.

Underlying Base Objects

The documented view text identifies the following sources:

• AX_EVENT_TYPES AET — the primary base table holding event type definitions.
• GL_SETS_OF_BOOKS GSOB and GL_SETS_OF_BOOKS GSOB2 — joined twice to resolve the set of books name for the event type and for the posting set of books.
• AX_EVENT_CATEGORY_V AECV — a companion view supplying the event category name.
• FND_APPLICATION_VL FA — the application definition view supplying the application name.

The join conditions link the event type to its category (CATEGORY_CODE), its owning application (APPLICATION_ID), its set of books (SET_OF_BOOKS_ID), and its posting set of books (POSTING_SET_OF_BOOKS_ID). The documented metadata lists no additional base objects beyond those above.

Key Columns

• ROW_ID, CATEGORY_CODE, SET_OF_BOOKS_ID, APPLICATION_ID, EVENT_TYPE — the identifying attributes of an event type within a specific set of books and application context.
• DESCRIPTION, ENABLED_FLAG — user-facing description and whether the event type is active.
• TRANSLATION_SCHEME, DIRECT_FLAG — controls governing how the event type is processed by the accounting engine.
• USER_EXIT — the user exit routine associated with the event type. This is the column most relevant to users searching on "user_exit," indicating which custom or seeded exit logic is invoked when the event type is processed.
• INCLUDE_IN_PROGRAM_FLAG — indicates whether the event type participates in the relevant accounting program.
• APPLICATION_NAME, SET_OF_BOOKS_NAME, CATEGORY_NAME, POSTING_SET_OF_BOOKS_ID, POSTING_SET_OF_BOOKS_NAME — denormalized descriptive values resolved from the joins.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing which event types call a user exit, confirming the posting set of books for a given event type, and reporting enabled event types per application and category.

List event types that reference a user exit:

SELECT event_type, application_name, set_of_books_name,
       category_name, user_exit, enabled_flag
FROM   ax_event_types_v
WHERE  user_exit IS NOT NULL
ORDER  BY application_name, event_type;

Report enabled event types and their posting books:

SELECT application_name, category_name, event_type,
       set_of_books_name, posting_set_of_books_name,
       translation_scheme, direct_flag
FROM   ax_event_types_v
WHERE  enabled_flag = 'Y'
ORDER  BY application_name, category_name;

Because the view is not implemented in all databases, availability should be confirmed before deployment in integration or reporting code.