Results for “receipt_method_id”

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

Overview

The APPS.AR_RECEIPT_METHOD_NAME_V view is a Receivables (AR) reporting and integration object that exposes a filtered, denormalized list of receipt methods restricted to credit card payment processing. Its defining characteristic is the predicate RM.PAYMENT_TYPE_CODE = 'CREDIT_CARD' combined with a date-effectiveness filter, which together ensure that only currently active credit card receipt methods are returned. Because the view projects the MERCHANT_ID attribute alongside the receipt method identifier, name, and class, it serves as the canonical lookup for mapping a receipt method to its associated merchant identifier when processing credit card transactions. It is commonly consumed by payment integration code, refund workflows, and reconciliation reports that must determine which merchant account is tied to a given receipt method.

Underlying Base Objects

The view is defined in the APPS schema and is constructed over two base objects, both referenced through synonyms:

• AR_RECEIPT_METHODS (SYNONYM) — aliased as RM in the view text; the primary source of receipt method identity, name, merchant identifier, payment type, and effective dating.
• AR_RECEIPT_CLASSES (SYNONYM) — aliased as RC; joined on RM.RECEIPT_CLASS_ID = RC.RECEIPT_CLASS_ID to supply the human-readable receipt class name.

The join is an inner equi-join on the receipt class identifier. The view applies two filtering conditions: the payment type must equal CREDIT_CARD, and the current system date (truncated) must fall between RM.START_DATE and NVL(RM.END_DATE, TRUNC(SYSDATE)), meaning records without an end date are treated as open-ended and therefore active.

Key Columns

• RECEIPT_METHOD_ID — Primary identifier of the receipt method from AR_RECEIPT_METHODS; the key used to join back to transactional tables such as AR_CASH_RECEIPTS.
• NAME — The receipt method name (RM.NAME), the descriptive label presented to users and used in reports.
• MERCHANT_ID — The merchant identifier (RM.MERCHANT_ID) associated with the credit card receipt method. This is the attribute most frequently searched for in integration and settlement contexts, as it links the EBS receipt method to the external payment processor's merchant account.
• CLASS — The receipt class name (RC.NAME), projected under the alias CLASS, indicating the classification of the receipt method.

Common Use Cases and Queries

Typical scenarios include resolving a merchant identifier for a credit card receipt method during payment authorization, validating that a receipt method is currently effective before use, and populating LOV-style lookup queries in integrations. A representative query listing all active credit card methods with their merchants is:

• SELECT receipt_method_id, name, merchant_id, class FROM apps.ar_receipt_method_name_v;
• Filtering by a specific merchant: SELECT receipt_method_id, name, class FROM apps.ar_receipt_method_name_v WHERE merchant_id = :merchant_id;
• Joining to transactions to attribute receipts: SELECT v.name, v.merchant_id, r.amount FROM apps.ar_receipt_method_name_v v, apps.ar_cash_receipts r WHERE v.receipt_method_id = r.receipt_method_id;

Because the view already enforces payment type and date effectiveness, consumers do not need to reapply those predicates, which reduces the risk of inconsistent filtering across integrations.