Search Results ar_interest_lines




Overview
Explore in AI Chat

Overview

AR_INTEREST_LINES_PKG is a PL/SQL package that supports the Oracle Receivables interest and finance charge calculation process. Interest lines in Receivables represent the individual charges assessed against delinquent transactions or overdue payment schedules when a customer fails to pay by the due date. Each interest line records the computed daily interest charge, the outstanding amount, the number of days overdue, the interest rate applied, the interest charged, and any associated finance charges. The package body provides a controlled API layer for maintaining these records, shielding callers from direct DML against the underlying table and enforcing the locking and validation conventions expected by the Receivables module. It belongs to the broader interest processing infrastructure that includes header-level logic (AR_INTEREST_HEADERS) and batch processes that generate interest for groups of overdue items.

Key Procedures and Functions

The package exposes four documented procedures:

  • LOCK_LINE — Acquires a pessimistic lock on a specific interest line row in AR_INTEREST_LINES prior to update or delete, ensuring that no concurrent session modifies the record while the caller holds it. As reflected in the source excerpt, the routine opens a cursor with a FOR UPDATE NOWAIT clause keyed on the interest_line_id, fetches the row, and returns an error status with an encoded message when the record is not found.
  • VALIDATE_LINE — Verifies that the supplied interest line attributes are internally consistent and acceptable before persistence. It serves as the pre-check that custom callers should invoke to avoid committing invalid interest data.
  • UPDATE_LINE — Persists changes to an existing interest line, updating the charge amounts, dates, rate information, and audit columns (last update date, user, login). This is the principal write path for maintaining interest line detail after calculation or adjustment.
  • DELETE_LINE — Removes an interest line record, typically after a regeneration or reversal of interest charges.

Each procedural call follows the standard Receivables API conventions, returning a return status plus message count and message data for error propagation.

Tables Accessed

  • AR_INTEREST_LINES — The primary table for this package. It stores the individual interest line records, including the interest line identifier, interest header reference, payment schedule reference, original transaction identifiers, daily interest charge, outstanding amount, days overdue, days of interest, interest charged, finance charge charged, amounts due, interest rate, rate start and end dates, schedule day ranges, last charge date, due date, actual close date, process status, and organization identifier. LOCK_LINE reads it for update, UPDATE_LINE writes to it, and DELETE_LINE removes rows from it.
  • AR_INTEREST_HEADERS — The header table that groups interest lines into an interest run. It provides the interest_header_id that keys each line, linking individual charges to their parent batch or calculation header.

Usage Notes

This package is invoked as a supporting API for interest processing rather than as an entry point in its own right. It is called by higher-level Receivables interest programs and by the forms used to review or adjust assessed interest, and it is available to custom code that must create, amend, or remove interest lines while respecting Receivables locking and validation rules. Custom callers should first invoke LOCK_LINE to secure the row, then VALIDATE_LINE to confirm the data, then UPDATE_LINE or DELETE_LINE to apply the change. Because the package returns status and message information through the standard FND API conventions, callers must inspect the return status and message data after every call. In Oracle EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is referenced through APPS synonyms; ETRM reports no other packages referencing it directly, so it is best treated as a lower-level utility within the interest framework. Direct DML against AR_INTEREST_LINES is strongly discouraged, as it bypasses the locking and validation logic provided here.