EAR9.2: Payment Predictor #OVERDUE is Applying Payment Completely to Principle When Item Has an Overdue Charge Entry Reason With Sequence Greater Than 9. (Doc ID 1932838.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

PeopleSoft Enterprise FIN Receivables - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

On : 9.2 version, Payment Predictor

ACTUAL BEHAVIOR
---------------
Trying to configure #OVERDUE to apply payments to overdue charges before applying to principle.
There are 22 entry reasons for overdue charges.
When an item has an overdue charge entry reason with a sequence < 9, payment are applied as expected - that is the payment is applied to the overdue charge first before applying remainder (if any) to principle.
However, when there is an overdue charge with an entry reason with a sequence > 9, payments are applied to principle.

EXPECTED BEHAVIOR
-----------------------
When there is an overdue charge with an entry reason with a sequence > 9, payments should be applied to the overdue charge first before applying remainder to principle.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Setup Overdue Charging with more than 9 different entry reasons.
  2. Run overdue charge process for an overdue charge ID where entry reason sequence > 9.
  3. Run ARUPDATE to post overdue charges.
  4. Create a regular deposit.
  5. Run payment predictor for #OVERDUE.
  6. Run ARUPDATE.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot use payment predictor to apply payments to overdue charges.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms