Search Results customer_reference




Overview
Explore in AI Chat

Overview

The AR_ICR_LINES_TRX_V view is a Receivables (AR) reporting object owned by the APPS schema. It presents a consolidated, transaction-level picture of payment schedule lines together with their associated customer, transaction, and terms attributes. The name's "ICR" component reflects its role in Interactive Collections/Receivables-style reporting, where collectors and analysts require a joined, denormalized dataset spanning invoices, debit memos, credit memos, payments, and applications.

The view is documented as Release 115 Only, meaning its definition originated in Release 11.5 of Oracle E-Business Suite and remains catalogued as VALID in the 12.2.2 data model. Its principal design goal is to spare report authors and integration developers from reconstructing the complex joins among payment schedules, receivables applications, customer accounts, and parties. Because it relies on the ARPT_SQL_FUNC_UTIL package and ARPT_SQL_FUNC_UTIL.GET_TRX_TYPE_DETAILS calls, it must be queried through the APPS schema context so that those PL/SQL functions and the underlying synonyms resolve correctly. In 12.1.1 and 12.2.2, it functions primarily as a read-only reporting and integration surface rather than a maintenance view.

Underlying Base Objects

The documented base objects for AR_ICR_LINES_TRX_V are:

The view joins these through ordered nested-loop access (the hint ORDERED USE_NL(PS, TRX, CI, CUST_ACCT, PARTY, SITE_USES, BS)), with the payment schedule as the anchor.

Key Columns

The metadata does not expose an ACCOUNT_DESCRIPTION column; users searching that term should map to CUSTOMER_NUMBER, CUSTOMER_NAME, or the interface attributes.

Common Use Cases and Queries

Typical scenarios include collections aging reports, customer statement reconciliation, and outbound integration extracts that require payment schedule lines with customer and transaction context.

SELECT payment_schedule_id, trx_number, customer_number,
       customer_name, due_date, amount_due_remaining, class_meaning
FROM   apps.ar_icr_lines_trx_v
WHERE  customer_id = :p_customer_id
AND    class IN ('INV','CM','DM')
ORDER BY due_date;

For collections prioritization, filter on AMOUNT_DUE_REMAINING > 0 and past-due dates. For integration, select the INTERFACE_HEADER_ATTRIBUTE1..10 columns alongside transaction identifiers. Because the view invokes PL/SQL functions per row, queries should always be schema-qualified as APPS.AR_ICR_LINES_TRX_V and constrained to avoid full scans across large Receivables volumes.