Search Results ar_autorec_api




Overview
Explore in AI Chat

Overview

AR_AUTOREC_API is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Receivables. It implements the AutoReceipts engine, the mechanism by which Oracle Receivables automatically creates receipt records and applies them against open customer transactions. AutoReceipts is used primarily to streamline high-volume cash application processing, where receipts are generated in bulk and matched to invoices using predefined rules rather than through manual data entry in the Receipts window. The package was designed to support both the standard concurrent-program-driven AutoReceipts flow and callable interfaces from other Receivables APIs.

The package holds a VALID status in the ETRM 12.2.2 data dictionary and is classified as an API. Its declared dependency footprint spans core Receivables tables (AR_BATCHES, AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_PAYMENT_SCHEDULES, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS), Trading Community Architecture tables (HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES), transaction tables (RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES), and financials infrastructure tables (AP_PAYMENT_PROGRAMS, plus the AutoReceipts working tables AR_AUTOREC_EXCEPTIONS, AR_AUTOREC_INTERIM, and AR_BATCHES_ALL).

Key Procedures and Functions

  • GET_PARAMETERS — Retrieves the controlling parameters for an AutoReceipts run, including batch attributes, receipt class and method information, and matching criteria that govern how invoices are selected.
  • SUBMIT_AUTOREC_PARALLEL — Submits the AutoReceipts process in parallel mode, coordinating concurrent workers so that large volumes of receipts can be generated across multiple processes. This is the primary entry point used by the AutoReceipts concurrent program.
  • INSERT_BATCH — Creates the AutoReceipts batch record in AR_BATCHES / AR_BATCHES_ALL using the parameters established for the run.
  • SELECT_VALID_INVOICES — Identifies the candidate open invoices that satisfy AutoReceipts selection criteria, drawing on transaction and payment-schedule data.
  • INSERT_EXCEPTIONS — Records invoices or transactions that fail AutoReceipts matching rules into the exceptions table, providing a diagnostic trail for application failures.
  • SUBMIT_REPORT — Launches the associated AutoReceipts report so that users can review the results of the run for audit and reconciliation purposes.
  • REC_RESET — Resets prior AutoReceipts state, allowing the process to be re-run cleanly without residual data from a previous execution.
  • GET_INVOICE_BAL_AFTER_DISC — Returns the invoice balance after accounting for applicable discounts, ensuring that applied receipt amounts reflect the discounted outstanding balance.
  • POPULATE_CACHED_DATA — Loads reference data (receipt methods, classes, customer information, transaction types) into package-level caches to reduce repeated queries during the AutoReceipts run.

Tables Accessed

The package writes receipt and batch records into AR_BATCHES, AR_BATCHES_ALL, and AR_CASH_RECEIPTS, with lifecycle tracking in AR_CASH_RECEIPT_HISTORY. Invoice and balance determination relies on AR_PAYMENT_SCHEDULES, RA_CUSTOMER_TRX, and RA_CUST_TRX_TYPES. Customer context comes from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_PARTIES. Receipt configuration is drawn from AR_RECEIPT_CLASSES and AR_RECEIPT_METHODS. AutoReceipts-specific working storage is held in AR_AUTOREC_EXCEPTIONS and AR_AUTOREC_INTERIM, while AP_PAYMENT_PROGRAMS is referenced for shared payment-related lookups.

Usage Notes

AR_AUTOREC_API is typically invoked indirectly through the AutoReceipts concurrent program rather than called directly by end users. It is referenced by ARP_PROCESS_APPLICATION, AR_PREPAYMENTS, AR_RECEIPT_API_PUB, and AR_RECEIPT_LIB_PVT, indicating that it plays a supporting role in receipt creation, prepayment handling, and application logic. Custom code that needs to automate bulk receipt generation should generally call the public receipt APIs (such as AR_RECEIPT_API_PUB) rather than invoking AR_AUTOREC_API procedures directly, since the internal procedures assume the full AutoReceipts orchestration context. When tracing AutoReceipts-run failures, querying AR_AUTOREC_EXCEPTIONS is the standard diagnostic starting point.