Results for “xla_event_classes_b”

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

Overview

The XLA_EVENT_CLASSES_B table is a core setup object in the Oracle Subledger Accounting (XLA) module of Oracle E-Business Suite, owned by the XLA schema. It stores the definition of every event class associated with a given subledger entity. In Subledger Accounting, an entity represents a business object such as a Payables invoice, a Receivables transaction, or an Assets addition. Within each entity, an event class groups the accounting events that produce journal entries — for example, Invoice Validated, Invoice Adjusted, or Payment Created. The _B suffix denotes the base table of the XLA event-classes entity, with translation (_TL) and other extension tables layered alongside it in the standard EBS multi-language pattern.

Under a heuristic Data Vault classification mined from the foreign-key structure, XLA_EVENT_CLASSES_B is modeled as standalone. In Data Vault terms this suggests it behaves primarily as a reference or definition table rather than a true hub, link, or satellite, since it does not participate in a documented parent-child FK chain within the extracted metadata. It functions as a source of stable business keys that other XLA objects reference by code.

Key Information Stored

The documented physical schema exposes ten columns. The composite primary key XLA_EVENT_CLASSES_B_PK is defined over APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE. Two unique indexes act as business-key candidates: XLA_EVENT_CLASSES_B_U1 (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, ZD_EDITION_NAME) and XLA_EVENT_CLASSES_B_U2 (APPLICATION_ID, EVENT_CLASS_CODE, ZD_EDITION_NAME). These guarantee that, within a given application, an event class code is unique for its entity (and edition, where ZD_EDITION_NAME applies).

• APPLICATION_ID — the owning application identifier (typically the Subledger Accounting application context) that scopes the entity and event class.
• ENTITY_CODE — the subledger entity this event class belongs to, such as the transaction type grouping in AP, AR, or FA.
• EVENT_CLASS_CODE — the short code uniquely identifying the event class within the entity; the primary lookup value used throughout XLA.
• ENABLED_FLAG — indicates whether the event class is active and available for use in accounting event processing.
• ZD_EDITION_NAME — the edition name used in the EBS 12.2 online-patching (editioning) architecture to distinguish object editions.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture who created and last modified the row and when.

Common Use Cases and Queries

Consultants and developers query this table to confirm which event classes exist for an entity before configuring accounting methods, event types, or journal line definitions. A typical lookup joins the application and entity codes to return enabled event classes:

• Verify setup: SELECT event_class_code, enabled_flag FROM xla_event_classes_b WHERE application_id = :app_id AND entity_code = :entity_code;
• Enable or disable an event class through a controlled UPDATE on ENABLED_FLAG, respecting audit columns.
• Report on all event classes across subledgers to document the accounting configuration for an implementation.
• Drive integration or reconciliation queries that map subledger events to event classes before tracing the resulting accounting entries in XLA_AE_HEADERS and XLA_AE_LINES.

Because the table is small and heavily cached by the subledger accounting engine, it is rarely a performance concern, but queries should always filter on APPLICATION_ID to leverage the leading index columns.

Related Objects

The event-class definition is referenced by the event-type and event-modeling structures that together drive Subledger Accounting. Significant related objects include:

• XLA_EVENT_TYPES_B — links event types to an event class via APPLICATION_ID and EVENT_CLASS_CODE; the most direct child of the event-class definition.
• XLA_EVENT_MODELS_B — default accounting models applied at event-class level, joined by APPLICATION_ID and EVENT_CLASS_CODE.
• XLA_EVENTS — the runtime table of actual accounting events, each associated with an event class code.
• XLA_ACCOUNTING_METHODS_B and their assignments, which resolve how an event class produces journal entries.
• XLA_AE_HEADERS and XLA_AE_LINES — the downstream journal repository whose rows are generated from events belonging to these event classes.
• Subledger entity definition views such as XLA_ENTITIES, which provide the valid ENTITY_CODE values joined by APPLICATION_ID and ENTITY_CODE.

Together these objects form the configuration and runtime chain that transforms a subledger business event into balanced accounting entries.