Results for “ra_cust_receipt_methods”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RA_CUST_RECEIPT_METHODS is an Oracle Receivables (AR) transaction table that stores the payment (receipt) methods assigned to a specific customer and, optionally, to a specific customer site. It acts as the configuration bridge that restricts or enables the set of receipt methods available for a given customer account, which in turn drives defaulting behavior, validation, and reporting in the Receivables receipt and AutoLockbox processes. Each row effectively answers the question: "For this customer (or this customer's site use), which receipt methods are permitted?"

At the physical level in Oracle E-Business Suite 12.1.1 and 12.2.2, the table resides in the AR schema and is documented in ETRM as VALID with 32 columns. The surrogate primary key is CUST_RECEIPT_METHOD_ID, enforced by constraint RA_CUST_RECEIPT_METHODS_PK. The heuristic Data Vault classification mined from the foreign-key structure is link, suggesting this object is best modeled as a relationship link table that associates parties (customers, site uses) with reference data (receipt methods) rather than as a pure hub or a descriptive satellite.

Key Information Stored

The most operationally significant columns are:

• CUST_RECEIPT_METHOD_ID — the surrogate primary key, populated from the RA_CUST_RECEIPT_METHODS_PK sequence. This is the technical identifier referenced by dependent child records.
• CUSTOMER_ID — foreign key to HZ_CUST_ACCOUNTS, identifying the customer account to which the receipt method assignment applies.
• SITE_USE_ID — foreign key to HZ_CUST_SITE_USES_ALL, identifying the specific customer site use. When populated, the assignment is scoped to that site; when null, it may apply at the account level.
• RECEIPT_METHOD_ID — foreign key to AR_RECEIPT_METHODS, identifying the receipt method being assigned.
• PRIMARY_FLAG — indicates whether the receipt method is the primary (default) method for the customer or site.
• START_DATE and END_DATE — effective dating that governs when the assignment is active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context columns for traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns.

The documented unique index RA_CUST_RECEIPT_METHODS_U1 covers CUST_RECEIPT_METHOD_ID; the composite business key RA_CUST_RECEIPT_METHODS_UK1 spans CUSTOMER_ID, SITE_USE_ID, and RECEIPT_METHOD_ID, enforcing uniqueness of the assignment combination.

Common Use Cases and Queries

Typical usage includes determining the default receipt method for a customer during receipt creation, validating that a chosen method is authorized, and reporting on payment method configuration. A common query pattern joins this table to AR_RECEIPT_METHODS and HZ_CUST_ACCOUNTS:

SELECT rcrm.cust_receipt_method_id, hca.account_number, rcrm.site_use_id, arm.name receipt_method, rcrm.primary_flag, rcrm.start_date, rcrm.end_date FROM ra_cust_receipt_methods rcrm, ar_receipt_methods arm, hz_cust_accounts hca WHERE rcrm.receipt_method_id = arm.receipt_method_id AND rcrm.customer_id = hca.cust_account_id AND rcrm.primary_flag = 'Y';

Reporting scenarios include auditing which customers have restricted payment methods, identifying primary methods per site use, and reviewing effective-dated assignments for AutoLockbox batch validation.

Related Objects

• AR_RECEIPT_METHODS — joined on RECEIPT_METHOD_ID; defines the receipt method master.
• HZ_CUST_ACCOUNTS — joined on CUSTOMER_ID; the customer account master.
• HZ_CUST_SITE_USES_ALL — joined on SITE_USE_ID; the customer site use master.
• AR_CASH_RECEIPTS and AR_RECEIVABLE_APPLICATIONS_ALL — consume the defaulted receipt method downstream.
• RA_CUSTOMER_TRX_ALL — transactions that reference customer receipt method defaults.
• HZ_CUST_ACCT_SITES_ALL — supporting customer site hierarchy joined via SITE_USE_ID.