Issues in Prepayment Handling in Custom AP Aging Report (As-of-Date Logic – Oracle Fusion)

Summary:

Incorrect remaining amount calculation in custom AP Aging Report due to improper handling of multiple prepayment applications (Invoice-Level and Line-Level), including application and unapplication as of report date.

Content (please ensure you mask any confidential information):

We are developing a custom AP Aging Report in Oracle Fusion to replicate seeded InvoiceAgingAsOfDateDM logic because we have a requirement to include installment level details because of business requirements.

We are facing issues in calculating the net prepayment applied amount as of a given report date (:p_to_date).

In our environment, prepayments are applied in two different ways:

Invoice-Level Prepayment Application (Distribution Based)