Results for “arbv_credit_memo_applications”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ARBV_CREDIT_MEMO_APPLICATIONS is a read-only Oracle EBS view owned by the APPS schema in the Receivables (AR) module. It exposes a filtered subset of rows from AR_RECEIVABLE_APPLICATIONS, restricted to those where APPLICATION_TYPE equals 'CM'. In Oracle Receivables, this application type identifies credit memo applications rather than cash receipt applications, so the view concentrates specifically on the linkage between credit memos and the transactions, payment schedules, and lines to which they have been applied.

Because the view is declared WITH READ ONLY, it is intended exclusively for query, reporting, and integration purposes. It carries the UNIQUE ATTRIBUTES comment in its SELECT list, advising the optimizer that the primary key attributes of the underlying table are preserved. The object is reported as VALID in the ETRM 12.2.2 metadata, meaning it compiles cleanly against its base object and is available for use in both 12.1.1 and 12.2.2 environments. Standard Receivables inquiry screens, credit memo application reports, and custom extracts frequently rely on this view to isolate credit memo activity without writing repetitive filter logic.

Underlying Base Objects

The view is defined over a single documented base object: AR_RECEIVABLE_APPLICATIONS, referenced through its synonym. No joins, unions, or subqueries are present. The definition is a straightforward projection of selected columns with one restrictive predicate, RA.APPLICATION_TYPE = 'CM', applied to the base table.

This means every row returned corresponds to an application record in AR_RECEIVABLE_APPLICATIONS whose application type denotes a credit memo. The reliance on a synonym rather than the fully qualified APPS table name follows common EBS coding standards and supports multi-org access patterns. Since the view performs no aggregation, its cardinality is a direct subset of the base table, and any change to credit memo applications in Receivables is immediately reflected in query results.

Key Columns

• RECEIVABLE_APPLICATION_ID — Primary identifier for the application record; the unique attribute emphasized by the view's comment.
• AMOUNT_APPLIED — The amount of the credit memo applied to the target transaction. The documented column list also exposes AMOUNT_APPLIED_BASE for the ledger currency equivalent.
• APPLY_DATE — The date on which the application was made, central to period-based reporting.
• LINE_APPLIED / LINE_AMOUNT_APPLIED — Line-level amounts applied against transaction lines.
• TAX_APPLIED, FREIGHT_APPLIED, RECEIVABLES_CHARGES_APPLIED — Component breakdowns showing how the applied amount is distributed across tax, freight, and receivables charges.
• DAYS_LATE — A derived measure indicating the number of days the applied transaction was overdue at application time.
• USSGL_TRANSACTION_CODE — The accounting transaction code associated with the application.
• ORG_ID — Operating unit identifier, supporting multi-org reporting.
• CUSTOMER_TRX_ID — The transaction to which the credit memo is applied.
• APPLIED_PAYMENT_SCHEDULE_ID and TRANSACTION_LINE_ID / APPLIED_CUSTOMER_TRX_LINE_ID — Identifiers for the invoice payment schedule and line against which the credit memo was applied.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard WHO audit columns for change tracking.

Common Use Cases and Queries

The view supports credit memo application analysis, reconciliation, and multi-org reporting. A typical query lists applications with amounts and dates for a given transaction:

• SELECT receivable_application_id, customer_trx_id, amount_applied, apply_date FROM arbv_credit_memo_applications WHERE org_id = :p_org_id AND apply_date BETWEEN :p_start AND :p_end;
• SELECT customer_trx_id, SUM(amount_applied) FROM arbv_credit_memo_applications WHERE org_id = :p_org_id GROUP BY customer_trx_id; — aggregate credit memo amounts per transaction.
• SELECT receivable_application_id, line_applied, tax_applied, freight_applied, receivables_charges_applied FROM arbv_credit_memo_applications WHERE customer_trx_id = :p_trx_id; — detailed component breakdown.

Because the view is read-only and unfiltered beyond application type, developers should always constrain queries by ORG_ID and APPLY_DATE or CUSTOMER_TRX_ID to maintain performance. For scenarios requiring cash receipt applications or other application types, query AR_RECEIVABLE_APPLICATIONS directly with an appropriate APPLICATION_TYPE predicate.