Search Results additional_date

Overview

AX_EVENTS_V1 is a reporting and integration view belonging to the Global Accounting Engine (AX) product family within Oracle E-Business Suite. It exposes the contents of the AX_EVENTS table through a fixed column projection, providing downstream consumers with a stable, read-only interface that isolates them from potential physical changes to the underlying event repository. AX_EVENTS serves as the central staging and tracking table for accounting events generated by subledger applications before and during transfer to the general ledger. The view is documented against EBS 12.1.1 and 12.2.2, and its column list includes the standard EBS who-columns, event descriptors, subledger accounting attributes, document sequencing fields, and a large block of generic EVENT_FIELD columns. The presence of ADDITIONAL_DATE, ADDITIONAL_NUMBER, and ADDITIONAL_VARCHAR2 makes the view particularly relevant to searches involving user-defined or auxiliary event metadata, since these columns frequently carry supplementary dates, reference numbers, and free-form identifiers that do not map to the primary EVENT_DATE or DOC_SEQUENCE_VALUE.

Underlying Base Objects

Per the documented view text, AX_EVENTS_V1 is defined entirely over the base table AX_EVENTS. The view performs no joins, unions, or derivations; it is a straightforward column-level selection expressed as a quoted column list. As a result, each row in the view corresponds one-to-one with a row in AX_EVENTS, subject to the privileges granted on the view. Because the view references only AX_EVENTS, any predicate applied to view columns is pushed to the base table, and no additional access paths are introduced. The ETRM metadata notes that the view is "Not implemented in this database" and lists no separately documented referenced base objects, which is consistent with a simple projection view whose dependencies are captured through the underlying table rather than through the view definition itself.

Key Columns

• EVENT_ID — Primary identifier for the accounting event row; used to correlate events across subledger and GL processing.
• EVENT_TYPE, APPLICATION_ID, SET_OF_BOOKS_ID, ORG_ID — Classify the event by type, source application, ledger, and operating unit, supporting multi-org and multi-ledger reporting.
• EVENT_DATE — The accounting event date, distinct from the transaction date carried in some EVENT_FIELD columns.
• ADDITIONAL_DATE — The column matching the user's "additional_date" search; typically stores a secondary or user-defined date associated with the event, useful when a date other than EVENT_DATE drives reporting.
• ADDITIONAL_NUMBER, ADDITIONAL_VARCHAR2 — Complementary numeric and character supplementary values, commonly used for external references, voucher numbers, or custom attributes.
• DOC_SEQUENCE_ID, DOC_SEQUENCE_VALUE — Document sequencing identifiers and the assigned sequence value, essential for statutory numbering and audit trails.
• TRANSLATION_STATUS, TRANSLATED_DATE — Indicate whether the event has been translated into GL balances and when, supporting reconciliation between subledger events and GL postings.
• MESSAGE_TEXT — Diagnostic or processing message text associated with event transfer.
• EVENT_FIELD1 through EVENT_FIELD25 — Generic attribute columns populated contextually by the originating application.
• Who-columns and program columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE provide auditing and concurrent program traceability.

Common Use Cases and Queries

The view is typically queried for event-level reporting, reconciliation of subledger events to GL, document sequencing audits, and integration extracts. A common pattern filters on ADDITIONAL_DATE, since searches for that column indicate a need to report by a secondary date.

-- Events with a secondary date in a period
SELECT event_id, event_type, event_date, additional_date,
       additional_number, additional_varchar2, doc_sequence_value
FROM   ax_events_v1
WHERE  additional_date BETWEEN :p_start AND :p_end
AND    set_of_books_id = :p_ledger_id;

-- Document sequencing reconciliation
SELECT doc_sequence_id, doc_sequence_value, event_id, translation_status
FROM   ax_events_v1
WHERE  application_id = :p_app_id
AND    doc_sequence_value IS NOT NULL;

-- Pending translation by event type
SELECT event_type, COUNT(*)
FROM   ax_events_v1
WHERE  translation_status <> 'Y'
GROUP BY event_type;

These queries reflect the documented column set and treat the view as the supported access layer over AX_EVENTS for reporting and extraction purposes.