Search Results ar_autorec_exceptions




Overview
Explore in AI Chat

Overview

The AR_AUTOREC_EXCEPTIONS table is a core technical object within Oracle E-Business Suite Receivables (AR) modules, specifically for versions 12.1.1 and 12.2.2. It functions as a temporary staging and logging table for the Automatic Receipts program and its related processes. The primary role of this table is to capture and persist detailed exception records generated when the system encounters issues during the automated creation of receipts from incoming payments, such as electronic bank statement lines. These exceptions must be reviewed and resolved by users before the associated funds can be successfully applied, ensuring data integrity in the receivables cycle.

Key Information Stored

The table stores a comprehensive record for each exception, keyed by a composite primary key (BATCH_ID, REQUEST_ID, EXCEPTION_CODE). Critical columns include BATCH_ID, linking to the AR_BATCHES_ALL table, and REQUEST_ID, linking to the concurrent request in FND_CONCURRENT_REQUESTS. The EXCEPTION_CODE defines the nature of the failure. Other significant columns reference the specific business entities involved in the failed transaction: PAYMENT_SCHEDULE_ID (the invoice), PAYING_CUSTOMER_ID and PAYING_SITE_USE_ID (the customer and site), and CUST_BANK_ACCT_ID (the customer's bank account). Crucially, it also stores bank account references for the remittance bank via REMIT_BANK_ACCT_ID (AP_BANK_ACCOUNTS_ALL) and REMIT_BANK_ACCT_USE_ID (CE_BANK_ACCT_USES_ALL), directly linking to the object referenced in the user's search.

Common Use Cases and Queries

The primary use case is troubleshooting and resolving automatic receipt failures. Administrators and AR specialists query this table to generate exception reports, often filtered by batch or request ID. A typical diagnostic query joins to related customer and transaction tables to provide context for resolution.

  • Sample Query for Exception Analysis:
    SELECT exc.*, cust.account_number, ps.trx_number
    FROM ar_autorec_exceptions exc,
         hz_cust_accounts cust,
         ar_payment_schedules_all ps
    WHERE exc.paying_customer_id = cust.cust_account_id
    AND exc.payment_schedule_id = ps.payment_schedule_id
    AND exc.request_id = :conc_request_id
    ORDER BY exc.exception_code;
  • Reporting Use Case: Identifying exceptions related to specific remittance bank accounts by querying on REMIT_BANK_ACCT_ID, which is essential for bank reconciliation and cash management processes.

Related Objects

As indicated by its foreign key constraints, AR_AUTOREC_EXCEPTIONS has strong dependencies on several fundamental EBS tables. It is directly linked to transaction batches (AR_BATCHES_ALL), customer data (HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL), and invoice schedules (AR_PAYMENT_SCHEDULES_ALL). Its connection to banking structures is particularly notable, with foreign keys to both the Accounts Payable bank account definition (AP_BANK_ACCOUNTS_ALL) and the Cash Management bank account use (CE_BANK_ACCT_USES_ALL). This positions the table at the intersection of Receivables, Cash Management, and Treasury operations. The table is populated and managed by the underlying Automatic Receipts engine and related concurrent programs.