Search Results xla_entity_events_v




Overview
Explore in AI Chat

Overview

XLA_ENTITY_EVENTS_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, denormalized picture of accounting events and the transaction entities that generated them. Subledger Accounting is the central accounting engine that receives transaction data from source subledgers such as Payables, Receivables, Assets, and Cost Management, creates events against transaction entities, and applies accounting rules to derive journal entries. This view assembles the event header, the associated transaction entity, the event type definition, and the event class attributes into a single queryable structure, which makes it suitable for reporting, reconciliation, and integration purposes without requiring consumers to join the underlying tables themselves.

Underlying Base Objects

The view is defined over four documented objects, all referenced through APPS synonyms: XLA_EVENTS, XLA_TRANSACTION_ENTITIES, XLA_EVENT_TYPES_B, and XLA_EVENT_CLASS_ATTRS. XLA_EVENTS (aliased EVT) supplies the event-level attributes, including identifiers, dates, status codes, reference columns, and the ON_HOLD_FLAG and BUDGETARY_CONTROL_FLAG. XLA_TRANSACTION_ENTITIES (ENT) supplies transaction-level context such as the transaction number, ledger, legal entity, entity code, source identifier columns, security identifier columns, and valuation method. XLA_EVENT_TYPES_B (XET) supplies the event type and event class codes, while XLA_EVENT_CLASS_ATTRS (ECA) adds the event class group code. Joins are performed on APPLICATION_ID and EVENT_TYPE_CODE between events and event types, on APPLICATION_ID and ENTITY_ID between events and transaction entities, and on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE between event class attributes and event types.

Key Columns

  • EVENT_ID / EVENT_NUMBER — unique identifier and display number for the accounting event.
  • APPLICATION_ID / SOURCE_APPLICATION_ID — application owning the event and the originating source application.
  • EVENT_TYPE_CODE / EVENT_CLASS_CODE / EVENT_CLASS_GROUP_CODE — classification of the event used by accounting rule derivation.
  • EVENT_DATE / TRANSACTION_DATE — accounting event date and the underlying transaction date.
  • ENTITY_ID / ENTITY_CODE / TRANSACTION_NUMBER — the transaction entity and its business-facing number.
  • LEDGER_ID / LEGAL_ENTITY_ID — accounting ledger and legal entity context.
  • EVENT_STATUS_CODE / PROCESS_STATUS_CODE — event lifecycle and processing state.
  • ON_HOLD_FLAG — indicates whether the event is currently held from further accounting processing; the column the user searched for.
  • BUDGETARY_CONTROL_FLAG — indicates budgetary control applicability.
  • SOURCE_ID_* / SECURITY_ID_* — generic source and security identifiers used for subledger-specific lookups and access control.
  • REFERENCE_NUM_* / REFERENCE_CHAR_* / REFERENCE_DATE_* — flexible reference attributes carried on the event.
  • Creation/audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and program/request identifiers.

Common Use Cases and Queries

Typical uses include identifying events placed on hold, tracing an event back to its transaction entity, and reconciling event status against ledger and legal entity. The query below returns events currently on hold for a given application:

  • SELECT event_id, event_number, event_type_code, event_date, entity_code, transaction_number, ledger_id, on_hold_flag FROM xla_entity_events_v WHERE on_hold_flag = 'Y' AND application_id = :app_id ORDER BY event_date;
  • SELECT event_status_code, process_status_code, COUNT(*) FROM xla_entity_events_v GROUP BY event_status_code, process_status_code;
  • SELECT e.event_id, e.transaction_number, e.legal_entity_id, e.event_class_code FROM xla_entity_events_v e WHERE e.entity_id = :entity_id;

Because the view exposes the join logic already, it is the preferred access path for diagnostic and reconciliation reports that must relate events, entities, and event classes without duplicating the underlying join conditions.