Search Results merchant_id




Overview
Explore in AI Chat

Overview

APPS.ASO_I_RECEIPT_METHODS_V is an Oracle E-Business Suite view owned by the APPS schema that exposes receipt method reference data from the Oracle Receivables foundation layer to the Order Capture / iStore (ASO) application modules. In EBS 12.1.1 and 12.2.2 it functions as a thin, integration-oriented wrapper: rather than re-implementing receipt method logic, it presents a curated projection of AR_RECEIPT_METHODS so that order capture, order management, and self-service checkout pages can validate and display the payment instruments that a customer or operating unit is permitted to use.

The view is most commonly encountered during investigation of payment or remittance attributes carried into order capture flows. Searches for merchant_id frequently resolve to this object, because the view is one of the few ASO-layer entry points that surfaces the merchant identifier associated with a receipt method — the credential used when receipt methods are routed to a payment processor or bank gateway.

Underlying Base Objects

The documented view text is a single-table projection:

  • SELECT receipt_method_id, name, start_date, end_date, merchant_id FROM ar_receipt_methods
  • Referenced base object: AR_RECEIPT_METHODS (accessed via a synonym).
  • Owner of the view: APPS, consistent with the shared APPS synonym layer used across EBS 12.1.1 and 12.2.2.

There are no joins, unions, or aggregations in the documented definition, so the view is logically equivalent to a column-restricted, filter-free query on AR_RECEIPT_METHODS. Row counts and effective-dating behaviour therefore mirror the underlying Receivables table exactly; any filtering by date or operating unit is the responsibility of the calling form, concurrent program, or custom report.

Key Columns

  • RECEIPT_METHOD_ID — Primary key of the receipt method. This is the value stored on order, payment, and remittance records as the foreign key reference, and is the correct join key when linking this view back to transactional tables.
  • NAME — User-facing receipt method name (for example, a credit card brand or a direct debit method). This is the value typically displayed in LOVs and order capture screens.
  • START_DATE / END_DATE — Effective-dating bounds for the receipt method. The view does not apply a SYSDATE filter, so inactive or future-dated methods are returned and must be excluded by the consumer.
  • MERCHANT_ID — Merchant identifier associated with the receipt method, used in payment processing and gateway configuration. Note that this is a column of AR_RECEIPT_METHODS; the view simply exposes it to the ASO layer. Where receipt methods are not processor-based, this value may be null.

Common Use Cases and Queries

The view is used for LOV population, data validation prior to order submission, and extract/reporting requirements in order capture and iStore. A typical lookup by identifier:

SELECT receipt_method_id, name, merchant_id
FROM   apps.aso_i_receipt_methods_v
WHERE  receipt_method_id = :p_receipt_method_id;

To restrict to currently effective methods, apply the date bounds explicitly — the view does not do so:

SELECT receipt_method_id, name, merchant_id
FROM   apps.aso_i_receipt_methods_v
WHERE  TRUNC(SYSDATE) BETWEEN NVL(start_date, TRUNC(SYSDATE))
                          AND NVL(end_date, TRUNC(SYSDATE));

Where payment routing depends on processor credentials, the merchant identifier is selected alongside the method name, and results are usually joined back to AR_RECEIPT_METHODS or the Receivables customer/remittance tables for the full processing context. Because the view exposes only four attribute columns, queries requiring additional receipt method attributes — such as remittance bank, printing options, or receipt class — must reference AR_RECEIPT_METHODS directly rather than this view.