Search Results ar_interest_lines_u1

Overview

AR.AR_INTEREST_LINES_ALL is the transactional detail table that stores the individual Late Charges interest document lines generated by Oracle Receivables during late charge and interest calculation processing. Each row represents a single computed interest charge against a specific payment schedule, capturing the overdue amount, the aging window applied, the interest rate in effect, and the resulting interest amount. The table sits beneath AR_INTEREST_HEADERS_ALL, which represents the parent interest document (the generated late charge invoice), and effectively functions as its line-level counterpart.

In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the AR schema, resides in the APPS_TS_TX_DATA tablespace, and is designated with FND Design Data AR.AR_INTEREST_LINES_ALL. It is a multi-org enabled object, evidenced by the presence of ORG_ID, and carries the standard WHO audit columns plus OBJECT_VERSION_NUMBER for optimistic locking, which is significant for release 12.2.2 online patching and OAF-based validation.

From a Data Vault modeling perspective, the mined foreign key structure suggests a hub-leaning classification. The table resolves identifiers for interest lines, headers, payment schedules, and original transactions, and its grain is naturally tied to the relationships it materializes between a payment schedule and a generated interest charge. Analysts may therefore treat it as a link-favored structure anchored on the INTEREST_LINE_ID business key, with the descriptive financial measures behaving as satellite attributes.

Key Information Stored

The surrogate primary key is INTEREST_LINE_ID, enforced by the unique index AR_INTEREST_LINES_U1. A second unique index, AR_INTEREST_LINES_U2, spans INTEREST_HEADER_ID and INTEREST_LINE_ID; this composite is a business-key candidate that reflects the natural parent-child line sequence within a given interest document. Both indexes reside in APPS_TS_TX_IDX.

• INTEREST_HEADER_ID — foreign key to AR_INTEREST_HEADERS_ALL.INTEREST_INVOICE_ID, identifying the parent interest document.
• PAYMENT_SCHEDULE_ID — foreign key to AR_PAYMENT_SCHEDULES_ALL.PAYMENT_SCHEDULE_ID, the overdue installment being charged.
• OUTSTANDING_AMOUNT — the overdue late payment amount used as the interest base.
• DAYS_OVERDUE_LATE and DAYS_OF_INTEREST — the number of days late and the days actually charged.
• INTEREST_CHARGED and FINANCE_CHARGE_CHARGED — the computed interest and the FINCHRG adjustment deducted from the overdue amount.
• INTEREST_RATE, RATE_START_DATE, RATE_END_DATE — the rate applied and its effectivity window.
• SCHEDULE_DAYS_FROM and SCHEDULE_DAYS_TO — the aging bucket range that selected the rate.
• AMOUNT_DUE_ORIGINAL and AMOUNT_DUE_REMAINING — copied payment schedule balances.
• ORIGINAL_TRX_ID, ORIGINAL_TRX_CLASS, CASH_RECEIPT_ID — linkage back to the originating transaction or receipt.
• DUE_DATE, LAST_CHARGE_DATE, ACTUAL_DATE_CLOSED — schedule dates governing accrual.
• RECEIVABLES_TRX_ID — foreign key to AR_RECEIVABLES_TRX_ALL, defining the activity used for the charge.
• PROCESS_STATUS and PROCESS_MESSAGE — outcome of the late charge program run.

Common Use Cases and Queries

The primary reporting use case is reconciling generated late charge invoices to their underlying overdue installments. A typical query joins lines to the payment schedule to verify outstanding balances and aging:

• Listing all lines for an interest document: SELECT interest_line_id, payment_schedule_id, outstanding_amount, days_of_interest, interest_charged FROM ar_interest_lines_all WHERE interest_header_id = :header_id.
• Interest accrual audit by customer: join to AR_PAYMENT_SCHEDULES_ALL on PAYMENT_SCHEDULE_ID to retrieve the customer and trx number, then aggregate INTEREST_CHARGED by period.
• Rate and bucket validation: group by SCHEDULE_DAYS_FROM, SCHEDULE_DAYS_TO, and INTEREST_RATE to confirm the correct aging band was applied.
• Error diagnostics from the Late Charges program: filter on PROCESS_STATUS and review PROCESS_MESSAGE.
• Drill-back to the original transaction or receipt using ORIGINAL_TRX_ID, ORIGINAL_TRX_CLASS, and CASH_RECEIPT_ID.

Related Objects

The most significant related objects and their join columns are:

• AR_INTEREST_HEADERS_ALL — parent header via INTEREST_HEADER_ID = INTEREST_INVOICE_ID.
• AR_PAYMENT_SCHEDULES_ALL — via PAYMENT_SCHEDULE_ID.
• AR_RECEIVABLES_TRX_ALL — via RECEIVABLES_TRX_ID.
• RA_CUSTOMER_TRX_LINES_ALL — references this table through INTEREST_LINE_ID, linking the generated invoice line to its interest line.
• AR_LATE_CHARGE_DOC_GT, AR_TRX_LINES_GT, and AR_TRX_LINES_TMP_GT — global temporary staging tables that reference INTEREST_LINE_ID during late charge document creation and validation.

These relationships confirm that AR_INTEREST_LINES_ALL is the central intersection between overdue receivables activity, rate configuration, and the resulting interest-bearing transactions.