Results for “xla_event_types_b_u2”

12 results




Overview
Explore in AI Chat

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

Overview

XLA.XLA_EVENT_TYPES_B is a foundational setup table within the Subledger Accounting (XLA) architecture of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the definition of event types that the accounting engine can recognize and process for a given application, entity, and event class. Each row represents a discrete business activity — such as an invoice validation, a payment creation, or a receipt application — that the Create Accounting program evaluates to determine whether accounting, tax, or both should be generated. Because the table carries the internal flags ACCOUNTING_FLAG, TAX_FLAG, and ENABLED_FLAG, it governs which events are eligible for subledger journal entry creation and which remain dormant in the configuration.

The object resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10 and is owned by the XLA schema. It is designated as Oracle Internal Use Only, meaning supported access is expected through standard Oracle Applications programs and the Subledger Accounting setup user interface rather than direct DML. The metadata suggests a standalone Data Vault classification, indicating the table is not modeled as a dependent hub, link, or satellite but rather as an independent reference entity keyed by its composite business key.

Key Information Stored

The table contains thirteen documented columns. The composite primary key, XLA_EVENT_TYPES_B_PK, spans APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE. Two unique indexes serve as business-key candidates:

  • APPLICATION_ID — the internal numeric identifier of the owning application (for example, Payables or Receivables), forming the leading column of both unique indexes.
  • ENTITY_CODE — the entity within the application to which the event type belongs, such as an invoice or payment entity.
  • EVENT_CLASS_CODE — the event class grouping that organizes related event types.
  • EVENT_TYPE_CODE — the discrete code identifying the business event itself.
  • ACCOUNTING_FLAG — an internal flag indicating whether the event type triggers accounting.
  • TAX_FLAG — an internal flag indicating whether the event type is relevant to tax processing.
  • ENABLED_FLAG — an internal flag controlling whether the event type is active for processing.
  • ZD_EDITION_NAME — the editioning column present in 12.2.x, supporting Online Patching and the AD edition-based redefinition architecture.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture audit lineage for every row.

XLA_EVENT_TYPES_B_U1 enforces uniqueness across APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE, and ZD_EDITION_NAME. XLA_EVENT_TYPES_B_U2 narrows the business key to APPLICATION_ID, EVENT_TYPE_CODE, and ZD_EDITION_NAME, reflecting the user-facing search term that returned this object.

Common Use Cases and Queries

Subledger accounting administrators query this table to audit which event types are enabled for accounting across applications. A typical diagnostic query retrieves all event types for a specific application and entity:

  • 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 ENTITY_CODE = :entity_code;
  • Filtering on ENABLED_FLAG = 'Y' isolates active event types for reconciliation of unexpected accounting entries.
  • Joining to application and entity definition tables resolves APPLICATION_ID and ENTITY_CODE into readable names for reporting.
  • Comparing ACCOUNTING_FLAG and TAX_FLAG values supports troubleshooting of missing tax lines or absent journal entries.

Because the table is internal-use only, reporting should rely on supported views and concurrent programs wherever possible, with direct queries reserved for authorized diagnostic investigation.

Related Objects

The ETRM metadata indicates XLA_EVENT_TYPES_B does not reference other database objects but is itself referenced. Significant related objects include:

  • XLA_EVENT_TYPES_TL — the translatable sibling table holding language-specific event type names and descriptions, joined on APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE.
  • XLA_EVENT_CLASSES_B — the parent event class definition joined on APPLICATION_ID and EVENT_CLASS_CODE.
  • XLA_ENTITY_TYPES_B — the entity definition joined on APPLICATION_ID and ENTITY_CODE.
  • XLA_EVENTS — transaction-level events instantiated from these definitions via APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE.
  • XLA_AE_HEADERS — accounting entries generated when ACCOUNTING_FLAG is set for the originating event type.
  • XLA_ACCOUNTING_OPTIONS / XLA_EVENT_TYPE_ASSIGNMENTS — configuration structures that consume event type definitions to determine accounting behavior.

Care should be taken to preserve the integrity of the composite key when extending or diagnosing this table, as downstream accounting derivation depends heavily on consistent event type identification.