Search Results xla_event_sources_pk

Overview

The XLA_EVENT_SOURCES table is a core configuration object in the Subledger Accounting (XLA) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the mapping of accounting sources assigned to a given event class or event entity. In the Subledger Accounting architecture, an accounting event is decomposed into an event class and event entity, and each of these carries a defined set of sources — the data elements such as amounts, currencies, dates, and identifiers that feed the journal entry creation process. XLA_EVENT_SOURCES records precisely which of those sources are available and applicable for each event class or event entity combination.

The table is owned by the XLA schema and holds 14 documented columns. From a heuristic Data Vault modeling perspective, the FK structure classifies this object as standalone. This reflects the fact that the table functions as a reference or configuration entity rather than as a transactional hub, link, or satellite dependent on foreign-key relationships. It defines the structural relationship between event definitions and the source data they expose.

Key Information Stored

The primary key, XLA_EVENT_SOURCES_PK, is a composite surrogate key comprising six columns: APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, SOURCE_TYPE_CODE, SOURCE_APPLICATION_ID, and SOURCE_CODE. This combination uniquely identifies each source assignment record.

• APPLICATION_ID — identifies the application or product that owns the event class or entity definition.
• ENTITY_CODE — the event entity code against which the source is assigned.
• EVENT_CLASS_CODE — the event class code that groups related business events.
• SOURCE_TYPE_CODE — categorizes the source, for example distinguishing system-level from other source classifications.
• SOURCE_APPLICATION_ID — the application that owns the source definition.
• SOURCE_CODE — the identifier of the source being assigned.
• ACTIVE_FLAG — indicates whether the source assignment is currently active for the event class or entity.
• LEVEL_CODE — denotes the level at which the source applies, such as event class or entity granularity.

A unique index, XLA_EVENT_SOURCES_U1, covers the business-key candidate columns APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, SOURCE_APPLICATION_ID, SOURCE_TYPE_CODE, SOURCE_CODE, and ZD_EDITION_NAME. The additional ZD_EDITION_NAME column in the unique index supports edition-based reference data management in Release 12.2.2. Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — track record lifecycle and change history.

Common Use Cases and Queries

Typical use cases include troubleshooting journal entry generation, auditing which sources are enabled for an event class, and building custom reporting on subledger configuration. A representative query retrieves active sources for a specific event class:

• SELECT source_code, source_type_code, source_application_id FROM xla_event_sources WHERE application_id = :app_id AND event_class_code = :ec_code AND entity_code = :ent_code AND active_flag = 'Y';
• Comparing source assignments across environments or releases by filtering on LEVEL_CODE to isolate event-class versus entity-level definitions.
• Joining to source definition tables to obtain descriptive names for reporting on configured accounting rules.

Related Objects

• XLA_EVENT_CLASSES — joined by APPLICATION_ID and EVENT_CLASS_CODE.
• XLA_EVENT_ENTITIES — joined by APPLICATION_ID, EVENT_CLASS_CODE, and ENTITY_CODE.
• XLA_SOURCES (and the related source definition view) — joined by SOURCE_APPLICATION_ID and SOURCE_CODE.
• XLA_EVENTS — the transactional event table populated using configured sources.
• XLA_AE_HEADERS / XLA_AE_LINES — downstream accounting entry tables that consume the source values.