Results for “xla_event_types_b”

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

Overview

The XLA_EVENT_TYPES_B table is a core configuration and reference table within the Subledger Accounting (XLA) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores every event type that belongs to an event class, providing the enumerated vocabulary by which Subledger Accounting recognizes, categorizes, and processes business events originating from subledger transactions such as payables invoices, receivables transactions, inventory movements, and payroll runs. Each row pairs an event class with one or more permissible event types, and carries flags that determine whether an event type participates in accounting and tax generation.

The object resides in the XLA schema and is registered as VALID in the EBS data dictionary. It is multi-tenant aware, as evidenced by the ZD_EDITION_NAME column that participates in both unique indexes. From a heuristic Data Vault modeling perspective, this object is classified as a standalone structure. That classification suggests modeling the table as an independent hub (or reference table) keyed on its composite business key, without mandatory parent links into other hubs at the physical level. The standalone classification reflects the fact that the documented foreign-key mining did not surface dependencies on other XLA entities, even though functional relationships to event classes and application contexts clearly exist at the logical level.

Key Information Stored

The table contains 13 documented columns. The physical primary key, XLA_EVENT_TYPES_B_PK, is a composite surrogate key consisting of APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE. Two unique indexes act as business-key candidates: XLA_EVENT_TYPES_B_U1 covers APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE, and ZD_EDITION_NAME, while XLA_EVENT_TYPES_B_U2 covers APPLICATION_ID, EVENT_TYPE_CODE, and ZD_EDITION_NAME. The most significant columns are:

• APPLICATION_ID — identifies the owning application (for example, Payables or Receivables) in which the event originates; part of the primary key and both unique indexes.
• ENTITY_CODE — the transaction entity within the application to which the event applies; part of the primary key and the U1 business key.
• EVENT_CLASS_CODE — the event class that the event type belongs to; part of the primary key and the U1 business key.
• EVENT_TYPE_CODE — the specific event type (for example, invoice validated or invoice accounted); part of the primary key, U1, and U2.
• ACCOUNTING_FLAG — indicates whether the event type is eligible for accounting generation.
• TAX_FLAG — indicates whether the event type is relevant to tax processing.
• ENABLED_FLAG — controls whether the event type is currently active for use by the subledger.
• ZD_EDITION_NAME — the edition discriminator that supports multi-tenant or editioned deployments and participates in both unique indexes.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard concurrent-program and user audit tracking.

Common Use Cases and Queries

Typical uses include identifying which event types are enabled for a given application and event class, validating accounting and tax eligibility before posting, and building diagnostic reports when subledger events fail to generate accounting.

A representative query to list enabled event types for an application and event class:

• SELECT EVENT_CLASS_CODE, EVENT_TYPE_CODE, ACCOUNTING_FLAG, TAX_FLAG, ENABLED_FLAG FROM XLA.XLA_EVENT_TYPES_B WHERE APPLICATION_ID = :app_id AND EVENT_CLASS_CODE = :class_code AND ENABLED_FLAG = 'Y' ORDER BY EVENT_TYPE_CODE;

To confirm the unique business key and detect duplicates, query by APPLICATION_ID and EVENT_TYPE_CODE using the U2 index columns. Reporting use cases include reconciliation of configured event types against those actually encountered in XLA_EVENTS, and impact analysis before enabling or disabling an event type that drives accounting for downstream transactions.

Related Objects

• XLA_EVENTS — the transactional event table that references configured event types by APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE, making XLA_EVENT_TYPES_B the definition source for runtime events.
• XLA_EVENT_CLASSES_B — defines the event classes to which each event type belongs; joined on APPLICATION_ID and EVENT_CLASS_CODE.
• XLA_EVENT_TYPES_TL — the translation table supplying language-specific names and descriptions for event types, joined on the same composite business key.
• XLA_EVENT_CLASSES_TL — provides translated event class descriptions used alongside event type reporting.
• XLA_ENTITY_TYPES_B — defines the entities referenced by ENTITY_CODE within the XLA configuration model.
• XLA_ACCOUNTING_EVENTS and the XLA accounting program APIs — consume enabled event types when generating and posting subledger journal entries.