Search Results on_account_amount




Overview
Explore in AI Chat

Overview

The APPS.AR_RECEIPT_AMOUNTS_V view is a Receivables reporting object that summarizes receipt activity by cash receipt, grouping applied, unapplied, on-account, and unidentified balances into a single row per receipt. It joins cash receipts to their application records and receipt methods, aggregating the AMOUNT_APPLIED value from AR_RECEIVABLE_APPLICATIONS according to application status. The object is owned by the APPS schema and is documented in ETRM as a VIEW with a status of VALID.

Its practical role is to expose receipt-level amount buckets without requiring report authors to write the status-based DECODE logic themselves. The view text shows that for standard receipt types, amounts are split by AR_RECEIVABLE_APPLICATIONS.STATUS: 'APP' contributes to APPLIED_AMOUNT, 'UNAPP' to UNAPPLIED_AMOUNT, 'ACC' to ON_ACCOUNT_AMOUNT, and 'UNID' to UNIDENTIFIED_AMOUNT. The original ETRM documentation for this object is marked "(Release 10SC Only)," so the definition above reflects the legacy view text; the same object remains documented in the 12.2.2 metadata listing under the APPS schema.

Underlying Base Objects

The documented metadata identifies three referenced base objects, all resolved through synonyms: AR_CASH_RECEIPTS, AR_RECEIPT_METHODS, and AR_RECEIVABLE_APPLICATIONS.

  • AR_CASH_RECEIPTS (alias CR) — supplies the receipt header attributes: CASH_RECEIPT_ID, RECEIPT_NUMBER, RECEIPT_DATE, CURRENCY_CODE, TYPE, and the RECEIPT_METHOD_ID used in the join.
  • AR_RECEIPT_METHODS (alias RM) — supplies the receipt method NAME, exposed as the METHOD column.
  • AR_RECEIVABLE_APPLICATIONS (alias RA) — supplies application rows; AMOUNT_APPLIED and STATUS drive the aggregated amount buckets.

Joins are made on RA.CASH_RECEIPT_ID = CR.CASH_RECEIPT_ID and CR.RECEIPT_METHOD_ID = RM.RECEIPT_METHOD_ID. Rows are grouped by cash receipt ID, date, number, method name, currency code, and receipt type, producing one aggregated row per receipt (per method/currency/type combination represented in the group-by list).

Key Columns

  • CASH_RECEIPT_ID — Primary identifier of the receipt; the natural key for joining back to AR_CASH_RECEIPTS.
  • RECEIPT_NUMBER — User-facing receipt number.
  • RECEIPT_DATE — Date the receipt was entered.
  • CURRENCY_CODE — Receipt currency.
  • METHOD — Receipt method name, from AR_RECEIPT_METHODS.NAME.
  • APPLIED_AMOUNT — Sum of AMOUNT_APPLIED where application status is 'APP'.
  • UNAPPLIED_AMOUNT — Sum of AMOUNT_APPLIED where status is 'UNAPP'; this is the column most relevant to the search term for this object.
  • ON_ACCOUNT_AMOUNT — Sum where status is 'ACC'.
  • UNIDENTIFIED_AMOUNT — Sum where status is 'UNID'.

Because the four amount columns are wrapped in DECODE(CR.TYPE, 'MISC', NULL, ...), miscellaneous receipts return NULL for those amounts rather than zero. All sums use NVL to substitute 0 when no matching application rows exist.

Common Use Cases and Queries

The view is useful for receipt reconciliation, unapplied cash monitoring, and cash position reporting. A typical query retrieves receipts with a remaining unapplied balance:

SELECT receipt_number, receipt_date, currency_code,
       method, applied_amount, unapplied_amount
FROM   apps.ar_receipt_amounts_v
WHERE  unapplied_amount > 0
ORDER  BY receipt_date;

The same pattern supports aging or trending analysis by joining RECEIPT_DATE to a calendar, and receipt method reporting by grouping on METHOD. The APPLIED_AMOUNT column supports application-rate analysis, while ON_ACCOUNT_AMOUNT and UNIDENTIFIED_AMOUNT isolate those two buckets for cash management review.

Two cautions apply. First, given the legacy "(Release 10SC Only)" designation, the 12.1.1/12.2.2 definition should be verified against the installed view text before production use, particularly because the underlying tables and application status codes may have evolved. Second, the view aggregates at receipt level; for transaction-level detail, query AR_RECEIVABLE_APPLICATIONS directly.