Search Results schedule_days_from

Overview

AR_INTEREST_LINES_V is an APPS-owned view in the Oracle E-Business Suite Receivables (AR) module, documented as the "Late Charge line preview work bench." It exposes the contents of the AR_INTEREST_LINES entity joined to supporting receivable transaction and payment schedule data, providing a denormalized, read-only presentation layer for late charge (interest) lines. In EBS 12.1.1 and 12.2.2 the object carries a status of VALID and is catalogued under the AR product. Because it is a view rather than a base table, it does not store data of its own; every row is derived at query time from the underlying interest line rows and their related transactions, payment schedules, and receivables transaction types.

The view plays a reporting and integration role. Receivables uses late charge lines to compute and apply finance charges on overdue items, and the preview work bench surfaces those computed values so that users and downstream processes can inspect the interest amounts, rates, and processing outcome before or after the charge is generated. The presence of PROCESS_MESSAGE and PROCESS_STATUS columns links directly to the search term "process_message," indicating that this view is used to diagnose why a late charge line succeeded or failed during the interest processing concurrent program.

Underlying Base Objects

The view text is defined over four base objects, all referenced in the APPS schema as synonyms:

• AR_INTEREST_LINES (aliased L) — the primary driver, supplying interest line identifiers, amounts, dates, rates, organization, processing message/status, and the object version number.
• AR_PAYMENT_SCHEDULES (aliased PS) — outer-joined on PAYMENT_SCHEDULE_ID, providing the schedule context for each interest line.
• RA_CUSTOMER_TRX (aliased CT) — outer-joined via PS.CUSTOMER_TRX_ID, supplying TRX_NUMBER and DOC_SEQUENCE_VALUE for the originating transaction.
• AR_RECEIVABLES_TRX (aliased RT) — outer-joined on RECEIVABLES_TRX_ID, supplying the receivables transaction name (exposed as REC_TRX_NAME).

All joins to PS, CT, and RT are outer joins (+), so interest lines are retained even when the related schedule, transaction, or receivables transaction type cannot be resolved.

Key Columns

• INTEREST_LINE_ID / INTEREST_HEADER_ID — primary identifier and the header that groups the line.
• PAYMENT_SCHEDULE_ID / ORIGINAL_TRX_ID — links to the schedule and originating transaction.
• OUTSTANDING_AMOUNT, AMOUNT_DUE_ORIGINAL, AMOUNT_DUE_REMAINING — monetary basis for the charge.
• DAYS_OVERDUE_LATE, DAYS_OF_INTEREST, SCHEDULE_DAYS_FROM/TO — timing inputs driving the calculation.
• INTEREST_CHARGED, FINANCE_CHARGE_CHARGED, DAILY_INTEREST_CHARGE, INTEREST_RATE — computed charge and rate values.
• DUE_DATE, PAYMENT_DATE, LAST_CHARGE_DATE, ACTUAL_DATE_CLOSED, RATE_START_DATE, RATE_END_DATE — date context.
• PROCESS_MESSAGE / PROCESS_STATUS — outcome and diagnostic text from interest processing.
• ORG_ID — multi-org operating unit discriminator.
• TRX_NUMBER, DOC_SEQUENCE_VALUE, REC_TRX_NAME — descriptive values from the joined objects.
• OBJECT_VERSION_NUMBER — optimistic locking token.

Common Use Cases and Queries

A frequent scenario is reviewing late charge lines for a specific operating unit and their processing outcome:

• SELECT interest_line_id, outstanding_amount, interest_charged, process_status, process_message FROM ar_interest_lines_v WHERE org_id = :p_org_id AND process_status = 'ERROR';
• SELECT trx_number, rec_trx_name, interest_rate, days_of_interest, finance_charge_charged FROM ar_interest_lines_v WHERE original_trx_id = :p_trx_id;

These queries support troubleshooting the interest processing concurrent program (via PROCESS_MESSAGE), reconciling finance charges against payment schedules, and building late charge preview reports. Joins to the customer transaction and receivables transaction allow the line to be presented alongside its transaction number and charge type without re-deriving the relationships.