Search Results allocated_receipt_amount_base




Overview
Explore in AI Chat

Overview

APPS.ARBV_CASH_APPLICATIONS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Receivables (AR) module. It is registered in FND Design Data as AR.ARBV_CASH_APPLICATIONS and holds a VALID status in the APPS schema. The view presents information about cash applied to customer transactions, exposing one row per receivable application (that is, per payment-to-invoice or payment-to-transaction association). Because it is a BIS view, it is intended primarily for reporting, analytical, and integration use rather than for transactional processing. It is commonly queried by receivables analysts, collections staff, and reporting developers who need a denormalized, read-friendly perspective on how cash receipts are applied against open customer transactions, including functional and base currency amounts, discounts, and application status.

Underlying Base Objects

Per the documented view metadata, ARBV_CASH_APPLICATIONS is defined over the base object AR_RECEIVABLE_APPLICATIONS, accessed through its APPS synonym. AR_RECEIVABLE_APPLICATIONS is the core transactional table in Oracle Receivables that stores every application of cash (receipts, credit memos, on-account cash, and other adjustments) against customer transactions and their payment schedules. The view therefore inherits the grain of that table — one record per application event — and layers on decoded, "_LA" (lookup-meaning) columns and base-currency equivalents that make the data more directly consumable for reporting. Additional denormalized identifiers such as CASH_RECEIPT_ID, TRANSACTION_ID, TRANSACTION_LINE_ID, APPLIED_PAYMENT_SCHEDULE_ID, and SET_OF_BOOKS_ID appear in the view to support joins back to receipts, transactions, and ledger contexts.

Key Columns

  • RECEIVABLE_APPLICATION_ID — Primary identifier for the application record; the natural key when joining to other AR objects.
  • AMOUNT_APPLIED / AMOUNT_APPLIED_BASE — The applied amount in the transaction currency and in the ledger (base) currency respectively.
  • ALLOCATED_RECEIPT_AMOUNT / ALLOCATED_RECEIPT_AMOUNT_BASE — The portion of the receipt allocated to the application, expressed in both the entered and base currencies. The user's search term "allocated_receipt_amount_base" maps directly to the ALLOCATED_RECEIPT_AMOUNT_BASE column, which reports the allocated receipt amount converted to the functional/base currency and is typically used for cross-currency reconciliation and reporting.
  • CROSS_CURRENCY_RATE — The exchange rate applied when the receipt currency differs from the transaction currency.
  • APPLY_DATE — The date on which the cash was applied to the transaction.
  • _LA:APPLICATION_STATUS — Decoded lookup meaning for the application status, presented as CHAR(45).
  • EARNED_DISCOUNT / UNEARNED_DISCOUNT (and their _BASE counterparts, plus LINE_, TAX_, FREIGHT_, and CHARGES_ splits) — Discount amounts taken at application time, itemized by component and reported in both currencies.
  • DAYS_LATE — Number of days by which the payment was late relative to the due date.
  • CASH_RECEIPT_ID, TRANSACTION_ID, TRANSACTION_LINE_ID, APPLIED_PAYMENT_SCHEDULE_ID, ORG_ID, SET_OF_BOOKS_ID — Foreign keys enabling joins to receipts, transactions, operating units, and ledgers.
  • COMMENTS, USSGL_TRANSACTION_CODE, LAST_UPDATE_DATE, CREATION_DATE — Supporting descriptive and audit columns.

Common Use Cases and Queries

Typical reporting scenarios include cash application analysis, unapplied or partially applied receipt reconciliation, discount utilization reporting, days-late aging, and cross-currency application review. The ALLOCATED_RECEIPT_AMOUNT_BASE column is frequently selected when analysts must compare allocated cash in the ledger currency, independent of the receipt's entered currency.

A representative query isolating the base-currency allocated receipt amount is:

  • SELECT receivable_application_id, allocated_receipt_amount, allocated_receipt_amount_base, amount_applied, apply_date, application_status_code FROM apps.arbv_cash_applications WHERE org_id = :p_org_id AND apply_date BETWEEN :p_from AND :p_to;
  • SELECT cash_receipt_id, SUM(allocated_receipt_amount_base) FROM apps.arbv_cash_applications GROUP BY cash_receipt_id; — returns total allocated cash per receipt in the base currency.
  • SELECT transaction_id, SUM(amount_applied), SUM(earned_discount + unearned_discount) FROM apps.arbv_cash_applications WHERE application_status_code = 'APP' GROUP BY transaction_id; — summarizes applied amounts and discounts by transaction.

Because the view is a reporting construct over AR_RECEIVABLE_APPLICATIONS, it should be used for query and extract purposes only; transactional updates must always be directed at the underlying base tables through the standard Receivables APIs.