Search Results ar_batch_sources

Overview

The AR_RX_OTHER_APPLICATIONS_V view is a reporting base object owned by the APPS schema within the Oracle Receivables (AR) module. It is documented as the base view for the RXi:Other Applications Report, a standard Oracle EBS report used to present miscellaneous receipt applications that are not tied to standard cash-receipt matching. The view consolidates data from Receivables, Cash Management, General Ledger, and Trading Community Architecture (HZ) tables into a single flat, denormalized projection intended to simplify extraction for reporting.

Its status is VALID and it is a read-only view; it is not a table and therefore should never be used for DML. It functions primarily as a reporting and integration surface, presenting receipt-application detail enriched with customer, bank, and accounting context. Because the view exposes bank information — notably BANK_NAME and BANK_BRANCH_NAME — it is frequently relevant to searches involving banking attributes such as "bank_branch".

Underlying Base Objects

The view is defined over a large join spanning multiple base objects. Documented referenced objects include AR_RECEIVABLE_APPLICATIONS (the driving application detail table), AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY (receipt header and history), AR_PAYMENT_SCHEDULES, AR_RECEIVABLES_TRX, AR_RECEIPT_METHODS, AR_BATCHES, AR_BATCH_SOURCES, and AR_SYSTEM_PARAMETERS. Customer and party data come from HZ_CUST_ACCOUNTS, HZ_PARTIES, and HZ_CUST_SITE_USES. Bank data originates from CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES, and CE_BANK_BRANCHES_V. Accounting and organization context is supplied by GL_SETS_OF_BOOKS, GL_CODE_COMBINATIONS, and the packages ARPT_SQL_FUNC_UTIL, ARP_PROCESS_WRITEOFF, FA_RX_FLEX_PKG, FND_GLOBAL, FND_PROFILE, MO_GLOBAL, XTR_USER_ACCESS, and FND_ACCESS_CONTROL_UTIL.

The join is driven by application records in AR_RECEIVABLE_APPLICATIONS, linked to receipts, schedules, and receipt history, with lookup enrichment via ARPT_SQL_FUNC_UTIL and functionality security enforced through MO_GLOBAL and FND packages.

Key Columns

• SET_OF_BOOKS — ledger name from GL_SETS_OF_BOOKS.
• CUSTOMER_NUMBER, CUSTOMER_NAME — account and party identification.
• RECEIPT_NUMBER, RECEIPT_DATE, RECEIPT_AMOUNT, CURRENCY_CODE — receipt attributes.
• APPLY_DATE, GL_DATE, AMOUNT_APPLIED, AMOUNT_APPLIED_FROM — application amounts and dates.
• APPLICATION_TYPE, REC_ACTIVITY_NAME — activity and application classification.
• BANK_NAME, BANK_BRANCH_NAME — the bank and branch the receipt relates to, derived from CE_BANK_BRANCHES_V; this is the column of interest for "bank_branch" searches.
• BANK_ACCOUNT_NUMBER, BANK_ACCOUNT_CURRENCY — internal bank account attributes.
• ACCOUNTING_FLEX_FIELD, APPLICATION_REF_TYPE, COMMENTS, DOC_SEQUENCE_VALUE — descriptive and reference data.

Common Use Cases and Queries

Typical uses include reconciliation of other applications, tracking receipt applications by bank branch, and feeding downstream reports. A representative query listing applications by branch:

• SELECT receipt_number, customer_name, bank_name, bank_branch_name, amount_applied FROM ar_rx_other_applications_v WHERE bank_branch_name IS NOT NULL;
• SELECT set_of_books, receipt_date, currency_code, amount_applied FROM ar_rx_other_applications_v WHERE gl_date BETWEEN :p_from AND :p_to;
• SELECT customer_number, customer_name, rec_activity_name, amount_applied FROM ar_rx_other_applications_v ORDER BY customer_name;

Because the view references secured objects and functions, query results are filtered by operating unit and responsibility access, ensuring users only see data permitted by their security profile.