Search Results clearing_house_branch_number

Overview

APPS.AR_REMITTED_RECEIPTS_FORMAT_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module that presents remitted receipt information in a flattened, denormalized format suitable for output, integration, and remittance file generation. The view consolidates receipt header data, customer identifying information, bank account details, remittance batch attributes, and clearing house information into a single row per remitted receipt. It is registered under FND Design Data as AR.AR_REMITTED_RECEIPTS_FORMAT_V and resides in the APPS schema with VALID status.

The view carries the standard Oracle warning designating it as internal use only, meaning Oracle Corporation does not support direct data access except from standard Oracle Applications programs. Regardless of this restriction, the view is widely referenced in customer-developed reports and interface extracts because it encapsulates the complex joins across receipt, customer, bank, and remittance entities that would otherwise require substantial custom SQL. The shape of the output mirrors the field layout expected by remittance advice formats and lockbox processing integrations, where a receipt must be described together with the remitting customer, the customer's bank, and the remitting bank.

Underlying Base Objects

The view is defined over a substantial set of base tables, synonyms, views, and packages. Receipt-centric data is drawn from AR_CASH_RECEIPTS, AR_CASH_RECEIPT_HISTORY, AR_PAYMENT_SCHEDULES, AR_RECEIPT_METHODS, and AR_BATCHES. Customer and party context comes from HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, and HZ_PARTIES. Bank and remittance banking data derive from CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, and CE_BANK_BRANCHES_V. Payment instrument extension data is sourced through IBY_TRXN_EXTENSIONS_V and the IBY_FNDCPT_TRXN_PUB package, while AR_LOOKUPS supplies decoded lookup meanings such as payment method and remittance method. Security and multi-org filtering are applied via FND_ACCESS_CONTROL_UTIL, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, and XTR_USER_ACCESS. The joins across these objects link each cash receipt to its customer account, site use, bank account, remittance batch, and clearing house, producing the composite row exposed by the view.

Key Columns

• RECEIPT_NUMBER, RECEIPT_CURRENCY, RECEIPT_AMOUNT, RECEIPT_DATE — core receipt identification and monetary attributes.
• CUSTOMER_NAME, CUSTOMER_NUMBER, CUSTOMER_SITE_LOCATION — remitting customer identification; CUSTOMER_SITE_LOCATION is the column most frequently searched in the context of this view, used to filter or display the customer site associated with the receipt.
• CUSTOMER_BANK_NAME, CUSTOMER_BANK_BRANCH_NAME, CUSTOMER_BANK_ACCOUNT_NAME, CUSTOMER_BANK_ACCOUNT_NUMBER — the remitting customer's bank details.
• REMIT_BANK_NAME, REMIT_BANK_BRANCH_NAME, REMIT_BANK_ACCOUNT_NAME, REMIT_BANK_ACCOUNT_NUMBER — the bank to which funds are remitted.
• CLEARING_HOUSE_NAME, CLEARING_HOUSE_BRANCH_NAME, CLEARING_HOUSE_BRANCH_NUMBER — intermediary clearing institution data.
• REMIT_BATCH_NAME, REMIT_BATCH_DATE, REMIT_BATCH_REMIT_METHOD, REMIT_BATCH_MEDIA_REFERENCE — remittance batch context.
• CASH_RECEIPT_ID, CUSTOMER_ID, CUSTOMER_BANK_ACCOUNT_ID, REMIT_BANK_ACCOUNT_ID, REMIT_BATCH_ID, PAYMENT_TRXN_EXTENSION_ID — surrogate keys enabling joins back to base entities.
• PAYMENT_CHANNEL_CODE, CUSTOMER_RECEIPT_REFERENCE, PAYMENT_METHOD, RECEIPT_FACTOR_DISCOUNT_AMOUNT, RECEIPT_SELECTED_FOR_FACTORING, MATURITY_DATE, RECEIPT_DEPOSIT_DATE, RECEIPT_EXCHANGE_RATE — processing and factoring attributes.

Common Use Cases and Queries

Typical uses include remittance advice reporting, lockbox and bank integration extracts, factoring candidate selection, and reconciliation reporting where receipt-to-customer-to-bank relationships must be presented together. Because CUSTOMER_SITE_LOCATION is a frequently requested column, queries commonly filter on it to isolate receipts by customer site.

Example: retrieve remitted receipts for a specific customer site within a date range.

• SELECT receipt_number, receipt_date, receipt_amount, receipt_currency, customer_name, customer_number, customer_site_location, remit_bank_name, remit_batch_name FROM apps.ar_remitted_receipts_format_v WHERE customer_site_location = :site_location AND receipt_date BETWEEN :start_date AND :end_date ORDER BY receipt_date, receipt_number;

Example: list receipts flagged for factoring with their bank details.

• SELECT receipt_number, customer_name, customer_site_location, receipt_selected_for_factoring, receipt_factor_discount_amount, customer_bank_name, customer_bank_account_number FROM apps.ar_remitted_receipts_format_v WHERE receipt_selected_for_factoring IS NOT NULL;

Example: join back to AR_CASH_RECEIPTS for additional attributes.

• SELECT v.receipt_number, v.customer_site_location, r.currency_code FROM apps.ar_remitted_receipts_format_v v, apps.ar_cash_receipts r WHERE v.cash_receipt_id = r.cash_receipt_id;

Given the Oracle internal-use designation, custom code should treat the view as read-only and validate behavior against the specific EBS patch level.