Search Results ax_ap_ae_headers_all_v

Overview

The AX_AP_AE_HEADERS_ALL_V view is a compatibility layer within the Oracle E-Business Suite Global Accounting Engine (AX) module. Its documented purpose is to act as a replacement for the Payables accounting entry table, AP_AE_HEADERS_ALL, when the AX accounting engine is used instead of the standard Subledger Accounting or the legacy AP accounting engine. In environments operating the Global Accounting Engine, subledger accounting events are stored in AX-owned tables rather than the AP-specific tables, and the standard AP header view contains no rows. This view re-presents AX event data using the AP accounting entry header column names, so that reports, concurrent programs, and integrations expecting the AP structure continue to function against a consistent interface while the underlying engine has changed.

Because its column names mirror the AP accounting entry header, the view is typically consumed by Payables reporting, period-close reconciliation, and custom extracts that historically targeted AP_AE_HEADERS_ALL. It is important to note the ETRM metadata records the view as not implemented in the reference database, and no base objects are documented beyond those visible in the view text.

Underlying Base Objects

The view text defines AX_AP_AE_HEADERS_ALL_V over two AX tables: AX_EVENTS (aliased AXE) and AX_SLE_HEADERS (aliased AXSH). The two are joined on AXE.EVENT_ID = AXSH.EVENT_ID, and the WHERE clause restricts results to subledger headers belonging to Payables by filtering AXSH.APPLICATION_ID = 200, the application identifier for Oracle Payables. The view also calls several packaged functions on the AX_PAYABLES_PKG package to derive or translate values, including AE_CATEGORY, AE_CROSS_CURRENCY_FLAG, and AE_HEADER_DESCRIPTION. These functions accept the AX event type (and, for some, additional context such as event field or currency) and translate AX-native codes into the AP-equivalent representations, which is the mechanism that preserves backward compatibility with the AP schema.

Key Columns

• AE_HEADER_ID — mapped from AXSH.SLE_HEADER_ID; the subledger accounting header identifier used as the accounting entry header key.
• ACCOUNTING_EVENT_ID — mapped from AXSH.EVENT_ID, the identifier of the originating accounting event.
• AE_CATEGORY — derived via AX_PAYABLES_PKG.AE_CATEGORY(AXE.EVENT_TYPE). This is the column users most often search for ("ae_category"); in the AP model it classifies the accounting entry (for example, invoice, payment, or adjustment categories). Here its value is computed from the AX event type, so the returned category reflects the AX event rather than a stored AP value.
• CROSS_CURRENCY_FLAG — computed by AX_PAYABLES_PKG.AE_CROSS_CURRENCY_FLAG from event type, document identifier, and currency code, indicating whether the entry involves cross-currency accounting.
• DOCUMENT_ID — from AXE.EVENT_FIELD1, the transaction or document reference associated with the event.
• SET_OF_BOOKS_ID, PERIOD_NAME, ACCOUNTING_DATE — ledger, accounting period, and effective accounting date for the event.
• GL_TRANSFER_FLAG, GL_TRANSFER_RUN_ID — indicate whether the entry has been transferred to General Ledger and identify the transfer run.
• DESCRIPTION — derived by AX_PAYABLES_PKG.AE_HEADER_DESCRIPTION from the event type and stored description.
• ACCOUNTING_ERROR_CODE and GL_TRANSFER_ERROR_CODE — exposed as NULL literals for structural compatibility with the AP header view.

Common Use Cases and Queries

Typical uses include reconciling accounting entries by category and period, confirming GL transfer status, and extracting Payables accounting header data in AX-enabled instances.

To list entries by category for a period:

• SELECT ae_header_id, accounting_event_id, ae_category, period_name, accounting_date FROM ax_ap_ae_headers_all_v WHERE ae_category = :category AND period_name = :period ORDER BY accounting_date;

To identify entries not yet transferred to GL:

• SELECT ae_header_id, ae_category, gl_transfer_flag, set_of_books_id FROM ax_ap_ae_headers_all_v WHERE gl_transfer_flag = 'N' AND set_of_books_id = :sob;

Because the columns AE_CATEGORY, CROSS_CURRENCY_FLAG, and DESCRIPTION are computed through packaged functions, queries filtering on these columns should be tested for performance, and the view should not be treated as a table for direct DML.