My Oracle Support Banner

EAR 9.2: Payment Worksheet Created By A Prior Payment Predictor Run Allows For An Item To Be Selected Even If Currently This Same Item Is Being Used On Another Worksheet (Doc ID 2711670.1)

Last updated on SEPTEMBER 16, 2020

Applies to:

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

Symptoms


The Payment Worksheet component (PAYMENT_WS_IC) is not issuing the expected Error Message when manually adding an Item ID on a previously Payment Predictor generated Payment Worksheet, if that Item is already currently being used in another yet to be posted Payment Worksheet.

This happens if the Item's Line is not 0, such as 1.

REPLICATION STEPS:

    1.- Log into the FSCM Online Application as a Receivables User.
    2.- Define a new Payment Predictor Method using the #REFS algorithm.
    3.- Link that Payment Predictor Method to a specific Customer ID at the Bill To Options set up level.
    4.- Create a new Pending Item Group with 3 new Items (ITEM_1, ITEM_2, and ITEM_3), all for 100 USD, and for the same Customer ID. Ensure that for all three, the Item Line is not the default 0 value, but 1. Set the Post Action to Batch Standard.
    5.- Launch AR Update for Pending Items option, to post the new Group.
    6.- Create a new Deposit, with two Payments (PYMNT_1, and PYMNT_2), each for 200 USD. At the References level, link Payment ID PYMNT_1 to ITEM_1 and ITEM_2, and Payment ID PYMNT_2 to ITEM_2 and ITEM_3. Ensure that Payment Predictor flag is selected on both Payments.
    7.- Launch the Payment Predictor process.
    8.- Confirm that there are two Payment Worksheets created: One for Payment ID PYMNT_1 in Applied status, with Items ITEM_1 and ITEM_2 (200 USD matching), and another one for Payment ID PYMNT_2 in Worksheet status, with Item ITEM_3 listed, and a remaining not applied amount of 100 USD.
    9.- Open the Payment Worksheet for Payment ID PYMNT_2, and next to Item ID ITEM_3, manually add Item ID ITEM_2. Balance the Payment Worksheet, and place it to Post Action Batch Standard.
    10.- Launch AR Update with the Payments option.
    11.- Confirm that Item IDs ITEM_1 and ITEM_3 have been successfully paid, and closed. Confirm as well that Item ID ITEM_2 has been paid twice, for which amount is now -100 USD, and remains open.

To gather more information concerning this scenario and its related problem, refer to the available Replication Steps PDF Document here linked containing the complete configuration and the replication steps necessary to reproduce the issue.

Some Invoices are being paid twice, and posted into the system, which is not correct. The free amount of the Payment received should remain as such, and be placed on another outstanding Invoice, or in a new On Account Item.

The Payment Worksheet component should prevent the User from manually adding Items that have already been picked up on other Worksheets, and issue the below Error Message:

    " Item already tagged in another group (6050,12)
      You have specified on the Receivables Installation Options page, that you do not want to allow an item to be selected in more than one group.  This item has already been selected for processing in another group. "

NOTE: In the images/screenshots/examples mentioned and/or the attached document, user details / company name / address / email / telephone number represent a fictitious sample (based upon made up data used in the Oracle Demo Vision instance).  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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.