Search Results grace_days

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:

• AR_PAYMENT_SCHEDULES (synonym) — the driving table, aliased PS, supplying transaction number, due dates, terms, class, currency, and amounts.
• RA_CUSTOMER_TRX (synonym) — the transaction header, aliased TRX, providing transaction type and interface header attributes.
• AR_RECEIVABLE_APPLICATIONS (synonym) — aliased APP, used to sum AMOUNT_APPLIED for payment-class rows.
• HZ_CUST_ACCOUNTS, HZ_PARTIES, HZ_CUST_SITE_USES, HZ_CUSTOMER_PROFILES (synonyms) — customer account number, party name, site location, and profile attributes such as discount grace days.
• RA_TERMS (synonym) — payment terms flags governing discount calculation.
• AR_CONS_INV (synonym) — consolidated billing number source.
• RA_BATCH_SOURCES (synonym) — aliased BS, batch source context.
• ARPT_SQL_FUNC_UTIL and ARP_DEDUCTION (packages) — PL/SQL utilities that decode transaction type details and lookup meanings at runtime.

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

• PAYMENT_SCHEDULE_ID — unique identifier of the payment schedule line; the view's grain.
• TRX_NUMBER and CUSTOMER_TRX_ID — transaction identity, with -1 substituted when no customer transaction exists.
• AMOUNT_DUE_REMAINING — computed as the negated sum of applied amounts for payment class, otherwise the stored remaining amount.
• CUSTOMER_NAME, CUSTOMER_NUMBER — party name (truncated to 50 bytes via SUBSTRB) and account number.
• LOCATION — resolved from site uses, branching on the schedule class (BR, PMT, or default).
• CLASS, CLASS_MEANING — schedule class code and its INV/CM lookup meaning.
• TYPE_NAME, ALLOW_OVERAPPLICATION_FLAG, NATURAL_APPLICATION_ONLY_FLAG, CREATION_SIGN — transaction type attributes retrieved via ARPT_SQL_FUNC_UTIL.GET_TRX_TYPE_DETAILS.
• DUE_DATE, TRX_DATE, TERMS_SEQUENCE_NUMBER, TERM_ID — scheduling and terms data.
• DISCOUNT_TAKEN_EARNED, DISCOUNT_TAKEN_UNEARNED, GRACE_DAYS, CALC_DISCOUNT_ON_LINES_FLAG, PARTIAL_DISCOUNT_FLAG — discount-related attributes.
• INTERFACE_HEADER_ATTRIBUTE1 through 10 — flexible descriptive attributes carried from the transaction header.

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.