Search Results ar_mass_applications_v




Overview
Explore in AI Chat

Overview

AR_MASS_APPLICATIONS_V is a Receivables (AR) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the candidate transaction rows that the Mass Apply workflow presents to users during automatic and manual application of receipts against open debit items. The view is a critical component of the AutoApply and Mass Apply programs, which match cash receipts, on-account credits, and unapplied payments against open invoices, debit memos, chargebacks, and credit memos. Note that the underlying query uses the /*+ FIRST_ROWS ... ORDERED */ hint set and USE_NL directives, indicating the view was designed for interactive, cursor-driven access where rows are fetched incrementally for user review rather than bulk reporting.

The object carries a VALID status and is synonymous across 12.1.1 and 12.2.2, which is significant given the HZ_CUST_ACCOUNTS_U1 index reference in the view text. The query deliberately pins the unique index HZ_CUST_ACCOUNTS_U1 on the customer account table, and this index is a documented touchpoint for the view's execution plan in both releases. The user's search for "hz_cust_accounts_u1" reflects this dependency, since plan stability for AR_MASS_APPLICATIONS_V often depends on that index remaining valid and analyzed.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed through APPS-schema synonyms:

The query's ORDERED hint means the join sequence follows the FROM clause order, with PS_INV leading and the customer, site-use, batch source, and terms tables nested-looped.

Key Columns

The view exposes a wide column set reflecting its dual role for payment and transaction rows:

Common Use Cases and Queries

AR_MASS_APPLICATIONS_V is queried by the Mass Apply concurrent program and by custom application extensions that reimplement the matching logic. A typical diagnostic query to list open invoice candidates for a single customer is:

  • SELECT ROW_ID, TRX_NUMBER, TRX_CLASS_NAME, AMOUNT_DUE_REMAINING, DUE_DATE, STATUS FROM APPS.AR_MASS_APPLICATIONS_V WHERE CUSTOMER_ID = :cust_id AND TRX_CLASS_CODE = 'INV' AND APPLIED_FLAG = 'N' ORDER BY DUE_DATE;
  • SELECT CUSTOMER_NAME, CUSTOMER_NUMBER, RECEIPT_NUMBER, AMOUNT_DUE_REMAINING FROM APPS.AR_MASS_APPLICATIONS_V WHERE CASH_RECEIPT_ID > 0 AND AMOUNT_DUE_REMAINING <> 0;

Because the optimizer relies on FIRST_ROWS and the HZ_CUST_ACCOUNTS_U1 index, queries should always be filtered by CUSTOMER_ID (or CUSTOMER_NUMBER) so the nested-loops path is taken. Running the view without a customer predicate causes the PUSH_SUBQ and FIRST_ROWS hints to force inefficient row-by-row access on large AR datasets. This is why support notes frequently pair the view with concerns about index HZ_CUST_ACCOUNTS_U1 — if that unique index is dropped for tuning reasons, view performance for Mass Apply degrades sharply in both 12.1.1 and 12.2.2.