Search Results xla_event_types_b

Overview

The XLA_EVENT_TYPES_B table is a core repository within Oracle E-Business Suite Subledger Accounting (SLA). It serves as the master definition table for all event types, which are the specific business transactions that trigger the creation of accounting entries. Each event type is a child of a broader event class and belongs to a specific subledger application and entity. This table is fundamental to the SLA architecture, as it defines the granular business activities for which accounting rules are assigned and executed. The integrity of this data is critical for ensuring accurate and complete financial reporting across all Oracle EBS modules that utilize Subledger Accounting.

Key Information Stored

The table's structure is designed to uniquely identify and categorize every event type within the system. The primary columns, which also form the table's composite primary and unique keys, are APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE. APPLICATION_ID links the event type to a specific EBS product, such as Payables or Receivables. ENTITY_CODE identifies the business entity, like Invoices or Payments. EVENT_CLASS_CODE groups related transaction types, such as Standard Invoices. Finally, EVENT_TYPE_CODE defines the specific transaction, for example, Invoice Validation or Payment Creation. Additional descriptive columns, not detailed in the provided metadata but typical for such setups, would include fields for the event type name, description, and status controls.

Common Use Cases and Queries

This table is primarily referenced for setup verification, troubleshooting accounting flows, and generating metadata reports. A common query involves listing all configured event types for a specific module to audit SLA setup. For instance, to review all Payables event types, one might use: SELECT event_class_code, event_type_code FROM xla_event_types_b WHERE application_id = 200 ORDER BY 1,2;. Another critical use case is during issue diagnosis, where developers join this table to transaction and accounting entry tables (like XLA_TRANSACTION_ENTITIES and XLA_AE_HEADERS) to trace why a specific business transaction did not generate the expected journal entries, verifying the event type's existence and active status is a first step.

Related Objects

XLA_EVENT_TYPES_B is a central hub in the SLA data model with several key relationships. It has a direct foreign key relationship with the XLA_EVENT_CLASSES_B table, typically joined via APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE, to get the event class description. Most importantly, the EVENT_TYPE_CODE and APPLICATION_ID are foreign keys into the XLA_EVENT_TYPES_TL table, which holds the translated names and descriptions. Furthermore, the columns APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE are referenced by numerous SLA transaction and accounting rule tables, such as XLA_TRANSACTION_ENTITIES (which stores individual business transactions) and the rule assignment tables (e.g., XLA_ACCT_CLASS_RULES), forming the backbone of the accounting derivation process.