Search Results ra_cust_receipt_methods

Overview

The RA_CUST_RECEIPT_METHODS table is a core data object within the Oracle E-Business Suite Receivables (AR) module. It functions as the central repository for storing and managing the assignment of payment methods to customers and their specific business locations (sites). This assignment is a critical configuration step that determines the acceptable forms of payment (e.g., Check, Credit Card, Wire Transfer) for a given customer transaction. The table enables a flexible hierarchy, allowing payment methods to be defined at the overall customer level or overridden at a more granular ship-to or bill-to site level, thereby enforcing and streamlining the cash application process.

Key Information Stored

The table's structure is designed to link customer, site, and payment method entities. Its primary and unique keys enforce critical business rules. The primary identifier is the system-generated CUST_RECEIPT_METHOD_ID. The unique key constraint (RA_CUST_RECEIPT_METHODS_UK1) on the combination of CUSTOMER_ID, SITE_USE_ID, and RECEIPT_METHOD_ID ensures that a specific payment method cannot be duplicated for the same customer and site. The CUSTOMER_ID column references the Trading Community Architecture's HZ_CUST_ACCOUNTS table. The SITE_USE_ID links to the customer site uses table (HZ_CUST_SITE_USES_ALL), and a NULL value in this field typically indicates a customer-level default. The RECEIPT_METHOD_ID is a foreign key to the AR_RECEIPT_METHODS table, which defines the master list of available payment methods in the system.

Common Use Cases and Queries

This table is central to operations involving customer setup, transaction entry, and receipt creation. A common reporting need is to list all payment methods assigned to a specific customer, including site-level assignments. The following query demonstrates this pattern:

• SELECT hca.account_number, hcsua.location, arm.name receipt_method_name FROM ra_cust_receipt_methods rcrm, hz_cust_accounts hca, hz_cust_site_uses_all hcsua, ar_receipt_methods arm WHERE rcrm.customer_id = hca.cust_account_id AND rcrm.site_use_id = hcsua.site_use_id(+) AND rcrm.receipt_method_id = arm.receipt_method_id AND hca.account_number = 'CUST123';

Another critical use case is validation during automated payment processing or manual receipt entry, where the system queries this table to verify if the payment method selected for a transaction is valid for the given customer and site. Troubleshooting payment method errors on invoices or receipts often involves verifying the existence and correctness of records in this table.

Related Objects

As indicated by its foreign keys, RA_CUST_RECEIPT_METHODS has direct dependencies on several fundamental AR and TCA tables. It is a child table to AR_RECEIPT_METHODS (master payment methods), HZ_CUST_ACCOUNTS (TCA customer definition), and HZ_CUST_SITE_USES_ALL (customer sites). In application logic, it is closely tied to the Receivables API for managing customer profiles. Data from this table is often surfaced in standard forms like the Customer Standard and Site Classifications forms, and it is integral to the underlying views that support the Receivables user interface for defining customer payment options.