Search Results invoicing_reason




Overview
Explore in AI Chat

Overview

APPS.AR_INV_ACT_V is a reporting view in the Oracle E-Business Suite Receivables module (12.1.1 and 12.2.2) that consolidates active application activity against customer transactions — invoices, credit memos, debit memos, and chargebacks. It presents one row per applied receivable application together with the associated payment schedule, transaction header, currency, and decoded lookup descriptions. The view is built on a UNION ALL of two branches: the first branch reports active applications applied to a payment schedule, while the second branch reports applications originating from a credit memo payment schedule. Because it exposes translated lookup meanings and original component amounts (line, tax, freight, and charges), it is particularly useful for aging-style, cash application, and reconciliation reporting where human-readable values are required.

The object is central to questions about application reasons, because the documented view text decodes INVOICING_REASON and CREDIT_MEMO_REASON lookup types through the AR_LOOKUPS view. A user searching for "invoicing_reason" is typically looking to resolve a numeric REASON_CODE stored on RA_CUSTOMER_TRX_ALL into its descriptive meaning, which this view supplies via the aliased AR_LOOKUPS joins arlk3 and arlk4.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is owned by APPS and references the following base objects:

  • AR_RECEIVABLE_APPLICATIONS_ALL (synonym) — the driving table, aliased APP, supplying application date, amount applied, applied-from amount, receipt ID, customer transaction ID, and status.
  • AR_PAYMENT_SCHEDULES (synonym) — aliased PS, supplying transaction number, payment schedule ID, terms sequence, class, and original line/tax/freight/charges amounts.
  • RA_CUSTOMER_TRX_ALL (synonym) — aliased CT, joined outer to the application on CUSTOMER_TRX_ID, supplying the transaction currency code and the REASON_CODE that drives the lookup decode.
  • AR_LOOKUPS (view) — joined four times (arlk1 through arlk4) to resolve INV/CM class, PAYMENT_TYPE status, INVOICING_REASON, and CREDIT_MEMO_REASON meanings. All four joins are outer ((+)), so rows survive even when no lookup match exists.
  • AR_CASH_RECEIPTS_ALL (synonym) — referenced indirectly through the scalar subquery that resolves the currency code for receipt-driven applications.
  • AR_ADJUSTMENTS (synonym) — listed among referenced objects; adjustments are surfaced in the activity set represented by the view.

Applications are filtered to active rows only: STATUS = 'APP' and DISPLAY = 'Y'.

Key Columns

  • APPLIED_PAYMENT_SCHEDULE_ID / PAYMENT_SCHEDULE_ID — identifies the schedule receiving the application.
  • CUSTOMER_TRX_ID / TRX_NUMBER — the transaction header and its user-facing number for the schedule.
  • APPLY_DATE — date the application was applied; the primary basis for period reporting.
  • AMOUNT_APPLIED (signed) — derived as -NVL(AMOUNT_APPLIED_FROM, AMOUNT_APPLIED), giving signed amounts suitable for netting.
  • Currency code expression — resolved from the cash receipt or the applied transaction currency, falling back to CT.INVOICE_CURRENCY_CODE.
  • arlk1.meaning — decoded INV/CM class (Invoice or Credit Memo).
  • arlk2.meaning — decoded PAYMENT_TYPE status.
  • Reason meaning — NVL(arlk3.meaning, arlk4.meaning), i.e., the invoicing reason when present, otherwise the credit memo reason.
  • CASH_RECEIPT_ID — links back to the receipt for cash-based applications.
  • LINE_AMOUNT, TAX_AMOUNT, FREIGHT_AMOUNT, CHARGES_AMOUNT, TOTAL_AMOUNT — original schedule components and their sum, defaulted to zero via NVL(...,0).

Common Use Cases and Queries

The view is well suited to cash application review, reason-code analysis, and reconciliation of applied amounts by transaction. A common query decodes the invoicing reason for active applications:

SELECT trx_number,
       apply_date,
       amount_applied,
       reason_meaning
FROM   apps.ar_inv_act_v
WHERE  reason_meaning IS NOT NULL
  AND  apply_date >= :from_date
  AND  apply_date <  :to_date;

Filtering by transaction class supports credit memo versus invoice reporting:

SELECT trx_number, total_amount, amount_applied
FROM   apps.ar_inv_act_v
WHERE  meaning = 'Credit Memo';

Note that the inner query column names are not fully retained in the excerpt; when querying, reference the column aliases shown in the select list (for example trx_number, apply_date, amount_applied, reason_meaning) or the underlying column names as exposed. As with all APPS views, access should be read-only and governed by the appropriate Receivables responsibilities.