Results for “ax_event_category_v”

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

Overview

The view AX_EVENT_CATEGORY_V belongs to the AX – Global Accounting Engine product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes a unified, presentation-ready list of event category codes and their descriptive names, reconciling two distinct sources of category data within the Global Accounting Engine. The view is primarily a reporting and reference object: it allows inquiry forms, concurrent programs, and custom reports to resolve a category code to a human-readable name without needing to know whether the category originated from Oracle's document sequencing setup or from the AX lookup mechanism.

Because the category list is consumed in accounting event processing, this view supports the assignment and validation of event categories used during subledger-to-General-Ledger transfers and AX event generation. Its dual-source UNION means any consumer of the view automatically sees both standard document sequence categories and the AX-specific default category lookups.

Underlying Base Objects

The view text is documented as follows:

• FND_DOC_SEQUENCE_CATEGORIES — filtered with APPLICATION_ID = 101, providing the document sequence categories registered for the Global Accounting Engine application.
• AX_LOOKUPS — filtered with LOOKUP_TYPE = 'AX_DEFAULT_CATEGORY', providing application-specific default category lookup values defined within AX.

The two result sets are combined with a UNION, which implies duplicate category codes are eliminated. The first branch contributes the standard EBS document sequencing categories, while the second contributes the default and supplemental categories maintained directly in AX. Note that the ETRM metadata for this object records no separately documented owner and no referenced base objects beyond those appearing in the view text; the definition is therefore best treated as authoritative.

Key Columns

The view projects two columns, drawn positionally from each branch of the UNION:

• CATEGORY_CODE — sourced from FND_DOC_SEQUENCE_CATEGORIES.CODE in the first branch and from AX_LOOKUPS.LOOKUP_CODE in the second. This is the unique identifier for the category and is the value typically stored on accounting event or journal records.
• CATEGORY_NAME — sourced from FND_DOC_SEQUENCE_CATEGORIES.NAME and AX_LOOKUPS.MEANING respectively. This is the descriptive label presented to users in lists of values and reports.

Common Use Cases and Queries

Typical uses include populating a category list of values on a parameter form, validating an inbound category code from an interface table, and producing a category reference listing for reconciliation of AX-generated events. A simple lookup of a single category is shown below:

• SELECT CATEGORY_CODE, CATEGORY_NAME FROM AX_EVENT_CATEGORY_V WHERE CATEGORY_CODE = :p_category_code;
• SELECT CATEGORY_CODE, CATEGORY_NAME FROM AX_EVENT_CATEGORY_V ORDER BY CATEGORY_NAME;

Because the view unions document sequence categories with AX default category lookups, it is the appropriate single source when a report must present the complete set of categories recognized by the Global Accounting Engine. Queries that require application-specific filtering or attachment of additional attributes should join back to FND_DOC_SEQUENCE_CATEGORIES or AX_LOOKUPS directly rather than relying on this view.