Search Results misc_payment_source

Overview

The IBE_AR_CASH_RECEIPTS_V view is a reporting and integration construct within the Oracle E-Business Suite iStore (IBE) module. Its stated purpose, per the ETRM metadata, is to retrieve payment information during post-sales customer interactions in iStore. In practice, this view consolidates receipt-level data from Oracle Receivables and exposes it in a denormalized, presentation-friendly format so that iStore pages and self-service flows can display customer payment history, applied and unapplied balances, on-account amounts, and banking details without requiring the calling application to join the underlying AR and ASO tables directly.

The view spans both the 12.1.1 and 12.2.2 releases and is documented as being based on AR_CASH_RECEIPTS and AR_PAYMENT_SCHEDULES, though the actual view text joins several additional objects. The user query "misc_payment_source" maps directly to the MISC_PAYMENT_SOURCE column exposed by this view, which surfaces the same column from AR_CASH_RECEIPTS. This column is significant because it identifies the source of miscellaneous (non-invoice) receipts, such as refunds, interest, or other ad hoc payments.

Underlying Base Objects

Although the ETRM metadata lists no formally "documented" base objects and the view is noted as "Not implemented in this database" for the sampled instance, the view text reveals its true foundation. The primary tables are AR_CASH_RECEIPTS (aliased CR) and AR_PAYMENT_SCHEDULES (aliased PS). Supporting joins extend to:

• AR_LOOKUPS (AL_PAY_TYPE) – resolves the receipt type meaning.
• AR_RECEIVABLE_APPLICATIONS (RA) – supplies applied, unapplied, and on-account amounts by status.
• AP_BANK_ACCOUNTS (CUST_BANK) and AP_BANK_BRANCHES (CUST_BANK_BRANCH) – provide customer bank account and branch names.
• ASO_I_CUST_ACCOUNTS_V (CUST) – supplies customer name, account number, party, and account ID.

All customer-side joins are outer joins (noted by the (+) syntax), ensuring receipts are returned even where customer or bank data is absent.

Key Columns

The view exposes a broad set of columns. Notable ones include:

• CASH_RECEIPT_ID, RECEIPT_NUMBER, RECEIPT_DATE, RECEIPT_STATUS – core receipt identifiers and status.
• AMOUNT, APPLIED_AMOUNT, UNAPPLIED_AMOUNT, ON_ACCOUNT_AMOUNT – currency-formatted amounts using FND_CURRENCY.SAFE_GET_FORMAT_MASK.
• PAYMENT_TYPE / TYPE – receipt type code and its lookup meaning.
• MISC_PAYMENT_SOURCE – the miscellaneous payment source from AR_CASH_RECEIPTS, central to the user's search.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUST_ACCOUNT_ID, PARTY_ID – customer identity fields.
• BANK_NAME, CUSTOMER_BANK_ACCOUNT, CUSTOMER_BANK_NAME, CUSTOMER_BANK_BRANCH – banking detail.
• PAYMENT_SCHEDULE_ID, MATURITY_DATE, CURRENCY_CODE, COMMENTS, RECEIPT_METHOD_ID – supporting attributes.

Common Use Cases and Queries

Typical scenarios include displaying a customer's receipt history in iStore, reconciling applied versus unapplied balances, and identifying the source of miscellaneous receipts. A representative query isolating the misc_payment_source follows:

• SELECT receipt_number, amount, payment_type, misc_payment_source FROM ibe_ar_cash_receipts_v WHERE cust_account_id = :p_cust_account_id;
• SELECT receipt_number, applied_amount, unapplied_amount, on_account_amount FROM ibe_ar_cash_receipts_v WHERE receipt_date BETWEEN :p_from AND :p_to;
• SELECT customer_name, misc_payment_source, receipt_status FROM ibe_ar_cash_receipts_v WHERE misc_payment_source IS NOT NULL;

Because amounts are pre-formatted and joins are pre-built, this view streamlines iStore post-sales reporting while preserving AR as the system of record.