Results for “event_status_code”

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

Overview

The view AX_AP_ACCOUNTING_EVENTS_ALL_V belongs to the AX - Global Accounting Engine product within Oracle E-Business Suite, and is documented as the replacement for the Payables table AP_ACCOUNTING_EVENTS_ALL when the AX accounting engine is enabled for the operating unit. In environments that use the Global Accounting Engine instead of the standard Subledger Accounting engine, subledger transactions must be presented to downstream accounting processes through a consistent, AP-shaped interface. This view provides exactly that interface: it exposes accounting event records for Oracle Payables with the same column set and semantics that Payables reporting, journal creation, and integration programs expect from AP_ACCOUNTING_EVENTS_ALL.

Because AX events are physically stored in a generic engine table rather than in Payables-specific tables, the view performs DECODE-based translation and column aliasing to surface that generic data in AP terms. This makes the view the effective source of truth for Payables accounting events under the AX engine, and the object that the application and any custom reporting should query instead of the underlying table.

Underlying Base Objects

The view is defined over a single base object, AX_EVENTS, filtered by APPLICATION_ID = 200. The value 200 corresponds to the Oracle Payables application, so the view returns only those AX events originating from Payables. No other base tables or views are documented as referenced by this view.

The relationship to the AP equivalent is functional rather than structural. AP_ACCOUNTING_EVENTS_ALL stores events natively in Payables; this view derives the same logical rows from AX_EVENTS when the AX engine is active. Consequently, the two objects are alternatives selected by configuration, not parallel copies populated simultaneously. The primary key of the underlying table, EVENT_ID, is exposed as ACCOUNTING_EVENT_ID, preserving the identifying column expected by dependent AP processes.

Key Columns

• ACCOUNTING_EVENT_ID — Maps from AX_EVENTS.EVENT_ID; unique identifier for the accounting event.
• EVENT_TYPE_CODE — Maps from AX_EVENTS.EVENT_TYPE; identifies the business event, such as NON_CASH_APPROVED, PREPAYMENT_APPLIED, CASH_APPLIED, CASH_CLEARED, FUTURE_MATURED, or SUPPLIER_MERGE.
• ACCOUNTING_DATE — Maps from AX_EVENTS.EVENT_DATE; the accounting date used for journal creation.
• EVENT_NUMBER — Hard-coded as -1; AX events do not carry a Payables event number, so the view supplies a constant placeholder.
• EVENT_STATUS_CODE — Derived via DECODE from AX_EVENTS.TRANSLATION_STATUS. Values N and P become CREATED; T and W become ACCOUNTED; E and U become ACCOUNTED WITH ERROR; any other value yields UNDEFINED. This column is the most frequently queried attribute, as it indicates whether an event has been successfully translated into accounting.
• SOURCE_TABLE — Derived by DECODE from EVENT_TYPE. Invoice-related events map to AP_INVOICES; check-, payment-, and clearing-related events map to AP_CHECKS.
• SOURCE_ID — Maps from AX_EVENTS.EVENT_FIELD1; identifies the source document.
• Audit and context columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE, PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and ORG_ID, all passed through from AX_EVENTS.

Common Use Cases and Queries

The view is typically queried to monitor the translation of Payables events into accounting under the AX engine, to reconcile event volumes by source table, and to detect events that did not translate cleanly. A common diagnostic query targets unaccounted or errored events:

• SELECT accounting_event_id, event_type_code, accounting_date, event_status_code, source_table, source_id, org_id FROM ax_ap_accounting_events_all_v WHERE event_status_code IN ('CREATED','ACCOUNTED WITH ERROR') ORDER BY accounting_date;
• SELECT source_table, event_status_code, COUNT(*) FROM ax_ap_accounting_events_all_v WHERE org_id = :p_org_id GROUP BY source_table, event_status_code;
• SELECT accounting_event_id, event_type_code, source_id, creation_date FROM ax_ap_accounting_events_all_v WHERE event_type_code = 'CASH_APPLIED' AND accounting_date BETWEEN :p_start AND :p_end;

Because EVENT_STATUS_CODE is a derived expression rather than an indexed column, filters on it are evaluated at runtime; constraining by ORG_ID, EVENT_TYPE_CODE, or ACCOUNTING_DATE where possible improves performance. Any logic previously written against AP_ACCOUNTING_EVENTS_ALL can generally be repointed to this view when the Global Accounting Engine is in use.