Search Results arp_chargeback_cover




Overview
Explore in AI Chat

Overview

ARP_CHARGEBACK_COVER is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its business purpose is to support the chargeback creation process within Oracle Receivables. A chargeback arises when a customer disputes all or part of an invoice, and the disputed amount is transferred from the original invoice to a new chargeback transaction, effectively reversing the receivable against the original document and re-establishing it as a new, separately tracked item. The package encapsulates the server-side logic required to perform this transfer in a controlled, API-compliant manner.

The package is classified in the ETRM repository as an OTHER-type API rather than a formally published public API. This classification indicates that it is an internal utility package, typically invoked by other Receivables components rather than being called directly by external integrations. Its status is recorded as VALID, confirming that it compiles and is present in the database. The package contains both a specification and a body, with the body containing the executable PL/SQL, and it is registered as a dependency-consuming object that references several core Receivables tables and the FND_API utility package.

Key Procedures and Functions

The documented metadata lists a single procedure or function: CREATE_CHARGEBACK. As the name suggests, this routine is responsible for driving the creation of a chargeback record. In the standard Receivables flow, the chargeback process involves reversing the disputed portion of the original transaction through the receivables applications table and inserting a new chargeback transaction in RA_CUSTOMER_TRX. The procedure orchestrates these steps, applying the appropriate transaction type, payment terms, and accounting rules.

No parameter list is documented in the ETRM metadata, and therefore none is reproduced here. The procedure is understood to accept the identifying context of the original transaction and the disputed amount, along with any relevant application and customer information required to build the replacement transaction. The dependency declarations confirm that ARP_CHARGEBACK_COVER references ARP_CHARGEBACK_COVER itself (recursive or overloaded references within the package), FND_API, and the Receivables tables identified below.

Tables Accessed

The package accesses a broad set of Receivables and Trading Community tables, consistent with the data requirements of chargeback creation. AR_RECEIVABLE_APPLICATIONS is read and written to reverse the disputed amount on the original invoice and to record the application of the chargeback. RA_CUSTOMER_TRX is inserted into for the new chargeback transaction header and lines, and RA_CUST_TRX_TYPES is read to determine the correct chargeback transaction type. AR_PAYMENT_SCHEDULES is updated to reflect the revised installments and balances on the original transaction.

AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY are referenced to preserve the linkage between the chargeback and the receipt activity that prompted the dispute. AR_SYSTEM_PARAMETERS provides operating configuration such as the chargeback transaction type and accounting defaults. FND_DOCUMENT_SEQUENCES supplies the document numbering for the new chargeback transaction. The customer and address context is resolved through HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTY_SITES, and HZ_LOCATIONS, ensuring that the chargeback inherits the correct bill-to and site information. Collectively these tables represent the full complement of data needed to create and account for a chargeback without leaving the transaction in an inconsistent state.

Usage Notes

ARP_CHARGEBACK_COVER is referenced by one other package, OZF_AR_PAYMENT_PVT, which places it within the Oracle Trade Management and Receivables payment integration path. It is not typically invoked directly from a concurrent program or a standard Receivables form; instead it is called programmatically by these higher-level packages when a chargeback must be raised as part of deduction or dispute resolution processing. Custom code should treat it as an internal API and avoid direct invocation, because the procedure assumes the surrounding transaction context is already established and may rely on package state or session settings maintained by the caller. Implementers extending chargeback functionality should call the supported Receivables APIs or the invoking trade management package rather than ARP_CHARGEBACK_COVER itself, and should verify behavior against the target release, since the package body is edition-sensitive across 12.1.1 and 12.2.2.