Search Results receivables_charges_applied




Overview
Explore in AI Chat

Overview

APPS.ARBV_CREDIT_MEMO_APPLICATIONS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Receivables module. It is owned by the APPS schema and carries the FND Design Data reference AR.ARBV_CREDIT_MEMO_APPLICATIONS; its status is VALID as documented in ETRM for both 12.1.1 and 12.2.2. The view presents information about credits issued to a customer as settlement for one or more debit items, specifically the credit memo side of the receivables application model.

Because it is a BIS view, it is intended for reporting, ad-hoc inquiry, and downstream integration rather than for direct transactional maintenance. It surfaces application-level and line-level amounts, tax, freight, and receivables charges applied against debit items, along with the applied payment schedule and transaction line identifiers that tie the credit back to specific open items and lines. The view also exposes audit columns and the operating unit identifier, making it suitable for multi-org reporting and for reconciliation of credit memo applications to their origin transactions.

Underlying Base Objects

The documented dependency confirms that APPS.ARBV_CREDIT_MEMO_APPLICATIONS references AR_RECEIVABLE_APPLICATIONS, which appears in the dependency listing as a synonym. AR_RECEIVABLE_APPLICATIONS is the core Receivables table that stores the linkage between a payment or credit and the debit items it settles, including the amounts applied at the application level. The view is not referenced by any other database object, so it functions as a leaf-level reporting construct with no dependent database objects of its own.

In practice, the view projects a credit memo-oriented perspective of that base table, exposing both application header figures and line-level detail, including the transaction line and applied payment schedule identifiers needed to join back to AR_PAYMENT_SCHEDULES and the transaction line tables. All access is through the APPS schema, so qualified references such as APPS.ARBV_CREDIT_MEMO_APPLICATIONS are appropriate in custom reports.

Key Columns

The extracted column set includes identifiers, amounts, dates, and audit fields:

Common Use Cases and Queries

Typical use cases include tax reconciliation on credit applications, credit memo application reporting by operating unit, aging analysis using DAYS_LATE, and subledger accounting analysis using USSGL_TRANSACTION_CODE. A basic query to retrieve applied tax, restricted to the current operating unit, is:

SELECT receivable_application_id, customer_trx_id, applied_payment_schedule_id, transaction_line_id, amount_applied, tax_amount_applied, freight_amount_applied, receivables_charges_applied, apply_date, days_late
FROM apps.arbv_credit_memo_applications
WHERE org_id = :p_org_id
AND apply_date BETWEEN :p_from AND :p_to
ORDER BY apply_date, customer_trx_id;

To isolate the tax component of credit applications for tax analysis, aggregate TAX_AMOUNT_APPLIED by transaction and date. Because the view exposes the applied payment schedule and transaction line identifiers, it joins cleanly to AR_PAYMENT_SCHEDULES and the transaction tables for drill-down reporting. Consumers should note that the view is a reporting abstraction and should not be used for DML; any adjustment must be performed through the standard Receivables application forms or the underlying API layer.