EAR9.1+: AO and AU Items Due Date Populating as Item Original Due Date After Running Payment Predictor. (Doc ID 2133449.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

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

Symptoms

On : 9.1 version, Payment Predictor

ACTUAL BEHAVIOR
---------------
AO and AU items Due date populating as Item original Due date after running Payment Predictor.
When using manual payment worksheet AO and AU items have correct due date (current date).

EXPECTED BEHAVIOR
-----------------------
AO and AU items Due date should be equal to current date after running Payment Predictor.

SETUP
-----------------------

  1. Predictor method is using algorithm group #DETAIL including Any Overpayment = Generate An Item using WS-06 and Any Underpayment = Generate An Item using WS-07.
  2. Payment predictor method is linked to Receivables Options.
  3. Require Reason is enabled for System Function WS-06 and WS-07 and Predictor Reason is defined.


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

  1. Add a new pending item group for US007 and create item TST_AU1 for customer USA11 (amount 100 $) and item TST_AO1 for customer USA12 (amount 100 $).
  2. Run ARUPDATE to post items.
  3. Create a regular deposit for 97 USD. Enter detailed item reference for customer USA11 (Pay Amt 100 $) and enable Payment Predictor.
  4. Create another regular deposit for 103 USD. Enter detailed item reference for customer USA12 (Pay Amt 100 $) and enable Payment Predictor.
  5. Run payment predictor.
  6. Verify results in PS_PENDING_ITEM, DUE_DT for AO and AU are based on original item DUE_DT.
  7. Run ARUPDATE to post payment.
  8. Due date for AU2 is same as original item. Due date for AU2 should be current date (date payment predictor was running).
  9. Due date for AO1 is same as original item. Due date for AO1 should be current date (date payment predictor was running).


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, AO and AU items have an incorrect due date.

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