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:
- EVENT_ID — the surrogate primary key, enforced by XLA_EVENTS_PK. This is the value written onto downstream accounting lines (XLA_AE_HEADERS, XLA_AE_LINES) to link entries back to their originating event.
- APPLICATION_ID — identifies the source subledger application (e.g., 200 for Payables, 222 for Receivables).
- ENTITY_ID — identifies the owning transaction entity within that application.
- EVENT_TYPE_CODE — the accounting event classification, such as invoice creation, payment, or adjustment.
- EVENT_DATE and TRANSACTION_DATE — the accounting date and the originating transaction date, respectively.
- EVENT_STATUS_CODE and PROCESS_STATUS_CODE — control flags indicating whether the event has been processed, is unprocessed, or is in error.
- EVENT_NUMBER — the human-readable sequence assigned within the entity.
- ON_HOLD_FLAG — indicates events deliberately excluded from accounting processing.
- BUDGETARY_CONTROL_FLAG — supports public-sector budgetary control integration.
- REFERENCE_NUM_1 through REFERENCE_NUM_4, REFERENCE_CHAR_1 through REFERENCE_CHAR_4, and REFERENCE_DATE_1 through REFERENCE_DATE_4 — denormalized reference placeholders used by subledger extract programs to carry transaction identifiers.
- UPG_BATCH_ID — the only documented foreign key, referencing XLA_UPG_BATCHES, used during upgrade processing. Additional upgrade columns (UPG_SOURCE_APPLICATION_ID, UPG_VALID_FLAG) accompany it.
- Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — identify the concurrent request that created or last modified the row.
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.
-
The XLA_EVENTS table record all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE.
-
The XLA_EVENTS table record all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE.
-
SYNONYM: APPS.XLA_EVENTS 12.1.1
-
SYNONYM: APPS.XLA_EVENTS 12.2.2
-
TABLE: XLA.XLA_EVENTS 12.2.2
-
TABLE: XLA.XLA_EVENTS 12.1.1