Search Results arp_xla_events




Overview
Explore in AI Chat

Overview

ARP_XLA_EVENTS is a PL/SQL package body owned by the APPS schema that serves as the Receivables (AR) subledger integration layer for Oracle Subledger Accounting (SLA/XLA). Its principal business function is to identify, construct, and register accounting events that the Receivables application must forward to Subledger Accounting for journal creation. When transactions, receipts, adjustments, or miscellaneous cash distributions occur in Receivables, they must be mapped to an XLA transaction entity and an XLA event before accounting can be generated. ARP_XLA_EVENTS performs this prerequisite work by inspecting the underlying AR tables and invoking the standard XLA event creation APIs. The package is classified in ETRM as "OTHER" — an internal utility package rather than a formally published public API — and is documented as VALID in release 12.2.2 and compatible with 12.1.1.

Key Procedures and Functions

  • CREATE_EVENTS — Creates SLA events for Receivables transactions and related sources. This is the core routine that evaluates eligible AR records and builds the corresponding XLA event rows.
  • CREATE_EVENTS_REQ — A request-mode variant of event creation, intended for invocation in a concurrent program context where large volumes of events are processed.
  • CREATE_EVENTS_DOC — A document-level variant that creates SLA events for a specific transaction document, supporting targeted rather than bulk processing.
  • DELETE_EVENT — Removes an XLA event associated with an AR activity, used when the underlying transaction is reversed or no longer requires accounting.
  • DELETE_REVERSE_REVREC_EVENT — Handles deletion and reversal of events tied to reversed or unreversed receipt scenarios, ensuring Subledger Accounting remains consistent with receipt reversal activity.
  • AR_XLA_PERIOD_CLOSE — Supports period-close processing by validating or finalizing XLA events for the Receivables subledger before the accounting period is closed.

Tables Accessed

The package reads and writes across the principal Receivables transaction and receipt tables. Transaction sources include RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES, RA_CUST_TRX_LINE_GL_DIST, and RA_CUST_TRX_LINE_GL_DIST_ALL, which supply invoice and credit memo data. Receipt-related processing draws on AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY, AR_CASH_RECEIPT_HISTORY_ALL, AR_RECEIVABLE_APPLICATIONS, and AR_RECEIVABLE_APPLICATIONS_ALL. Adjustments are read from AR_ADJUSTMENTS and AR_ADJUSTMENTS_ALL, while miscellaneous receipts come from AR_MISC_CASH_DISTRIBUTIONS and AR_MISC_CASH_DISTRIBUTIONS_ALL. AR_TRANSACTION_HISTORY and AR_TRANSACTION_HISTORY_ALL provide transaction lifecycle history. Setup and control values are obtained from AR_SYSTEM_PARAMETERS, ARP_GLOBAL, ARP_STANDARD, and profile options via FND_PROFILE. The package writes to and reads from XLA_EVENTS, XLA_EVENTS_INT_GT, and XLA_EVENTS_PUB_PKG, and uses DBMS_SQL for dynamic statement execution. XLA_TRANSACTION_ENTITIES provides the entity registration needed before events can be created.

Usage Notes

ARP_XLA_EVENTS is an internal Receivables-to-SLA bridge and is not intended as a general-purpose public API. In normal operation it is invoked automatically by Receivables when accounting must be generated — typically through transaction and receipt processing, the Create Accounting concurrent program, or period-close activities. The CREATE_EVENTS_REQ entry point supports concurrent, set-based processing for high-volume event generation, whereas CREATE_EVENTS_DOC supports document-specific handling. Because the package is documented as not referenced by any database object, it is a top-level driver rather than a dependency of other stored code; however, it is itself referenced by roughly thirty-six other packages within the E-Business Suite. Customizations should generally avoid calling this package directly; instead they should rely on the supported XLA public APIs (XLA_EVENTS_PUB_PKG) and the standard Create Accounting flow. Direct invocation risks leaving the XLA event and transaction entity tables in an inconsistent state relative to the underlying AR transactions.