Search Results ar_receivable_applications_v




Overview
Explore in AI Chat

Overview

AR_RECEIVABLE_APPLICATIONS_V is an APPS-owned view in the Oracle Receivables module that consolidates receivable application activity into a single reporting and integration source. It joins receipt, transaction, payment schedule, customer, and batch-source information so that applied, unapplied, and discount-related amounts can be examined without navigating the underlying normalized tables individually.

The view carries a documented status of VALID, and its title in the ETRM metadata explicitly notes "(Release 11.5 Only)." This qualification is significant: the definition presented reflects the 11.5 lineage, and the object should be evaluated against the 12.1.1 or 12.2.2 instance in which it is deployed. The view text includes an ORDERED hint with a coordinated INDEX hint block that pins access paths for APP (AR_RECEIVABLE_APPLICATIONS_N1), PS_INV (AR_PAYMENT_SCHEDULES_U1, _N2, _N6), CR (AR_CASH_RECEIPTS_U1), CT (RA_CUSTOMER_TRX_U1), CTT (RA_CUST_TRX_TYPES_U1), BS (RA_BATCH_SOURCES_U2), SU (HZ_CUST_SITE_USES_U1), T (RA_TERMS_U1), and AR_RECEIVABLES_TRX_U1. Because these hints are embedded in the view definition, execution plans for queries against it are effectively pre-determined, which is a material consideration for performance tuning and for planning index maintenance.

Underlying Base Objects

The documented 12.2.2 metadata lists the following referenced base objects: ARPT_SQL_FUNC_UTIL (package), ARP_DEDUCTION (package), AR_CASH_RECEIPTS, AR_CONS_INV, AR_LOOKUPS, AR_PAYMENT_SCHEDULES, AR_RECEIVABLES_TRX, AR_RECEIVABLE_APPLICATIONS, HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES, HZ_PARTIES, RA_BATCH_SOURCES, RA_CUSTOMER_TRX, RA_CUSTOMER_TRX_LINES, and RA_CUST_TRX_TYPES.

The view's central fact table is AR_RECEIVABLE_APPLICATIONS (aliased APP), which supplies AMOUNT_APPLIED, discount taken amounts, and the applied payment schedule reference. AR_PAYMENT_SCHEDULES (PS_INV) supplies the installment detail, including CUSTOMER_TRX_ID, TRX_NUMBER, TERMS_SEQUENCE_NUMBER, AMOUNT_DUE_REMAINING, and the earned and unearned discount amounts. AR_CASH_RECEIPTS (CR) contributes the RECEIPT_NUMBER. Customer attribution flows through HZ_PARTIES and HZ_CUST_ACCOUNTS, while HZ_CUST_SITE_USES supports site-use context. Transaction-level data originates from RA_CUSTOMER_TRX and RA_CUST_TRX_TYPES, with AR_CONS_INV and RA_CUSTOMER_TRX_LINES available as additional referenced objects. The two packages, ARPT_SQL_FUNC_UTIL and ARP_DEDUCTION, indicate that portions of the view's logic rely on packaged functions rather than pure inline SQL, which can affect the view's behavior across patch levels.

Key Columns

The view exposes a ROW_ID derived from the base rowid, alongside standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID.

Common Use Cases and Queries

Typical uses include reconciliation of receipt applications, credit and collection reporting, customer-level applied-amount analysis, and integration extracts feeding downstream financial systems. A representative query is:

  • SELECT CASH_RECEIPT_ID, CUSTOMER_TRX_ID, RECEIPT_NUMBER, TRX_NUMBER, AMOUNT_APPLIED, DISCOUNT, AMOUNT_DUE_REMAINING FROM AR_RECEIVABLE_APPLICATIONS_V WHERE AMOUNT_DUE_REMAINING > 0 ORDER BY RECEIPT_NUMBER;
  • SELECT CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME, SUM(AMOUNT_APPLIED) FROM AR_RECEIVABLE_APPLICATIONS_V GROUP BY CUSTOMER_ID, CUSTOMER_NUMBER, CUSTOMER_NAME;

Given the embedded INDEX hints, performance-sensitive reporting should account for the fixed access paths and be validated on the specific 12.1.1 or 12.2.2 instance. Readers who searched for "ra_customer_trx_u1" should note that this unique index appears in the view's hint block as the designated access path for RA_CUSTOMER_TRX (alias CT), confirming its relevance to transaction-number retrieval within this view.