Search Results amount_applied_base




Overview
Explore in AI Chat

Overview

ARFV_CREDIT_MEMO_APPLICATIONS is an APPS-owned read-only view in the Oracle E-Business Suite Receivables (AR) module. In 12.1.1 and 12.2.2 the view exposes credit memo application activity — the linkage between a credit memo transaction and the open receivable (payment schedule or transaction line) it is applied against. It is one of a family of "ARFV" application views that present filtered slices of AR_RECEIVABLE_APPLICATIONS, in this case restricted to rows where APPLICATION_TYPE = 'CM'. Because the view text concludes with WITH READ ONLY, it is designed strictly for query, reporting, and extraction, not for DML.

The view is commonly used for operational reporting, reconciliation workflows, custom concurrent programs, and integration extracts where users need to see how credit memos have been consumed against customer balances, and in particular how the credit memo amount has been split across line, tax, freight, and receivables charges components.

Underlying Base Objects

The view is defined over several base objects in the APPS schema. The primary driving table is AR_RECEIVABLE_APPLICATIONS (RA), which stores every application of a payment, credit memo, or adjustment against a payment schedule. AR_PAYMENT_SCHEDULES (PS) supplies the applied schedule through APPLIED_PAYMENT_SCHEDULE_ID. RA_CUSTOMER_TRX (CTR) provides the credit memo header context — transaction number, transaction date, and reason code — via CUSTOMER_TRX_ID. RA_CUSTOMER_TRX_LINES (CTL) is joined via APPLIED_CUSTOMER_TRX_LINE_ID and supplies the applied line number. HR_ALL_ORGANIZATION_UNITS (AOU) is joined with an outer (+) to the ORG_ID to resolve the operating unit name.

All referenced base objects are SYNONYMs pointing to their underlying APPS tables. The view therefore inherits the security, indexing, and data model characteristics of AR_RECEIVABLE_APPLICATIONS, which is one of the highest-volume transactional tables in Receivables.

Key Columns

Common Use Cases and Queries

Typical scenarios include credit memo application reconciliation, freight and tax application analysis, multi-org reporting, and extract feeds into data warehouses. Example: identify credit memo applications where freight was applied.

SELECT credit_transaction_number, credit_transaction_date, applied_transaction_number, amount_applied, freight_amount_applied, tax_amount_applied, apply_date FROM arfv_credit_memo_applications WHERE freight_amount_applied > 0 AND apply_date >= :start_date;

Example: summarize credit memo applications by operating unit and transaction.

SELECT operating_unit, credit_transaction_number, SUM(amount_applied) total_applied FROM arfv_credit_memo_applications GROUP BY operating_unit, credit_transaction_number;

Because the view is filtered to APPLICATION_TYPE = 'CM', it isolates credit memo activity without requiring the caller to remember that predicate. For large-volume reporting, restrict by APPLY_DATE or ORG_ID and consider indexing AR_RECEIVABLE_APPLICATIONS accordingly.