Results for “remit_bank_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_AUTOMATIC_RECEIPTS_FORMAT_V is an APPS-owned view in the Oracle Receivables (AR) module that exposes information about confirmed automatic receipts that are being formatted for printing or transmission. Automatic receipts are receipts created without manual entry, typically generated by the Automatic Receipts program against a receipt batch defined by an automatic receipt method. Once these receipts are confirmed, the formatting process reads them from this view to produce the physical or electronic output delivered to the customer, such as a printed remittance document or a bank transmission file.

The view consolidates data from receipt header, batch, customer, payment schedule, and bank account sources into a single flat structure that a formatting program or report can consume directly. Because it includes batch-level attributes such as BATCH_ID, BATCH_DATE, and MEDIA_REFERENCE alongside receipt-level detail, it is well suited for both batch-oriented printing and reconciliation queries. Callers searching on receipt_batch_id will find that the batch identity is surfaced through this view as BATCH_ID, derived from AR_BATCHES.

Underlying Base Objects

The view joins numerous AR, HZ, CE, and IBY objects. Documented referenced base objects include AR_BATCHES, AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_PAYMENT_SCHEDULES, AR_RECEIPT_CLASSES, and AR_RECEIPT_METHODS (all synonyms), together with CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, CE_BANK_BRANCHES_V, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, and the IBY payment instrument objects (IBY_CREDITCARD, IBY_EXT_BANK_ACCOUNTS, IBY_FNDCPT_PMT_CHNNLS_B, IBY_FNDCPT_TX_EXTENSIONS, IBY_PMT_INSTR_USES_ALL).

Key join logic: receipts link to receipt methods and receipt classes, restricted to RC.CREATION_METHOD_CODE = 'AUTOMATIC'. Customer and site data come via HZ_CUST_ACCOUNTS and HZ_CUST_SITE_USES. Bank details come from CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, and CE_BANK_BRANCHES_V. The view also references runtime packages such as FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS, indicating that Org and access-control predicates may be applied when the view is queried.

Key Columns

• RECEIPT_NUMBER, RECEIPT_DATE, CURRENCY_CODE, AMOUNT, EXCHANGE_RATE — core receipt header attributes from AR_CASH_RECEIPTS.
• CASH_RECEIPT_ID — primary identifier of the receipt.
• BATCH_ID, NAME, BATCH_DATE, MEDIA_REFERENCE — batch identity and transmission reference from AR_BATCHES.
• DUE_DATE — payment schedule due date from AR_PAYMENT_SCHEDULES.
• PRINTED_NAME, PAYMENT_CHANNEL_CODE — receipt method attributes from AR_RECEIPT_METHODS.
• CUSTOMER_BANK_ACCOUNT_NUMBER — instrument number decoded as account or card number via IBY.
• REMIT_BANK_NAME, REMIT_BANK_BRANCH_NAME, REMIT_BANK_BRANCH_NUMBER, REMIT_BANK_ACCOUNT_NAME, REMIT_BANK_ACCOUNT_NUMBER, REMIT_BANK_ACCOUNT_ID — remittance bank details.
• PAYMENT_TRXN_EXTENSION_ID, CUST_ACCOUNT_ID — linkage keys for payment extension and customer account.

Common Use Cases and Queries

Typical uses include formatting automatic receipts for output, reconciling receipts by batch, and auditing remittance bank information. A representative query filtering on the batch identifier is:

• SELECT receipt_number, batch_id, amount, currency_code, remit_bank_account_number FROM ar_automatic_receipts_format_v WHERE batch_id = :receipt_batch_id;
• SELECT receipt_number, batch_date, media_reference FROM ar_automatic_receipts_format_v WHERE batch_id = :receipt_batch_id ORDER BY receipt_number;

Because the view applies automatic-receipt and org-access predicates, its result set is already restricted to confirmed automatic receipts ready for formatting, making it a reliable source for both printing programs and diagnostic reconciliation reports.