My Oracle Support Banner

EAR 9.2: Unable To Set Prenote Status To NEW For A Customer As System Incorrectly Triggers Error Message (9030,217) (Doc ID 2588663.1)

Last updated on SEPTEMBER 16, 2019

Applies to:

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

Symptoms

ISSUE:

It has been detected that the Prenote functionality for the Direct Debit feature in Accounts Receivable is triggering Error Message (9030,217) incorrectly. The scenario is involving two customers, using the exact same Customer ID, but under a different Set ID value, and both configured for Direct Debit functionality.

If the first Customer has sent its Prenote EFT file via Financial Gateway, and the system is still acknowledging the confirmation (or no acknowledgement is needed), but the User runs again the Direct Debit Creation process (AR_DIRDEBIT AE Program) after the minimum number of days has passed, the system will update the first Customer's Prenote Status to 'Confirmed' (Record Field PS_CUST_OPTION.PRENOTE_STATUS = C), however, it will not update the Payment Status in Financial Gateway, as it will remain in a value of 'Dispatched to Bank' (PS_PMT_DETAIL_TBL.PMT_STATUS = S).

This causes a problem when the User tries to configure the Prenote feature for the second Customer, which is under a different Set ID value. It seems that when manually setting the Prenote Status to NEW on this second Customer, the system throws an Error Message stating that there is already an EFT Prenote transaction awaiting to be processed in Financial Gateway. However, this would be for the wrong customer.

REPLICATION STEPS:

    1.- Create a new Customer ID AAAA under Set ID SHARE, and enable it for Direct Debit payments
    2.- Activate the Prenote to be required, and set the following values:
              - Prenote Status = New
              - Days = 1
    3.- Save the changes
    4.- Create a new Pending Item Group for this Customer, and set it to Post Action Batch Standard
    5.- Launch AR Update to post the new Item to the Customer's Account, with Payment Method of Direct Debit
    6.- Run Direct Debit Creation process for this Customer ID AAAA
    7.- Confirm the Direct Debit Worksheet is created, and remit it
    8.- Create the EFT file to push the data into Financial Gateway (AR_FG_PROC AE Program)
    9.- Dispatch the Payment transaction in Financial Gateway
    10.- The next day, run the Direct Debit Creation process again
    11.- Verify Customer ID AAAA Prenote Status is now Confirmed at the Bill To Options page
    12.- Create a new Customer ID AAAA under Set ID US002, and enable it for Direct Debit payments
    13.- At the Bill To Options page, try to set the Prenote Status to NEW, but the system throws an Error Message

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

ERROR MESSAGE:

    " A Direct Debit prenote exists for this customer (Business Unit: XXXXX, DD_ID: 12345). (9030,217)
      You must first cancel the existing prenote before resetting Prenote Status to New. "

ACTUAL RESULT:

Users are unable to set the Prenote Status to New on a Customer that has not yet been processed by Direct Debits Creation (AR_DIRDEBIT AE Program). This prevents Users from sending the Prenote to the Bank for confirmation.

EXPECTED BEHAVIOR:

The system should not throw such Error Message, as it should be smart enough to check not only the Customer ID, but under what Set ID value is it defined, and allow the User to manually set the Prenote Status to New if needed.

NOTE: In 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.