Search Results xla_diag_events




Overview
Explore in AI Chat

Overview

XLA_DIAG_EVENTS is a Subledger Accounting (XLA) repository table that stores events processed by the Oracle EBS diagnostic framework. Within the XLA product, accounting events represent business transactions originating in subledgers such as Payables, Receivables, Assets, and Payroll, which are subsequently transformed into journal entries through accounting rules. The diagnostic framework captures these events for troubleshooting, validation, and audit purposes, enabling support personnel and implementers to trace how a specific transaction was evaluated during subledger accounting processing.

The table resides in the XLA schema and is classified as VALID in the ETRM 12.2.2 repository, with documented presence in 12.1.1 environments as well. From a heuristic Data Vault perspective, the metadata indicates a standalone classification, which suggests modeling this entity as a hub table keyed on EVENT_ID. In practice, the table behaves as a diagnostic capture point rather than a transactional source of truth; the persistent accounting event data lives in XLA_AE_HEADERS and XLA_AE_LINES, while XLA_DIAG_EVENTS serves as a supporting diagnostic trace.

Key Information Stored

The documented physical schema contains 18 columns. The most significant columns for identification, filtering, and interpretation are:

The distinction between EVENT_ID and the transactional attributes (TRANSACTION_NUMBER, EVENT_NUMBER, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE) is important: EVENT_ID is the immutable synthetic key, while the latter combination constitutes the natural business meaning of the event.

Common Use Cases and Queries

Typical usage centers on diagnostics and reconciliation. A support analyst investigating an accounting failure may query events by transaction or by concurrent request:

  • Trace a specific transaction: SELECT * FROM XLA.XLA_DIAG_EVENTS WHERE TRANSACTION_NUMBER = :txn AND APPLICATION_ID = :app_id;
  • Inspect the output of a concurrent diagnostic run: SELECT EVENT_ID, TRANSACTION_NUMBER, EVENT_CLASS_CODE, EVENT_TYPE_CODE FROM XLA.XLA_DIAG_EVENTS WHERE REQUEST_ID = :request_id ORDER BY EVENT_NUMBER;
  • Investigate event distribution by class: SELECT EVENT_CLASS_CODE, COUNT(*) FROM XLA.XLA_DIAG_EVENTS GROUP BY EVENT_CLASS_CODE;
  • Join to the accounting engine for reconciliation: link EVENT_ID or the natural key columns to XLA_AE_HEADERS and XLA_AE_LINES to confirm whether a diagnostic event produced corresponding journal lines.

Because the table is diagnostic in nature and typically small relative to production accounting tables, date-bounded queries using EVENT_DATE and CREATION_DATE are effective for isolating records within a processing window.

Related Objects

The most significant objects in the XLA diagnostic and accounting ecosystem that logically relate to XLA_DIAG_EVENTS are:

  • XLA_AE_HEADERS — Accounting entry headers generated from processed events; join on EVENT_ID where populated.
  • XLA_AE_LINES — Detail journal lines corresponding to accountants entries, reached via AE_HEADER_ID.
  • XLA_EVENTS — Persistent repository of accounting events from which diagnostic events are derived.
  • XLA_TRANSACTION_ENTITIES — Maps source transactions to entities via ENTITY_CODE and TRANSACTION_NUMBER.
  • XLA_EVENT_CLASSES / XLA_EVENT_TYPES — Reference metadata for EVENT_CLASS_CODE and EVENT_TYPE_CODE.
  • XLA_DIAG_DIAGNOSTICS — Parent diagnostic run metadata corresponding to REQUEST_ID context.
  • FND_CONCURRENT_REQUESTS — Concurrent program run context tied to REQUEST_ID and PROGRAM_ID.

Because the metadata classifies XLA_DIAG_EVENTS as standalone with a single primary key and no declared foreign keys, joins to related accounting tables are generally performed on business columns rather than enforced referential constraints.