Search Results create_payment_extension

Overview

ARP_PROCESS_CHARGEBACK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Receivables (Release 12.1.1 and 12.2.2). It encapsulates the core business logic required to create, maintain, reverse, and delete chargebacks within the Oracle Receivables transaction and receipt lifecycle. A chargeback arises when a customer deducts an amount from a payment against one transaction and the remaining balance is transferred onto a new debit item, effectively converting an unpaid receivable into a distinct chargeback transaction. In the ETRM metadata this package is classified as API type OTHER, is listed with a VALID status, and is referenced by two other packages: ARP_CHARGEBACK_COVER and ARP_PROCESS_APPLICATION.

Key Procedures and Functions

The documented package exposes eight procedures and functions, which collectively manage the full chargeback operation:

• REVISION — Performs revision processing against a chargeback, allowing adjustments to an existing chargeback record without full reversal.
• REVERSE_CHARGEBACK — Undoes a previously created chargeback, restoring the underlying receivable relationship.
• VALIDATE_CB_REVERSAL — Validates whether a chargeback is eligible for reversal before the reversal is executed, enforcing Receivables business rules.
• CREATE_CHARGEBACK — Creates a new chargeback transaction, establishing the debit item and its associated payment schedule.
• UPDATE_CHARGEBACK — Modifies an existing chargeback record when corrections are required.
• DELETE_CHARGEBACK — Removes a chargeback and its supporting accounting/distribution artifacts.
• CREATE_PAYMENT_EXTENSION — Generates the payment extension associated with the chargeback, ensuring the receivable and corresponding payment schedule remain aligned.
• REVISION (function form) — The same identifier is documented as both a procedure/function entry, indicating a public callable used for revision handling.

Tables Accessed

Through APPS synonyms, the package reads and writes core Receivables and Trading Community tables. Transaction-side tables include RA_CUSTOMER_TRX, AR_ADJUSTMENTS, AR_PAYMENT_SCHEDULES, AR_MEMO_LINES, and AR_RECEIVABLES_TRX. Receipt-side tables include AR_CASH_RECEIPTS, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, and AR_RECEIVABLE_APPLICATIONS. Customer and party data are drawn from the HZ schema tables HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. These references support chargeback creation (debit item and payment schedule), adjustment and memo-line reversal, and reconciliation to the originating customer site and receipt.

Usage Notes

ARP_PROCESS_CHARGEBACK is not intended to be called directly by end users. It is normally invoked implicitly by the standard Receivables forms and concurrent programs, particularly during chargeback entry in the Transactions and Receipts windows, and by the ARP_CHARGEBACK_COVER and ARP_PROCESS_APPLICATION packages that act as orchestration layers. Custom integrations that require creating, reversing, or deleting chargebacks should call the documented public procedures rather than performing direct DML against the underlying tables, preserving the validation and accounting logic enforced by VALIDATE_CB_REVERSAL and the related entry points. Because the package name is shared with a foreign-key style dependency entry, developers verifying dependencies in ETRM should note the package is both a referenced and referencing object.