Search Results ap_bank_branches




Overview
Explore in AI Chat

Overview

The AR_CASH_RECEIPTS_ALL table is the central repository for detailed receipt information within Oracle E-Business Suite Receivables (AR) module. It stores the core transactional data for every cash receipt entered into the system, regardless of its processing status. As a multi-organization table (indicated by the "_ALL" suffix), it contains data for all operating units, making it the primary table for enterprise-level reporting and integration. Each record represents a single receipt transaction, which may be in the form of cash, checks, credit cards, or electronic funds transfers. The table's integrity is maintained through its primary key, AR_CASH_RECEIPTS_PK, on the CASH_RECEIPT_ID column, and it serves as the foundation for the entire cash application and reconciliation process.

Key Information Stored

The table's columns capture the complete lifecycle of a receipt. The primary identifier, CASH_RECEIPT_ID, uniquely defines each transaction. Critical business attributes include RECEIPT_NUMBER, AMOUNT, CURRENCY_CODE, and RECEIPT_DATE. The table links to major master data entities through foreign keys: PAY_FROM_CUSTOMER references the customer (HZ_CUST_ACCOUNTS), RECEIPT_METHOD_ID defines the processing rules (AR_RECEIPT_METHODS), and SET_OF_BOOKS_ID ties the receipt to its ledger (GL_SETS_OF_BOOKS_11I). For bank transactions, columns like REMITTANCE_BANK_ACCOUNT_ID (AP_BANK_ACCOUNTS_ALL) and CUSTOMER_BANK_ACCOUNT_ID (IBY_EXT_BANK_ACCOUNTS) are crucial. Status is managed via columns such as STATUS ('APP', 'UNAPP', 'REV', 'NSF', 'STOP') and TYPE ('CASH', 'MISC').

Common Use Cases and Queries

This table is essential for operational reporting, audit inquiries, and data fixes. Common scenarios include analyzing unapplied or unidentified receipts, tracing receipt history for a customer, and reconciling bank statements. A typical query to find unapplied receipts for a specific customer would join AR_CASH_RECEIPTS_ALL to HZ_CUST_ACCOUNTS on PAY_FROM_CUSTOMER and filter on STATUS = 'UNAPP'. For period-end close, reports summarizing receipt activity by currency, receipt method, or operating unit (using ORG_ID) are generated from this table. Technical consultants often query it to diagnose payment application issues or to extract data for custom cash forecasting reports. The unique key constraint on PAY_FROM_CUSTOMER, RECEIPT_NUMBER, and AMOUNT (AR_CASH_RECEIPT_UK1) is critical to understand when troubleshooting duplicate receipt errors.

Related Objects

AR_CASH_RECEIPTS_ALL has extensive relationships within the Receivables schema. It is the parent table for key transactional tables: AR_CASH_RECEIPT_HISTORY_ALL stores status changes, AR_RECEIVABLE_APPLICATIONS_ALL records applications to transactions, and AR_PAYMENT_SCHEDULES_ALL holds the resulting accounting entries. As shown in the metadata, it references numerous control and master tables, including AR_BATCHES_ALL for remittance processing and AR_RECEIVABLES_TRX_ALL for miscellaneous receipts. The AR_CASH_RECEIPTS_ALL table is also accessed through public APIs, such as AR_RECEIPT_API_PUB, and is the base for important views like AR_CASH_RECEIPTS_V for reporting. Its relationship with CE_BANK_ACCT_USES_ALL and IBY_FNDCPT_TX_EXTENSIONS highlights its integration with Cash Management and the Payments modules.