Search Results xla_event_class_predecs_u1

Overview

XLA.XLA_EVENT_CLASS_PREDECS is a configuration table within the Subledger Accounting (XLA) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines predecessor relationships between event classes, enabling the Subledger Accounting engine to determine the sequence in which accounting events must occur or be processed. Each row establishes that a given event class is preceded by another event class for a specific application, supporting dependency logic used during event completion and accounting generation.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning it is not heavily integrated into a foreign-key web of dependent entities within the documented relationship data. It functions primarily as a reference or configuration table rather than a transactional hub, link, or satellite. The table is owned by XLA and carries the FND Design Data identifier XLA.XLA_EVENT_CLASS_PREDECS.

The object carries an Oracle Internal Use Only warning, meaning Oracle does not support direct application data access except through standard Oracle Applications programs. Custom reporting should therefore be undertaken cautiously, with attention to supported integration patterns.

Key Information Stored

The table contains 10 documented columns. The most significant are the composite key columns and the standard audit/who columns.

• APPLICATION_ID (VARCHAR2, 15): Internal identifier of the application owning the event class relationship. Part of the business key.
• EVENT_CLASS_CODE (VARCHAR2, 30): The code of the event class that has a predecessor. Part of the business key.
• PRIOR_EVENT_CLASS_CODE (VARCHAR2, 30): The code of the event class that must precede EVENT_CLASS_CODE. Part of the business key.
• OBJECT_VERSION_NUMBER (NUMBER, 15): Standard OVN column used for optimistic locking and concurrency control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN: Standard who columns capturing row creation and last modification audit information.
• ZD_EDITION_NAME (VARCHAR2, 30): Editioning column supporting Oracle EBS 12.2 online patching and edition-based redefinition.

The documented primary key is XLA_EVENT_CLASS_PREDECS_PK defined on (APPLICATION_ID, EVENT_CLASS_CODE, PRIOR_EVENT_CLASS_CODE). The unique index XLA_EVENT_CLASS_PREDECS_U1 — the object referenced in the user's search — extends that key with ZD_EDITION_NAME, making it the edition-aware business-key candidate: (APPLICATION_ID, EVENT_CLASS_CODE, PRIOR_EVENT_CLASS_CODE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical uses include validating event-class sequencing during subledger setup, diagnosing accounting event processing failures, and documenting configuration for audit or migration. A common query retrieves predecessor definitions for a specific application and event class:

• SELECT APPLICATION_ID, EVENT_CLASS_CODE, PRIOR_EVENT_CLASS_CODE FROM XLA.XLA_EVENT_CLASS_PREDECS WHERE APPLICATION_ID = :app_id AND EVENT_CLASS_CODE = :code;
• Join to XLA_EVENT_CLASSES (via EVENT_CLASS_CODE and APPLICATION_ID) to resolve descriptive names instead of codes.
• Filter by ZD_EDITION_NAME when querying in a 12.2 multi-edition environment to isolate the active edition.

Because of the internal-use warning, production queries should be read-only and aligned with Oracle-supported extraction methods.

Related Objects

The documented dependency data indicates XLA.XLA_EVENT_CLASS_PREDECS does not reference any database object directly, but it is referenced by the editioning view XLA_EVENT_CLASS_PREDECS#. Supplemental relationships to consider include:

• XLA_EVENT_CLASSES — references event class codes and application identifiers.
• XLA_EVENTS — accounting events governed by event class sequencing.
• XLA_ACCOUNTING_EVENTS — downstream accounting entries derived from events.
• FND_APPLICATION — joins on APPLICATION_ID for application names.
• FND_USER — joins on CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — joins on LAST_UPDATE_LOGIN.