Search Results correct_funds_error

Overview

ARP_CORRECT_CC_ERRORS is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Receivables (AR) module and provides the procedural infrastructure for detecting, diagnosing, and automatically correcting errors that arise during credit card processing on receivables transactions. Organizations that accept credit card payments through Oracle iPayment or the Receivables payment processing framework frequently encounter authorization declines, settlement mismatches, expired instruments, and funds-related rejections. Rather than requiring collectors to manually resolve each exception, this package exposes a structured set of correction routines that can reauthorize a transaction, retry a failed authorization, substitute an alternate payment instrument, or resolve a funds error and record the corrective action against the originating credit card transaction. Because correction activity must be auditable, the package also maintains error history and notes for every action it performs. The package is classified as OTHER in the ETRM documentation, indicating that it is an internal utility package rather than a formally published public API, and it is referenced directly by three other packages in the Receivables codebase. Its most commonly searched member, the GET_COLLECTOR_NAME function, supports the collection and credit card error workflows by resolving the collector associated with a customer and customer site use.

Key Procedures and Functions

The package exposes nine documented procedures and functions:

• CC_AUTO_CORRECT — The primary concurrent-program entry point. It accepts a request identifier and a mode parameter, and drives the automatic correction cycle for credit card transaction errors that fall within its scope.
• CC_AUTO_CORRECT_COVER — A cover routine that wraps the automatic correction logic, invoked with a request identifier and mode, typically from the concurrent manager.
• OBTAIN_ALTERNATE_PAYMENT — Retrieves or establishes an alternate payment instrument for a credit card transaction that cannot be completed on the original instrument, accepting the transaction identifier, category, and error notes.
• REAUTHORIZE — Re-submits a credit card transaction for authorization, taking the transaction identifier, category, customer bank account identifier, and error notes.
• RETRY — Reattempts processing of a previously failed credit card transaction using the same set of identifying and note parameters as REAUTHORIZE.
• LOCK_TABLE_NOWAIT — Acquires a non-blocking lock on a specified table row using a primary key, optional object version number, table name, and transaction number, protecting correction operations from concurrent modification.
• CORRECT_FUNDS_ERROR — Resolves a funds-related credit card error by applying a corrective action and, where relevant, updating the instrument number and expiration date, with error notes captured for audit.
• GET_COLLECTOR_NAME — A function returning the collector name for a given customer and customer site use. It is used across the credit card error and collections flows to identify the responsible collector.
• CC_MAPPING_EXIST — A function that validates whether a mapping exists for a given credit card error code, transaction category, and receipt method, returning a value that indicates mapping availability.

Tables Accessed

The package operates against core Receivables and shared reference tables. Credit card error mappings are read from AR_CC_ERROR_MAPPINGS, while AR_CC_ERROR_HISTORY stores the audit trail of corrections. Payment records are touched through AR_CASH_RECEIPTS, AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY, AR_RECEIVABLE_APPLICATIONS, and AR_PAYMENT_SCHEDULES. Collector identity for GET_COLLECTOR_NAME is sourced from AR_COLLECTORS, with customer context supplied by HZ_CUSTOMER_PROFILES, HR_ALL_ORGANIZATION_UNITS, and FND_USER. Notes and corrective comments are persisted in AR_NOTES and AR_NOTES_S. Receipt method validation draws on AR_RECEIPT_METHODS, and concurrent request context is read from FND_CONCURRENT_REQUESTS.

Usage Notes

ARP_CORRECT_CC_ERRORS is typically invoked in three ways. First, the CC_AUTO_CORRECT procedure executes as the program unit behind the Receivables "Automatic Correction of Credit Card Errors" concurrent program, with the mode parameter controlling whether corrections are applied or previewed. Second, the correction procedures REAUTHORIZE, RETRY, OBTAIN_ALTERNATE_PAYMENT, and CORRECT_FUNDS_ERROR are called from the Receivables credit card error correction user interface, where a collector selects a failed transaction and chooses a corrective action; GET_COLLECTOR_NAME supplies the collector display in those forms. Third, because the package is referenced by three other packages, custom extensions should call it only after confirming behavior in a non-production environment. GET_COLLECTOR_NAME is safe to invoke read-only, but the correction procedures commit data and should never be called directly from ad hoc scripts outside the supported concurrent or form-driven flows.