Search Results create_application_event
Overview
ARP_XLA_EVENTS is a core Oracle EBS Receivables (AR) package that bridges subledger accounting and the eBusiness Tax Reporting and Accounting (XLA) engine. It is responsible for creating, managing, and maintaining subledger accounting events that originate from the Receivables transactional tables. In Oracle EBS 12.1.1 and 12.2.2, the SLA (Subledger Accounting) architecture requires that every accounting-relevant business activity in Receivables — a transaction, adjustment, cash receipt, or miscellaneous receipt — generate a corresponding event in the XLA_EVENTS table. ARP_XLA_EVENTS is the documented mechanism that performs this event creation, denormalization, and the reverse cleanup required when events are modified or removed.
The package supports multiple processing modes, as reflected in its xla_events_type record definition, which carries an xla_mode flag distinguishing upgrade, OLTP, and batch modes, and an xla_call flag controlling whether event creation, denormalization, or both are executed. This design allows the same package to service real-time transaction entry as well as large-scale batch and upgrade processing.
Key Procedures and Functions
The documented package exposes six internal procedures and functions:
- CREATE_EVENTS — The principal entry point. It forks processing based on input parameters and creates accounting events for a given document, spanning the supported document types such as transactions, adjustments, and receipts.
- CREATE_EVENTS_REQ — The request-driven variant of event creation. This is the procedure invoked in a concurrent processing context, allowing events to be generated in bulk across documents selected by a request ID, consistent with the
xla_req_idfield in thexla_events_typerecord. - CREATE_EVENTS_DOC — Creates events for a single, specific document identified by document ID, used for targeted or online processing.
- DELETE_EVENT — Removes an accounting event, typically when the underlying transaction or distribution is altered or reversed and the prior event is no longer valid.
- DELETE_REVERSE_REVREC_EVENT — Handles deletion and reversal of reversal-related events, ensuring that Reversal Reversal (RevRec) style corrections are properly unwound in the SLA event stream.
- AR_XLA_PERIOD_CLOSE — Supports period-close activity within the Receivables-to-XLA event cycle, ensuring events are fully processed before a period is closed.
Tables Accessed
The package reads and writes Receivables transactional data through APPS synonyms. Document and transaction sources include RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_ALL (transaction headers and lines), AR_ADJUSTMENTS and AR_ADJUSTMENTS_ALL (adjustments), AR_CASH_RECEIPTS_ALL and AR_CASH_RECEIPT_HISTORY(_ALL) (receipts and their status history), AR_MISC_CASH_DISTRIBUTIONS(_ALL), and AR_RECEIVABLE_APPLICATIONS(_ALL) (application and unapplication activity). AR_TRANSACTION_HISTORY(_ALL) and AR_SYSTEM_PARAMETERS provide supporting context. DBMS_SQL appears as a referenced object because the package relies on dynamic SQL and bulk array fetching, consistent with the DBMS_SQL.VARCHAR2_TABLE and NUMBER_TABLE columns declared in the ev_rec_type record used for high-volume batch processing.
Usage Notes
ARP_XLA_EVENTS is invoked internally by the Receivables Subledger Accounting process rather than being an end-user API. In OLTP mode it fires as accounting-relevant operations are committed during form-based transaction entry, receipt application, and adjustment. In batch mode it is driven through concurrent programs such as the Receivables SLA event creation request, where CREATE_EVENTS_REQ retrieves documents by request ID. Because the package is referenced by 36 other packages, customizations should avoid modifying it directly and should instead rely on the documented XLA event APIs. Implementers diagnosing missing or duplicate accounting events, subledger period-close discrepancies, or reversals in 12.1.1 and 12.2.2 commonly trace issues to this package and its supporting tables.