Search Results ar_batches_all




Overview
Explore in AI Chat

Overview

The AR_BATCHES_ALL table is a core transactional table within the Oracle E-Business Suite Receivables (AR) module, specifically designed to store receipt batch information. It serves as the central repository for all metadata and control attributes associated with the grouping of cash receipts and related transactions. This batching mechanism is fundamental to the efficient processing, reconciliation, and reporting of incoming payments. The table supports a multi-organization architecture, as indicated by the '_ALL' suffix, meaning it stores data for all operating units accessible to a user, with security enforced via the MOAC (Multi-Org Access Control) security profile. Its primary role is to provide a controlled audit trail and workflow management for receipt processing, from initial creation through final posting and remittance.

Key Information Stored

The table's structure captures comprehensive batch details. The primary identifier is BATCH_ID. Key descriptive columns include BATCH_NAME, BATCH_DATE, and BATCH_STATUS, which tracks the batch's lifecycle (e.g., NEW, POSTED, REMITTED). Critical control columns link the batch to its source and processing rules: BATCH_SOURCE_ID (foreign key to AR_BATCH_SOURCES_ALL), LOCKBOX_ID (for automated lockbox processing), and TRANSMISSION_REQUEST_ID (for electronic transmissions). Financial control is maintained through CURRENCY_CODE, CONTROL_AMOUNT, and CONTROL_COUNT. The table also stores bank account details for remittance via REMITTANCE_BANK_ACCOUNT_ID and REMIT_BANK_ACCT_USE_ID, linking to the Cash Management and Payables modules. Additional programmatic control columns like AUTO_PRINT_PROGRAM_ID and AUTO_TRANS_PROGRAM_ID facilitate automated batch processing workflows.

Common Use Cases and Queries

This table is central to receipt batch inquiry, reconciliation, and audit reporting. A common use case is identifying batches in a specific status for a given operating unit to manage workflow. For example, to list unposted batches:

  • SELECT batch_name, batch_date, control_amount FROM ar_batches_all WHERE batch_status = 'NEW' AND org_id = :org_id;

Another frequent scenario is reconciling batch control totals against the sum of actual receipts. This involves joining with AR_CASH_RECEIPTS_ALL:

  • SELECT ab.batch_name, ab.control_amount, SUM(acr.amount) total_receipts FROM ar_batches_all ab JOIN ar_cash_receipts_all acr ON ab.batch_id = acr.batch_id WHERE ab.batch_id = :batch_id GROUP BY ab.batch_name, ab.control_amount;

The table is also essential for tracing the remittance path of receipts, linking through SELECTED_REMITTANCE_BATCH_ID or REMITTANCE_BATCH_ID columns in related transaction tables.

Related Objects

As evidenced by its extensive foreign key relationships, AR_BATCHES_ALL is a hub within the Receivables schema. It is a parent table to core transaction tables including AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_ADJUSTMENTS_ALL, and AR_INTERIM_CASH_RECEIPTS_ALL. It references master data and control tables such as AR_BATCH_SOURCES_ALL, AR_LOCKBOXES_ALL, AR_TRANSMISSIONS_ALL, FND_CURRENCIES, and CE_BANK_ACCT_USES_ALL. Crucially, the batch identifier propagates to key transactional entities like RA_CUSTOMER_TRX_ALL (for invoices selected for remittance) and AR_PAYMENT_SCHEDULES_ALL, creating a critical audit link between receipts, their applications, and the original invoices. This network of relationships underscores the batch's role as a controlling document for financial sub-ledger integrity.