Results for “xla_events”

50+ results




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

Overview

The XLA_EVENTS table is the central event repository within the Subledger Accounting (XLA) architecture of Oracle E-Business Suite 12.1.1 and 12.2.2. Owned by the XLA schema, it stores every accounting event generated by the subledgers — Payables, Receivables, Assets, Inventory, Payroll, and others — before those events are transformed into journal entries by the Subledger Accounting Engine. In the EBS processing model, subledger transactions create events, events create accounting entries, and entries ultimately transfer to the General Ledger. XLA_EVENTS occupies the second stage of that pipeline and is therefore the principal auditing and troubleshooting point for the Create Accounting process.

From a dimensional-modeling perspective, the heuristic Data Vault classification for this object is standalone; the mined foreign-key structure does not show it acting as a subordinate satellite of another business key. It is best modeled as a transaction-level hub-like entity keyed on the surrogate EVENT_ID, with descriptive status and reference attributes carried directly on the row.

Key Information Stored

The documented physical schema for 12.2.2 contains 36 columns. The most significant are:

Two unique indexes define business-key candidates: XLA_EVENTS_U1 (EVENT_ID, APPLICATION_ID) and XLA_EVENTS_U2 (ENTITY_ID, EVENT_NUMBER, APPLICATION_ID), the latter guaranteeing that event numbers are unique per entity and application.

Common Use Cases and Queries

The table is queried most often when diagnosing why a transaction failed to create accounting, when reconciling subledger activity to GL, or when reporting event volumes by subledger and period. A typical diagnostic query retrieves unprocessed or errored events for a given application and date range:

SELECT e.event_id, e.entity_id, e.event_type_code,
       e.event_status_code, e.process_status_code, e.event_date
FROM   xla.xla_events e
WHERE  e.application_id = 200
AND    e.process_status_code IN ('U','E')
AND    e.event_date BETWEEN :p_start AND :p_end;

Joining XLA_EVENTS to XLA_AE_HEADERS on EVENT_ID and APPLICATION_ID provides the end-to-end view from event to journal line, which is the standard audit trail for Create Accounting. Event counts grouped by EVENT_TYPE_CODE and accounting period support period-close reporting, while the PROCESS_STATUS_CODE column drives exception reports for the accounting reconciliation process.

Related Objects

  • XLA_UPG_BATCHES — referenced by XLA_EVENTS.UPG_BATCH_ID; tracks upgrade batches that generated events during migration.
  • XLA_AE_HEADERS — joined on EVENT_ID and APPLICATION_ID; holds the journal entry headers created from each event.
  • XLA_AE_LINES — the journal lines that trace back through the header to a specific EVENT_ID.
  • XLA_EVENTS_PK / XLA_EVENTS_U1 / XLA_EVENTS_U2 — the indexes enforcing primary and business-key uniqueness.
  • XLA_EVENT_TYPES and the XLA_ARRAY_EVENT_TYPE structure — define the event type metadata and programmatic array type used when this table's rows are constructed.
  • XLA_ACCOUNTING_PKG and the Create Accounting concurrent programs — the engine that reads XLA_EVENTS and writes the resulting accounting entries.