Search Results current_batch_unremitted




Overview
Explore in AI Chat

Overview

AR_BOE_REMIT_RECEIPTS_CBUNR_V is an Oracle E-Business Suite Receivables (AR) view owned by the APPS schema. The name encodes its function: "BOE" refers to the Bank of England / remittance batch processing lineage, "REMIT" to remittance batches, and the "CBUNR" suffix abbreviates the literal selection type CURRENT_BATCH_UNREMITTED. The view presents the set of cash receipts that belong to a remittance batch but have not yet been remitted, packaged as a uniform row structure so that the receipts can be surfaced in the Remittance Batch window and in concurrent programs that build and transmit remittance advice files to banks.

Within the Oracle Receivables Automatic Receipts and Remittance workflow, this view acts as a reporting and integration surface rather than a transactional table. Its canonical role is to expose, for a given remittance batch, the receipt header, the associated receipt method, the remitting bank account and branch, the customer, and the instrument details needed to construct a bank remittance file. The SELECTION_TYPE column is hard-coded to the constant 'CURRENT_BATCH_UNREMITTED', which signals to any consuming process that the rows returned are the current-batch, not-yet-remitted population. In the 12.2.2 data dictionary the object is documented as (Release 11.5 Only), meaning it originated in Release 11i and is retained in later releases primarily for backward compatibility; in 12.1.1 and 12.2.2 the remittance/BOE logic is largely superseded by IBY (Oracle Payments) functionality.

Underlying Base Objects

The view is defined over a broad set of APPS synonyms and public views. The core AR objects are AR_CASH_RECEIPTS (the driving receipt row, aliased CR), AR_CASH_RECEIPT_HISTORY (aliased CRH, supplying the historical amount and history identifier), AR_BATCHES (aliased BAT, supplying the batch identifier, name, and applied status), AR_PAYMENT_SCHEDULES (aliased PS, providing maturity and due dates), AR_RECEIPT_METHODS (aliased RM, providing the receipt method name), and AR_RECEIPT_CLASSES (aliased RC, supplying the remit method code).

Bank-side data comes from CE_BANK_ACCOUNTS (aliased CBA, for the bank account number), CE_BANK_ACCT_USES (a view, for the remittance bank account use), and CE_BANK_BRANCHES_V (aliased BB, for bank name and branch name). Customer and party attributes are sourced from HZ_CUST_ACCOUNTS (aliased CUST_ACCT, for the customer number), HZ_PARTIES (aliased PARTY, for the customer name, truncated to 50 bytes via SUBSTRB), and the Receivables customer site use. Instrument details (bank account or credit card numbers) are resolved from IBY_EXT_BANK_ACCOUNTS and IBY_CREDITCARD (aliased IBY), with IBY_PMT_INSTR_USES_ALL and IBY_FNDCPT_TX_EXTENSIONS supporting the payment instrument joins.

Contextual security and multi-org scoping are applied through the FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, and FND_PROFILE packages, with MO_GLOBAL providing operating-unit (Multi-Org) filtering and XTR_USER_ACCESS supporting any trading/treasury access restrictions.

Key Columns

Common Use Cases and Queries

Typical usage is to enumerate unremitted receipts for a remittance batch prior to transmitting a remittance advice, or to reconcile which receipts remain outstanding in a batch. A representative query is:

  • SELECT cash_receipt_id, receipt_number, batch_id, batch_name, amount, remit_bank_account_number FROM apps.ar_boe_remit_receipts_cbunr_v WHERE batch_id = :p_batch_id AND selection_type = 'CURRENT_BATCH_UNREMITTED';
  • Filtering by receipt_method_id or remit_method_code to isolate receipts by remittance channel.
  • Joining back to AR_CASH_RECEIPTS on cash_receipt_id for additional receipt detail not exposed by the view.

Because the view is documented as Release 11.5-only and remittance processing in 12.1.1/12.2.2 is delivered primarily through Oracle Payments (IBY), this view should be treated as a legacy reporting surface. Direct queries remain valid for read-only reconciliation, but new integrations should target the supported IBY remittance APIs.