Results for “xla_event_class_predecs_pk”

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

Overview

XLA_EVENT_CLASS_PREDECS is a Subledger Accounting (XLA) configuration table in Oracle E-Business Suite 12.1.1 and 12.2.2. The table is owned by the XLA schema and holds the predecessor relationships that exist between event classes. Within the Oracle Subledger Accounting architecture, each accounting event is classified into an event class—such as invoices, payments, receipts, or journals—and the accounting program derives the appropriate Accounting Method and Subledger Journal Entry rules for that class. The XLA_EVENT_CLASS_PREDECS table records the ordered dependencies through which one event class must be processed or recognized before another, allowing the accounting engine to determine correct sequencing and to support event completion and period-level processes.

The table carries no foreign-key relationship dependencies as documented in the ETRM metadata and is therefore classified as standalone; the heuristic Data Vault classification places it as a standalone structure rather than a hub, link, or satellite. As a modeling suggestion, the business-key pair (APPLICATION_ID, EVENT_CLASS_CODE, PRIOR_EVENT_CLASS_CODE) could serve as a natural link between event classes, but the table itself is maintained directly within the XLA schema and does not participate in documented FK constraints.

Key Information Stored

XLA_EVENT_CLASS_PREDECS contains ten documented columns. The most significant are the three that constitute both the primary key and the business-key candidate:

• APPLICATION_ID — Identifies the owning application (subledger) whose event classes are being related. It scopes every row to a specific application context.
• EVENT_CLASS_CODE — The event class whose predecessor is being defined; this is the dependent class in the relationship.
• PRIOR_EVENT_CLASS_CODE — The predecessor event class that must be accounted for or completed before the dependent class. Together these three columns form XLA_EVENT_CLASS_PREDECS_PK and the unique index XLA_EVENT_CLASS_PREDECS_U1 (with ZD_EDITION_NAME appended). The primary key is the surrogate enforcing uniqueness, while the three-column business key represents the meaningful identifier.
• OBJECT_VERSION_NUMBER — Supports optimistic locking and concurrent update control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO-column audit attributes recording creation and modification details.
• ZD_EDITION_NAME — The editioning column introduced in the 12.2 online patching architecture, indicating the edition in which the row is active.

Common Use Cases and Queries

The table is queried primarily during Subledger Accounting setup, diagnostics, and impact analysis of accounting method changes. Typical patterns include:

• Listing all predecessors for a given event class: SELECT PRIOR_EVENT_CLASS_CODE FROM XLA.XLA_EVENT_CLASS_PREDECS WHERE APPLICATION_ID = :app_id AND EVENT_CLASS_CODE = :code;
• Detecting circular or orphaned predecessor chains across event classes within an application.
• Validating the configured sequence of accounting event processing when journal entries are missing or out of order.
• Joining to event class and application lookups to produce a readable dependency map for documentation or audit.

Because the table is small and configuration-oriented, queries are typically simple equi-joins on APPLICATION_ID and EVENT_CLASS_CODE; no performance tuning beyond the primary key is normally required.

Related Objects

The following objects are the most significant reference or dependency points:

• XLA_EVENT_CLASSES — Joins on APPLICATION_ID and the appropriate event class code column; defines the event class metadata.
• XLA_EVENTS — The transactional accounting events whose processing sequence depends on the predecessor configuration.
• XLA_EVENT_TYPES — Event type definitions associated with each event class.
• XLA_ACCOUNTING_METHODS / XLA_APPLICATION_ACCOUNTING_METHODS — Determine which event classes are active for an application.
• FND_APPLICATION — Resolves APPLICATION_ID to the owning subledger application name.

These objects, combined with XLA_EVENT_CLASS_PREDECS, allow functional and technical consultants to understand and diagnose the ordering of accounting event class processing across Oracle EBS subledgers.