Search Results delete_incomplete_reversal




Overview
Explore in AI Chat

Overview

The APPS.XLA_REVERSE_EVENTS_PUB_PKG package body (xlaprevevt.pkb, version 120.2, last updated 2011/03/11) is an Oracle Subledger Accounting (XLA) public API package that provides the programmatic infrastructure for performing bulk reversal of accounted events. In the Oracle EBS 12.1.1 and 12.2.2 architectures, XLA sits as the accounting engine between subledgers such as Payables, Receivables, Assets, and Projects, and the General Ledger. When a source transaction has already been accounted and subsequently needs to be reversed — for example, a cancelled or corrected event — the reversal must be reflected as a new accounting entry rather than a deletion of the original. This package encapsulates the logic required to generate those reversal accounting entries in volume, rather than one event at a time.

The header comments explicitly state that the package is "mainly for FAH Customer," meaning it was originally delivered to support the Fusion Accounting Hub (FAH) use case, where external or non-standard sources feed events into XLA. Oracle cautions that any Oracle subledger intending to adopt this API should contact XLA Development before implementing, indicating that it is a controlled public interface rather than a freely reusable utility.

Key Procedures and Functions

Two procedures are documented for this package:

  • CREATE_REVERSAL_ACCOUNTING — This is the core routine invoked to generate reversal accounting for accounted events. It drives the creation of the reverse accounting entries corresponding to the original accounted event, ensuring the reversal is processed through the standard XLA accounting pipeline. The name corresponds directly to the user search term create_reversal_accounting.
  • DELETE_INCOMPLETE_REVERSAL — This procedure cleans up reversal records that were not successfully completed. The history note dated 08-MAR-2011 records a change "for Batch wise processing even for Delete_Incomplete_Reversal," indicating the procedure was enhanced to operate in batch mode, permitting efficient removal of incomplete reversal artifacts across many events in a single invocation.

Parameter lists for these procedures are not disclosed in the available metadata and are therefore not reproduced here. Both procedures are classified under the API classification "OTHER" in the ETRM 12.2.2 repository.

Tables Accessed

The ETRM metadata for this object does not enumerate the specific tables referenced through APPS synonyms. Given the package's stated purpose of bulk reversal of accounted events, it operates against the XLA accounting repository — principally the XLA events and accounting entries tables that store accounted events and their corresponding journal lines, along with the reversal-specific control columns maintained within that schema. Because the documented table list is not provided, no specific table names should be assumed beyond those implied by the accounting reversal function.

Usage Notes

This package is not typically surfaced through a standard Oracle EBS form or a seeded concurrent program for end users. It is a public PL/SQL API intended to be invoked by subledger application code or by custom code that has adopted XLA as its accounting engine — most notably FAH-based integrations that process events in bulk. The package includes an internal local trace routine bound to FND_LOG levels (STATEMENT, PROCEDURE, EVENT, EXCEPTION, ERROR, UNEXPECTED) with the module identifier xla.plsql.xla_reverse_events_pub_pkg, allowing diagnostic logging to be enabled via the standard FND logging framework when troubleshooting reversal processing. The metadata records that the package is referenced by zero other packages, confirming it is a top-level entry point rather than a shared library. Because Oracle explicitly requests prior consultation before subledger uptake, consumers should treat the API as controlled and validate behavior against the specific EBS release (12.1.1 or 12.2.2) in use.