Search Results paying_customer_name

Overview

APPS.AR_BOE_AUTO_RECEIPTS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema with FND Design Data reference AR.AR_BOE_AUTO_RECEIPTS_V. Its status is VALID. Oracle classifies it as a supplementary view used to simplify coding within Oracle Forms, and the standard caveat applies: direct querying or alteration of the underlying data through this view is not recommended, as its definition may change substantially between minor or major releases.

The object supports the AutoReceipts / Bill of Exchange style workflow in Oracle Receivables, presenting a flattened, denormalized picture of receivables transactions joined to their cash receipts, batch assignments, payment schedules, and payment instrument attributes. It is oriented toward the receipt-creation and receipt-batch processing screens rather than to general ledger reporting, which is why many of its columns are prefixed with terms reflecting selection, application, and batching state.

Underlying Base Objects

The view is defined over a set of APPS synonyms that resolve to the following base tables and supporting objects:

• AR_BATCHES, RA_BATCH_SOURCES, and AR_CASH_RECEIPTS — batch header and receipt header information.
• AR_CASH_RECEIPT_HISTORY — receipt lifecycle status and history records.
• AR_PAYMENT_SCHEDULES and AR_RECEIVABLE_APPLICATIONS — payment schedules and applied receipt-to-invoice relationships.
• AR_CONS_INV — consolidated invoice data.
• RA_CUSTOMER_TRX and RA_CUST_TRX_TYPES — receivables transactions and their transaction types.
• HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_PARTIES — customer, site use, and party name data.
• IBY_CREDITCARD, IBY_EXT_BANK_ACCOUNTS, IBY_PMT_INSTR_USES_ALL, IBY_FNDCPT_PMT_CHNNLS_B, IBY_FNDCPT_PMT_CHNNLS_TL, and IBY_FNDCPT_TX_EXTENSIONS — payment instrument, bank account, and payment channel information.
• FND_APPLICATION — application identity used for the IBY payment channel naming.

The join effectively anchors a transaction line to its customer, bill-to and paying customer context, its payment instrument, and its receipt application and batch state in a single row.

Key Columns

The BILLING_LOCATION column (VARCHAR2(40)) is the field most commonly sought when searching this view; it carries the billing location description associated with the customer site use for the transaction, and is one of the principal customer-facing attributes exposed for receipt selection screens.

Other important columns include CASH_RECEIPT_ID, RECEIPT_NUMBER, and TRX_NUMBER, which identify the receipt and transaction; SELECTED_FOR_RECEIPT_BATCH_ID and BATCH_ID, which tie rows to receipt batch processing; CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER, and CUSTOMER_SITE_USE_ID, which identify the customer context; and BILL_TO_CUSTOMER_ID, BILL_TO_SITE_USE_ID, PAYING_CUSTOMER_ID, PAYING_CUSTOMER_NAME, and PAYING_CUSTOMER_NUMBER, which distinguish the bill-to and paying parties.

Financial and instrument columns include CURRENCY_CODE, AMOUNT_APPLIED, TERM_DUE_DATE, TRX_DATE, BANK_NAME, BANK_BRANCH_NAME, BANK_ACCOUNT_NUMBER, and CUSTOMER_BANK_ACCOUNT_ID. Status and relationship columns include RA_STATUS, CRH_STATUS, BATCH_APPLIED_STATUS, PAYMENT_SCHEDULE_ID, RECEIVABLE_APPLICATION_ID, and APPLIED_PAYMENT_SCHEDULE_ID. ATTRIBUTE1 through ATTRIBUTE11 provide the standard descriptive flexfield context.

Common Use Cases and Queries

Typical usage is diagnostic or reporting queries against AutoReceipts activity, filtered by customer, billing location, batch, or receipt state. The view is frequently joined to AR_CASH_RECEIPTS or AR_BATCHES when a query needs columns not exposed here.

A representative query retrieving receipts by billing location:

• SELECT receipt_number, trx_number, customer_name, billing_location, amount_applied, crh_status FROM apps.ar_boe_auto_receipts_v WHERE billing_location IS NOT NULL;

To examine activity for a specific batch:

• SELECT batch_id, batch_name, receipt_number, trx_number, amount_applied, batch_applied_status FROM apps.ar_boe_auto_receipts_v WHERE batch_id = :p_batch_id;

Because Oracle explicitly discourages direct DML and warns that the view may change across releases, any production integration should rely on the documented Receivables APIs and public views rather than binding permanently to this object.