Search Results creation_method_dsp




Overview
Explore in AI Chat

Overview

AR_OEX_RECEIPTS_VIEW is a valid Oracle E-Business Suite view owned by the APPS schema in the Receivables (AR) product. It is designed to support the Oracle Exchange Bill Presentment Payments page, presenting cash receipt information in a denormalized, display-ready format for exchange billing scenarios. The view consolidates data from receipt headers, receipt history, receipt methods, receipt classes, customer accounts, and party records so that a single query returns both technical identifiers and descriptive lookup values required by the Exchange-presented payments interface. Because it joins current and original receipt history rows, it exposes both the original and the functional (accounted) receipt amounts, statuses, and attributes.

Underlying Base Objects

The view is defined over a documented set of synonyms and views in the APPS schema, including AR_CASH_RECEIPTS_ALL, AR_CASH_RECEIPT_HISTORY_ALL, AR_BATCHES_ALL, AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, AR_PAYMENT_SCHEDULES_ALL, AR_RECEIVABLES_TRX_ALL, AR_LOOKUPS, HZ_CUST_ACCOUNTS, HZ_PARTIES, AP_BANK_ACCOUNTS_ALL, and AP_BANK_BRANCHES. It also references the FND_PROFILE package to retrieve the AR_MASK_BANK_ACCOUNT_NUMBERS profile option, which controls masking of customer bank account numbers. The primary join is between AR_CASH_RECEIPTS_ALL (CR) and AR_CASH_RECEIPT_HISTORY_ALL (CRH_CURRENT), with the customer bank account and branch information resolved through AP_BANK_ACCOUNTS_ALL and AP_BANK_BRANCHES, and customer identity resolved through HZ_CUST_ACCOUNTS and HZ_PARTIES.

Key Columns

Common Use Cases and Queries

Although the view is purpose-built for the Exchange Bill Presentment Payments page, it is frequently queried for receipt reporting where decoded statuses and masked bank details are required. A typical query might select receipt number, receipt date, amount, status description, and creation method for a given operation unit:

SELECT receipt_number, receipt_date, amount, receipt_status_dsp, creation_method_dsp
FROM apps.ar_oex_receipts_view
WHERE org_id = :org_id
AND receipt_date BETWEEN :from_date AND :to_date;

Another common scenario filters on receipt status to isolate unreconciled or reversed receipts, joining back to AR_CASH_RECEIPTS_ALL or AR_RECEIVABLES_TRX_ALL to reconcile history and transaction references. Because the view exposes CUSTOMER_RECEIPT_REFERENCE and CUSTOMER_BANK_ACCOUNT, it is also useful for customer-facing summaries and for auditing the receipt reversal reason captured in the associated receivable transaction records.