My Oracle Support Banner

EAR9.2 - DOCUMENT Field Is Not Getting Updated As payment_id_item.REF_VALUE By Payment Predictor When More Than One Payment in Deposit (Doc ID 2549929.1)

Last updated on JUNE 03, 2019

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 PUM 11 version, Payment Predictor

ACTUAL BEHAVIOR
---------------
Payment predictor creates OA item with document field as deposit bu+deposit id+ payment seq num.

EXPECTED BEHAVIOR
-----------------------
Payment predictor should populated item id as a document so that auto maintenance can match credit and debit.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create deposit with two payments with payment predictor check and give item reference where item doesn't exist.
2. Run payment predictor and the arupdate
3. Check ITEM.DOCUMENT field, it is not same as item id given in item reference.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot run auto maintenance to match debit and credit as document field doesn't have item id.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.