Search Results calling_sequence

Overview

AP_XLA_EVENTS_PKG is a PL/SQL package body owned by the APPS schema that provides the core event-management infrastructure for the subledger accounting (XLA) architecture within Oracle Payables. In Oracle EBS 12.1.1 and 12.2.2, Subledger Accounting captures accounting events generated by Payables transactions — invoices, payments, adjustments, and related activity — and transforms them into journal entries through the Create Accounting process. AP_XLA_EVENTS_PKG serves as the internal API layer through which Payables creates, maintains, and queries those accounting events before they are passed to the XLA engine.

The package is classified as OTHER in the ETRM API classification, indicating that it is a supporting internal package rather than a formally published integration API. Its primary dependencies are APP_EXCEPTION for error handling, AP_DEBUG_PKG for diagnostic logging, and XLA_EVENTS_PUB_PKG, the public XLA package that performs the actual event persistence into the XLA_EVENTS table. This layering confirms that AP_XLA_EVENTS_PKG acts as an AP-specific wrapper around the generic XLA event public API.

Key Procedures and Functions

The documented program units (12 total) include the following procedures and functions:

• CREATE_EVENT — Creates a new subledger accounting event in the XLA event model for a Payables transaction, establishing the event record that subsequent accounting generation will process.
• UPDATE_EVENT — Modifies attributes of an existing event, typically when the source transaction data changes prior to accounting.
• UPDATE_EVENT_STATUS — Changes the processing status of an event, for example marking it as processed, unprocessed, or in error during the accounting cycle.
• DELETE_EVENT — Removes a single event record, used when the underlying transaction is reversed or purged.
• DELETE_EVENTS — Performs bulk deletion of event records, supporting cleanup of groups of events associated with a transaction or accounting period.
• GET_EVENT_INFO — Retrieves detailed attribute information for an event, returning the data needed by callers to inspect or reprocess the event.
• GET_ARRAY_EVENT_INFO — Performs a bulk (array-based) retrieval of event information, optimized for processing multiple events in a single call.
• GET_EVENT_STATUS — Returns the current status of an event without retrieving the full event record.
• EVENT_EXISTS — A Boolean-style check that determines whether an event already exists for a given transaction, preventing duplicate event creation.

These units collectively provide the create, read, update, and delete operations required to manage the lifecycle of Payables accounting events.

Tables Accessed

The ETRM metadata does not enumerate specific tables referenced directly through APPS synonyms. However, given the package's dependency on XLA_EVENTS_PUB_PKG, the underlying data manipulation is performed against the XLA event tables — principally XLA_EVENTS and its associated header and line tables — via the XLA public API rather than through direct DML. The package therefore reads and writes event data indirectly, relying on XLA_EVENTS_PUB_PKG to persist and query the XLA_EVENTS records while AP_XLA_EVENTS_PKG manages AP-specific validation, status transitions, and error handling.

Usage Notes

AP_XLA_EVENTS_PKG is not referenced by any database object according to the ETRM dependency listing, but the documented 12.2.2 metadata states that it is referenced by three other packages. This indicates that it is invoked internally by other APPS packages rather than exposed as a standalone entry point. In practice, the package is called during Payables transaction processing — invoice validation, payment processing, and the Create Accounting concurrent program — whenever an accounting event must be created, updated, or queried. Because it is an internal package, Oracle does not guarantee its signature across releases, and customizations should favor the public XLA APIs. Developers maintaining or debugging Payables accounting events may reference this package to understand how event lifecycle operations are implemented, but direct invocation in custom code is not recommended.