Search Results ar_boe_auto_receipts_v




Overview
Explore in AI Chat

Overview

AR_BOE_AUTO_RECEIPTS_V is an Oracle Receivables (AR) dictionary view owned by the APPS schema. It is documented in the ETRM reference as a Release 11.5-only object, and its view text makes clear that it was built to support the Bill of Exchange (BOE) automatic receipt creation process. The view presents a flattened, receipt-shaped projection of payment schedule and transaction data so that the BOE batch mechanism could treat selected invoices and their installments as if they were already cash receipts.

Structurally, the view emulates the column layout of an AR receipt/application result set. It supplies constants and placeholders for identifiers that do not yet exist at selection time — notably CASH_RECEIPT_ID = -1, RECEIVABLE_APPLICATION_ID = -1, and APPLIED_PAYMENT_SCHEDULE_ID = -1 — while populating real values from payment schedules, transactions, customers, banks, and batch sources. This makes it an integration and batch-processing view rather than an operational inquiry view. In 12.1.1 and 12.2.2 the object is retained for backward compatibility and defined over the current AR and IBY synonyms listed in the metadata.

Underlying Base Objects

The documented base objects include the core AR transaction and payment schedule tables — AR_PAYMENT_SCHEDULES, RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, RA_BATCH_SOURCES, AR_BATCHES, AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_RECEIVABLE_APPLICATIONS, and AR_CONS_INV. Customer and party data comes from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_PARTIES; bank and payment instrument data is drawn from the IBY tables IBY_EXT_BANK_ACCOUNTS, IBY_CREDITCARD, IBY_PMT_INSTR_USES_ALL, IBY_FNDCPT_PMT_CHNNLS_B, IBY_FNDCPT_PMT_CHNNLS_TL, and IBY_FNDCPT_TX_EXTENSIONS. FND_APPLICATION provides application context. The view joins payment schedule rows (PS) to their customer transactions (CT) and enriches them with customer, bank, and batch attributes.

Key Columns

Common Use Cases and Queries

Typical usage is to identify payment schedule installments eligible for automatic BOE receipt generation and to reconcile them by due date. A representative query retrieves open installments with their term due date:

  • SELECT customer_trx_id, trx_number, term_due_date, amount_applied, currency_code, customer_name FROM apps.ar_boe_auto_receipts_v WHERE term_due_date BETWEEN :p_from AND :p_to AND batch_applied_status IS NULL ORDER BY term_due_date;

Analysts also use it to group unresolved balances by batch and customer, or to verify instrument and bank attributes before creating receipts. Because the view is 11.5-era and largely retained for compatibility, new development should confirm column availability in the target 12.1.1/12.2.2 instance; where TERM_DUE_DATE drives maturity logic, joining back to AR_PAYMENT_SCHEDULES ensures consistency with current AR data.