Results for “reason_meaning”

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

Overview

AR_INV_ACT_V is an Oracle Applications (APPS) view defined in the Receivables (AR) module. According to the documented ETRM metadata, its description is marked (Release 11.5 Only), indicating that the view originated in the 11.5.x code line and is retained in the 12.1.1 and 12.2.2 schemas primarily for backward compatibility. Its status remains VALID in the repository.

The view presents the "active applications" activity relating to invoices, credit memos, and their associated payment schedules. It exposes the applied-payment schedules, the transaction number, application date, applied amounts, currency, and the various lookup meanings that classify the transaction and application. In effect, it provides a flattened, descriptive representation of how payments and credit memos have been applied against receivables items, which makes it suitable for activity and reconciliation reporting rather than for transactional processing. Because the view embeds lookup joins for descriptive meanings (lookup meaning columns through AR_LOOKUPS) and computes currency codes conditionally, it is typically consumed by custom reports, extracts, and integration queries where a single, denormalized row per application is required.

Underlying Base Objects

The documented base objects referenced by AR_INV_ACT_V in 12.2.2 are: AR_ADJUSTMENTS (synonym), AR_CASH_RECEIPTS_ALL (synonym), AR_LOOKUPS (view), AR_PAYMENT_SCHEDULES (synonym), AR_RECEIVABLE_APPLICATIONS_ALL (synonym), and RA_CUSTOMER_TRX_ALL (synonym).

The principal driving table is AR_RECEIVABLE_APPLICATIONS_ALL (aliased APP), which supplies the application records. It is joined to AR_PAYMENT_SCHEDULES (PS) on PAYMENT_SCHEDULE_ID, to RA_CUSTOMER_TRX_ALL (CT) as an outer join on CUSTOMER_TRX_ID, and to multiple instances of AR_LOOKUPS (ARLK1–ARLK4) through outer-joined lookup types such as INV/CM, PAYMENT_TYPE, INVOICING_REASON, and CREDIT_MEMO_REASON. Cash receipt currency is resolved via a scalar subquery against AR_CASH_RECEIPTS_ALL. The metadata associates AR_ADJUSTMENTS with the view's object set, consistent with the view's role in reconciling applied activity across the application tables. The definition is a UNION ALL of at least two branches: one for standard active applications (STATUS = 'APP', DISPLAY = 'Y') and one that shows active applications for a given credit memo payment schedule.

Key Columns

• TRX_NUMBER — transaction number of the underlying invoice or credit memo.
• APPLY_DATE — date on which the payment or credit was applied.
• CASH_RECEIPT_ID / CUSTOMER_TRX_ID / PAYMENT_SCHEDULE_ID — identifiers linking the application to the receipt, transaction, and schedule.
• TERMS_SEQUENCE_NUMBER and CLASS — schedule sequencing and transaction class (invoice versus credit memo).
• Applied amount (derived from AMOUNT_APPLIED_FROM/AMOUNT_APPLIED) — signed so that the two UNION branches represent debit and credit perspectives.
• MEANING columns — lookup meanings for class, payment type, and reason codes.
• LINE_AMOUNT, TAX_AMOUNT, FREIGHT_AMOUNT, CHARGES_AMOUNT, TOTAL_AMOUNT — original schedule amounts, summed in TOTAL_AMOUNT.

Common Use Cases and Queries

Typical usage includes receivable activity reports, application reconciliations, and integration extracts that need application detail with decoded meanings.

• Listing applied activity for a transaction: SELECT trx_number, apply_date, total_amount FROM apps.ar_inv_act_v WHERE trx_number = :p_trx_number;
• Reconciling applications for a receipt: SELECT cash_receipt_id, trx_number, total_amount FROM apps.ar_inv_act_v WHERE cash_receipt_id = :p_receipt_id;
• Extracting application detail for a date range: SELECT trx_number, apply_date, payment_schedule_id FROM apps.ar_inv_act_v WHERE apply_date BETWEEN :p_from AND :p_to;

Because the view is documented as 11.5-only, implementers should verify its continued suitability against 12.x functionality before depending on it in new customizations.