Search Results ar_app_adj_v




Overview
Explore in AI Chat

Overview

AR_APP_ADJ_V is a Receivables view owned by the APPS schema that consolidates payment application and adjustment activity into a single reporting structure. It was introduced in Release 11.5 and remains present and valid in Oracle EBS 12.1.1 and 12.2.2, where it is retained primarily for backward compatibility with custom reports, interfaces, and legacy integrations. The view presents adjustments and receivable applications together with the transaction, receipt, and payment schedule context needed to interpret them, exposing amounts in their natural transaction sign.

Because it depends on the ARPT_SQL_FUNC_UTIL package to translate lookup codes into user-facing meanings at runtime, the view is intended for read-only querying and reporting rather than for transactional processing. It is best understood as a reporting convenience layer that shields callers from the join complexity among applications, adjustments, receipts, and payment schedules.

Underlying Base Objects

ETRM documents AR_APP_ADJ_V as defined over the following objects in the APPS schema:

The core of the view is AR_RECEIVABLE_APPLICATIONS, aliased APP, which supplies the applied amounts, application date, status, GL date, cash receipt and customer transaction identifiers. AR_PAYMENT_SCHEDULES (PS) contributes transaction number, class, currency, due date, terms sequence, and payment schedule identifier. AR_RECEIVABLES_TRX and RA_CUST_TRX_TYPES provide the credit memo and invoice transaction type names, while AR_CASH_RECEIPTS and AR_CASH_RECEIPT_HISTORY supply receipt-level attributes such as creation status. Credit memo reason codes are resolved through AR_ADJUSTMENTS and lookup utilities.

Key Columns

The view exposes columns that are highly relevant to payment-type analysis, which is the term most frequently associated with this object in user searches:

Common Use Cases and Queries

Typical usage includes reconciliation of applications against receipts, payment-type reporting, and analysis of adjustments by reason code.

To list applications by payment type meaning:

  • SELECT trx_number, status, apply_date FROM ar_app_adj_v WHERE status = 'CASH';

To aggregate applied amounts by transaction:

  • SELECT trx_number, SUM(amount_applied) FROM ar_app_adj_v GROUP BY trx_number;

Because lookup meanings are resolved on every row via ARPT_SQL_FUNC_UTIL, queries against large data sets should be filtered tightly and, where possible, restricted by date or transaction number to avoid costly function calls.