Search Results receipt_method_name




Overview

AR_BOE_REMIT_RECEIPTS_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module. Its name reflects its function: a Bills of Exchange (BOE) remittance receipts view that consolidates cash receipt, remittance batch, customer, and bank account information into a single queryable structure. The view presents rows for remittance processing, with a literal SELECTION_TYPE column of 'CURRENT_BATCH_UNREMITTED' indicating its role in identifying receipts that are candidates for remittance to a bank.

The documented description marks this object as "(Release 11.5 Only)." Although the object appears as VALID in later releases, including 12.1.1 and 12.2.2, its functional scope originates in the 11.5 remittance workflow. In current releases it typically survives as a compatibility and reporting artifact rather than a primary processing view. Regarding the user's search term, payment_channel_code, this column is not exposed by AR_BOE_REMIT_RECEIPTS_V. Payment channel codes are associated with IBY (Payments) and receipt method/channel configuration objects; the closest columns available here are RECEIPT_METHOD_ID, RECEIPT_METHOD_NAME, and REMIT_METHOD_CODE.

Underlying Base Objects

The view is defined over the following documented base objects. The 12.2.2 metadata lists:

The core driver is AR_CASH_RECEIPTS (aliased CR), joined to its history (CRH) for amounts and bank charges, and to AR_BATCHES (BAT) for remittance batch context. Bank details derive from CE_BANK_ACCOUNTS (CBA) and CE_BANK_BRANCHES_V (BB). Customer identity comes from HZ_PARTIES and HZ_CUST_ACCOUNTS. The inclusion of MO_GLOBAL and XTR_USER_ACCESS indicates multi-org and user-access (security) filtering is applied, while FND_PROFILE and FND_GLOBAL supply session and profile context.

Key Columns

Common Use Cases and Queries

Typical uses include identifying unremitted receipts, reconciling remittance batches, and feeding bank-format exports. A representative query:

SELECT receipt_number, customer_name, amount, currency_code,
       remit_bank_account_number, remit_method_code, batch_name
FROM   apps.ar_boe_remit_receipts_v
WHERE  selection_type = 'CURRENT_BATCH_UNREMITTED'
  AND  remit_method_code IS NOT NULL;

Because payment_channel_code is unavailable, users seeking channel data should join to receipt method or IBY payment instrument configuration. Always apply MO_GLOBAL/security-aware filters, as the view already enforces org access via its underlying packages.