Search Results ar_batch

Overview

FV_APPLY_CASH_RECEIPT is an Oracle E-Business Suite package body owned by APPS and classified under the OTHER API category. Its name reflects its purpose: within the Oracle Fusion Receivables/Public Sector (FV) product family, the package supports the application of interim cash receipts to open transactions such as invoices and debit memos. The header identifier (FVXDCCRB.pls) and internal module naming (fv.plsql.fvxdccrb.fv_apply_cash_receipt.) indicate this is a Receivables-based script that governs the posting of payments against customer balances.

The package is used in both Oracle EBS 12.1.1 and 12.2.2 environments. It operates against the FV_INTERIM_CASH_RECEIPTS staging structures and coordinates with the standard Oracle Receivables cash receipt tables to carry applied amounts forward. Package-level globals such as g_org_id, g_sob_id, g_ErrorFound, and the g_DEBIT_MEMO/g_INVOICE constants establish the operating context and transaction classification used throughout execution.

Key Procedures and Functions

The ETRM metadata documents a single entry point for this package body:

• MAIN — The principal driver routine. It orchestrates the receipt-application process, reading interim receipt records, resolving the corresponding customer and open items, and writing application results. It relies on the package's internal record types (CashReceiptRec, CashReceiptApplicationsRec) and the error-collection structures (ErrorInfoRec/ErrorInfoTbl) to accumulate status and diagnostic information during a run.

Because MAIN is the only documented routine, all business logic—including currency handling, exchange-rate resolution, and error tracking—flows through it. No additional public procedures or functions are exposed by the ETRM definition, so callers interact with the package solely through MAIN.

Tables Accessed

The package reads and writes a well-defined set of Receivables and shared EBS tables via APPS synonyms:

• FV_INTERIM_CASH_RECEIPTS — primary staging source of receipt header data (receipt_number, amount), read during initialization.
• AR_CASH_RECEIPTS / AR_CASH_RECEIPTS_ALL — the standard Receivables receipt tables, queried and updated as applications are finalized.
• AR_RECEIVABLE_APPLICATIONS — records the applied portions of receipts against customer transactions.
• AR_PAYMENT_SCHEDULES — supplies open balance and due-amount information used to validate applications.
• AR_CASH_RECEIPT_HISTORY_ALL — tracks the lifecycle status of each receipt.
• AR_BATCHES — batch context for receipt processes.
• AR_RECEIPT_METHODS — validates the payment method attached to receipts.
• FV_AR_BATCHES / FV_AR_BATCHES_ALL — FV-product batch staging tables.
• FV_FINANCE_CHARGE_CONTROLS — finance-charge configuration affecting application rules.
• CE_BANK_ACCOUNTS — bank account context for receipt validation.
• GL_DAILY_CONVERSION_TYPES — exchange-rate type used for foreign-currency receipts.
• HZ_CUST_ACCOUNTS / HZ_CUST_SITE_USES — customer party and site information used to identify the paying customer.

Usage Notes

FV_APPLY_CASH_RECEIPT is typically invoked programmatically rather than directly by end users. It is called from Receivables batch or lockbox-style processes, customization layers, and FV-specific concurrent programs that stage interim receipts before applying them to transactions. ETRM records show no other packages reference it, meaning it serves as a leaf-level routine invoked from external callers rather than an internal dependency.

When invoking the package, the caller must ensure the operating unit (g_org_id) and set of books (g_sob_id) context are properly established, since these globals govern the scope of application. The package's error collection table is the primary mechanism for detecting failed applications, so callers should inspect it after MAIN returns. The comment referencing g_debug and the presence of internal log-message structures indicate the package supports diagnostic tracing, which is relevant given the search term "debug_init"—developers troubleshooting application failures may enable debug output through the FND debug framework to trace error handling inside MAIN.