Results for “axbv_document_histories”

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

Overview

AXBV_DOCUMENT_HISTORIES is a read-only view shipped with the Global Accounting Engine (AX) product family in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes the event-level audit trail that the Global Accounting Engine records as it processes accounting events originating from subledger and feeder systems. The view presents a chronological history of document and event processing, including translation status and diagnostic messages, and is primarily intended for reconciliation, troubleshooting, and reporting on the status of accounting event generation. Because it is defined WITH READ ONLY, it cannot be used as a DML target and must be treated strictly as a query surface. Note that the ETRM metadata records this object as not implemented in the reference database associated with the documentation, meaning no live rows were available to validate the column semantics during documentation capture.

Underlying Base Objects

The view text documented in the ETRM metadata defines AXBV_DOCUMENT_HISTORIES as a projection over a single base object, AX_EVENTS:

• SELECT EVENT_ID, EVENT_DATE, EVENT_TYPE, EVENT_FIELD1, TRANSLATION_STATUS, MESSAGE_TEXT, APPLICATION_ID, SET_OF_BOOKS_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM AX_EVENTS WITH READ ONLY

The ETRM metadata lists no other referenced base objects. There is an important discrepancy to observe: the projected column list in the view text differs from the "Columns" list recorded in the same metadata. The view text selects EVENT_DATE, EVENT_TYPE, EVENT_FIELD1, and MESSAGE_TEXT, whereas the documented column list names ACCOUNTING_DATE, DOCUMENT_CATEGORY, DOCUMENT_ID, and MESSAGE. The column list appears to describe the logical contents of the underlying event record rather than the literal projection. Practitioners should verify the actual view definition in their instance with DBMS_METADATA.GET_DDL or ALL_VIEWS.TEXT before relying on any specific column name. Note also that DOCUMENT_CATEGORY — the term the user searched for — does not appear in the documented view text but is listed among the view's columns in the metadata, reinforcing the need for instance-level verification.

Key Columns

• EVENT_ID — Unique identifier for each accounting event recorded by the Global Accounting Engine.
• EVENT_DATE / ACCOUNTING_DATE — The date associated with the event, used to align history records with accounting periods.
• EVENT_TYPE — Classification of the event processed.
• DOCUMENT_CATEGORY — Category of the source document the event relates to; the attribute referenced by searches for document classification.
• DOCUMENT_ID / EVENT_FIELD1 — Identifier or reference to the originating document or event field.
• TRANSLATION_STATUS — Status of the translation step applied to the event in the accounting engine.
• MESSAGE_TEXT / MESSAGE — Diagnostic or informational text produced during event processing.
• APPLICATION_ID — Identifies the source application that generated the event.
• SET_OF_BOOKS_ID — The ledger (set of books) context for the event.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include tracing why a document failed to translate, auditing event volume by application or ledger, and reporting history for a given document category.

• Review recent processing history and messages:

  SELECT event_id, translation_status, message_text
  FROM   axbv_document_histories
  WHERE  set_of_books_id = :ledger_id
  ORDER BY creation_date DESC;

• Filter by the searched attribute, document category:

  SELECT event_id, accounting_date, document_id, translation_status
  FROM   axbv_document_histories
  WHERE  document_category = :category
  AND    accounting_date BETWEEN :from_date AND :to_date;

• Isolate events with errors for a source application:

  SELECT event_id, application_id, message_text
  FROM   axbv_document_histories
  WHERE  translation_status <> 'TRANSLATED';

Because the view is read-only and defined over AX_EVENTS, query performance depends on indexing of the base table; predicate on SET_OF_BOOKS_ID, ACCOUNTING_DATE, or APPLICATION_ID where possible.