Search Results xla_event_class_attrs




Overview
Explore in AI Chat

Overview

The XLA_EVENT_CLASS_ATTRS table is a core configuration object within the XLA (Subledger Accounting) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the generic and specific attributes that govern how event classes behave during subledger accounting processing. Event classes represent the fundamental accounting business events recognized by the Subledger Accounting Engine — for example, invoice validation, payment creation, or receipt application — and this table captures the per-event-class settings that drive journal entry creation, amount calculation, and reporting behavior.

Because subledger accounting depends on consistent, centrally defined rules for generating accounting entries, XLA_EVENT_CLASS_ATTRS acts as a reference table consulted during event processing and account derivation. The documented Data Vault classification for this object is standalone, suggesting that from a dimensional modeling perspective it functions neither as a hub nor as a link or satellite in a strictly modeled sense, but rather as an independently keyed configuration entity that other processes read at runtime.

Key Information Stored

The table is keyed by the composite primary key XLA_EVENT_CLASS_ATTRS_PK, defined over APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE. This triple uniquely identifies the operating unit-independent combination of application, entity, and event class to which the attribute row belongs. A documented unique index, XLA_EVENT_CLASS_ATTRS_U1, extends this same key with ZD_EDITION_NAME, which supports the multi-edition data model introduced in later 12.2.x releases.

Among the seventeen documented columns, the most significant include:

Common Use Cases and Queries

Typical use cases for querying XLA_EVENT_CLASS_ATTRS include troubleshooting journal entry generation, validating accounting setup, and building subledger reporting extracts. A common reporting query joins this table to the event class and entity reference tables to retrieve the journal category and amount-calculation flags for a given application and entity.

For example, to identify all event classes configured to allow budgets within Payables:

  • SELECT event_class_code, je_category_name, allow_budgets_flag FROM xla_event_class_attrs WHERE application_id = :app_id AND entity_code = :entity AND allow_budgets_flag = 'Y';

Other practical scenarios include auditing changes to calculation flags over time using the audit columns, verifying that encumbrance accounting is enabled for the relevant event classes, and cross-checking the JE_CATEGORY_NAME against GL journal categories before period close.

Related Objects

XLA_EVENT_CLASS_ATTRS references and is referenced by several objects in the Subledger Accounting schema. Principal related objects include:

  • XLA_EVENT_CLASSES — the parent definition of event classes; join on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE.
  • XLA_EVENTS — the runtime events generated by subledger transactions; related through application, entity, and event class.
  • XLA_ENTITY_TYPES — defines the entity codes referenced by ENTITY_CODE.
  • XLA_JE_CATEGORIES — source of JE_CATEGORY_NAME values.
  • XLA_ACCOUNTING_PROGRAMS — accounting programs that consume event class attributes at runtime.
  • XLA_LOOKUPS — lookup values used by the control flags.

Because the table is documented as standalone under the Data Vault heuristic, its relationships are enforced primarily through business rules and application logic rather than a dense foreign-key network.