EAR9.1+: Deposit Status Value Not Set To 'P' For Partial Payments Done Using Payment Predictor process(DTL_TLR algorithm group). (Doc ID 2104355.1)

Last updated on NOVEMBER 28, 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 Online Deposit

ACTUAL BEHAVIOR
---------------

After applying Payments using Payment Predictor process, deposit status for Partial Payments did not change from 'N' to 'P'.

EXPECTED BEHAVIOR
-----------------------

After applying Payments using Payment Predictor process, deposit status for Partial Payments should change from 'N' to 'P'.

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

  1. Set up 'DTL_TLR' Predictor method.
  2. Setup default Payment Predictor method at customer level.
  3. Enter 1 pending item for the customer and Run ARUPDATE process.
  4. Enter a Deposit having 2 payment lines/sequences with detail references to partially pay a single item.
  5. Run Payment Predictor process.
  6. Run ARUPDATE process.
  7. The Deposit status for the Partial Payment did not change from 'N' to 'P'.

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