Search Results rec_activity_name




Overview
Explore in AI Chat

Overview

APPS.AR_APP_ADJ_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module that presents a unified, denormalized picture of payment applications and adjustments recorded against customer transactions. In Oracle EBS 12.1.1 and 12.2.2, the view is owned by the APPS schema and is primarily intended to support the Receivables "Application and Adjustment" inquiry and reconciliation functionality. It surfaces rows from AR_RECEIVABLE_APPLICATIONS (cash, credit memo, and other applications) combined with descriptive attributes drawn from payment schedules, customer transactions, transaction lines, receipt methods, and receivable transaction types.

The view's most distinctive role is as a presentation layer for application reference information. It exposes APPLICATION_REF_TYPE, APPLICATION_REF_NUM, APPLICATION_REF_REASON, and a derived APPLICATION_REF_TYPE_MEANING column generated by a call to ARPT_SQL_FUNC_UTIL.GET_LOOKUP_MEANING. This makes the view a convenient source for reports and integrations that need to understand why a particular application was created, such as a claim, deduction, or prepayment, without joining the underlying lookup tables manually.

Underlying Base Objects

The view is defined over several AR and FND synonyms as documented in the ETRM metadata. The driving table is AR_RECEIVABLE_APPLICATIONS (aliased APP), which supplies the application rows, applied amounts, status, application type, and the application reference columns. AR_PAYMENT_SCHEDULES (PS) provides transaction number, class, currency, due date, payment schedule identifiers, and terms sequence information. RA_CUSTOMER_TRX (CT) and RA_CUSTOMER_TRX_LINES (CTL) contribute reason codes and line numbers, while RA_CUST_TRX_TYPES (CTT) and AR_RECEIVABLES_TRX (RM) supply transaction type names via DECODE logic. AR_CASH_RECEIPTS (CRH) contributes receipt creation status, AR_CASH_RECEIPT_HISTORY supports receipt history context, AR_RECEIPT_METHODS supports receipt method joins, AR_ADJUSTMENTS supports adjustment data, and FND_USER supports the audit columns.

Two PL/SQL packages are referenced directly in the SELECT list: ARPT_SQL_FUNC_UTIL, which resolves lookup meanings for INV/CM class, payment type, invoicing reason, credit memo reason, receipt creation status, and application reference type; and ARP_DEDUCTION, which retrieves a trade management reason for claim-type applications through ARP_DEDUCTION.GET_TM_ORACLE_REASON on secondary_application_ref_id.

Key Columns

Common Use Cases and Queries

The view supports application and adjustment inquiry, cash reconciliation, deduction and claim analysis, and custom reporting. It is frequently used in Oracle Reports, BI Publisher, and OAF-based inquiries where a flat result set is preferable to multi-table joins.

Example query to examine applications by reference type:

SELECT trx_number,
       application_ref_type,
       application_ref_type_meaning,
       application_ref_num,
       amount_applied,
       apply_date,
       status
FROM   apps.ar_app_adj_v
WHERE  application_ref_type = 'CLAIM'
ORDER BY apply_date DESC;

Example query to summarize applied amounts by transaction:

SELECT trx_number,
       invoice_currency_code,
       SUM(amount_applied) total_applied
FROM   apps.ar_app_adj_v
WHERE  status = 'APP'
GROUP BY trx_number, invoice_currency_code;

Because the view invokes lookup functions in its SELECT list, reports should filter aggressively and avoid unnecessary full scans. Its decoded columns remove the need for downstream joins to FND_LOOKUP_VALUES, simplifying both ad hoc queries and production integrations.