Search Results xla_event_class_grps_b




Overview
Explore in AI Chat

Overview

The table XLA_EVENT_CLASS_GRPS_B is a Subledger Accounting (XLA) base table in the Oracle E-Business Suite database, owned by the XLA schema. Its documented purpose is to record groups of event classes used for processing purposes within Subledger Accounting. Event classes in EBS represent the categories of accounting-relevant business activities—such as invoices, payments, receipts, and journals—that subledgers pass to XLA for accounting rule evaluation and journal creation. By grouping these event classes, XLA_EVENT_CLASS_GRPS_B allows the application to treat a set of event classes as a single processing unit, which supports the configuration of accounting methods, event models, and application accounting definitions throughout the accounting lifecycle.

The table is documented as standalone within the mined Data Vault classification, indicating that no foreign key dependencies were detected from the physical schema. Under a Data Vault modeling suggestion, this object would therefore be treated as an independent reference or hub-like structure rather than a link or satellite, since it holds the descriptive grouping identifier directly against the application scope. It carries base-table designation ("_B") in the standard EBS naming convention, and in a multi-language configuration a corresponding translation table normally exists alongside it. The object is valid in both 12.1.1 and 12.2.2, with the documented physical schema reflecting nine columns in the 12.2.2 ETRM repository.

Key Information Stored

The most significant columns recorded in the documented schema are:

  • APPLICATION_ID — Identifies the owning Oracle application (subledger) whose event classes are grouped; a component of both the primary key and the unique business-key index.
  • EVENT_CLASS_GROUP_CODE — The short, language-independent code that names the event class group; a component of both the primary key and the unique business-key index.
  • ENABLED_FLAG — Indicates whether the event class group is active and available for processing.
  • ZD_EDITION_NAME — The editioning column introduced in the 12.2 online patching architecture; a component of the unique business-key index XLA_EVENT_CLASS_GRPS_B_U1.
  • CREATION_DATE / CREATED_BY — Standard audit columns recording when and by whom the row was created.
  • LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit columns recording the most recent change and its session context.

The surrogate primary key is XLA_EVENT_CLASS_GRPS_B_PK, defined on (APPLICATION_ID, EVENT_CLASS_GROUP_CODE). The unique index XLA_EVENT_CLASS_GRPS_B_U1 on (APPLICATION_ID, EVENT_CLASS_GROUP_CODE, ZD_EDITION_NAME) serves as the business-key candidate and simultaneously enforces the editioning constraint.

Common Use Cases and Queries

Typical usage includes reporting on which event class groups are enabled, resolving the group code for a given application, and validating configuration when accounting methods or event models produce unexpected behavior. A representative query is:

<

SELECT application_id, event_class_group_code, enabled_flag, last_update_date FROM xla.xla_event_class_grps_b WHERE enabled_flag = 'Y' ORDER BY application_id, event_class_group_code;

Configuration auditors commonly join the base table to its translation table to retrieve the descriptive group name in the user's language, and filter by ZD_EDITION_NAME = 'ORA$BASE' to restrict results to the current edition in a 12.2 environment. Migration and testing scripts frequently select from this table to verify that custom event class groupings were carried through cloning or patching.

Related Objects

  • XLA_EVENT_CLASS_GRPS_TL — Translation table supplying the language-specific name and description for each group, joined on APPLICATION_ID and EVENT_CLASS_GROUP_CODE.
  • XLA_EVENT_CLASSES_B — Defines the individual event classes that are members of a group.
  • XLA_EVENT_TYPES_B — Parent of event classes and a logical reference for the grouping hierarchy.
  • XLA_EVENT_MODELS_B — Event models for which event class groups govern processing behavior.
  • XLA_ACCOUNTING_METHODS_B — Accounting methods that consume event class groupings during journal creation.
  • FND_APPLICATION — Resolves APPLICATION_ID to the owning subledger application name.
  • FND_APPLICATION_VL and FND_LOOKUPS — Support descriptive reporting and validation of lookup values used across XLA configuration tables.