My Oracle Support Banner

EAR 9.2: Lockbox Deposit Being Incorrectly Flagged By AR_PAYLOAD AE Program As 'Hold Duplicate' Even If Lockbox ID Value On The Flat File Is Different (Doc ID 2276932.1)

Last updated on APRIL 11, 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:

Per PeopleBooks, if two Lockbox files have the same Deposit Business Unit and Lockbox ID, then it looks at the Bank, Bank Account, Deposit Date and Control Totals to determine if it's a duplicate deposit. However, it has been detected that even if the Lockbox file being uploaded has the same Deposit Business Unit, but the Lockbox ID is different, the system still marks it as a duplicate if the other 4 variables are the same (Bank, Bank Account, Deposit Date and Control Totals).

   - From PeopleBooks:

     Duplicate deposits in lockbox and EDI deposits are placed on hold, with an indicator on the Payment Interface Duplicate - Totals page.
     The system uses different criteria to identify duplicates, depending on the type of deposit:
        - If two lockbox deposits with the same deposit unit and lockbox ID are received, the system uses four criteria to determine whether they are duplicates: bank, bank account, deposit date, and control totals.
     The system groups duplicate payments into deposits and marks them as duplicates.

REPLICATION STEPS:

     1.- Have a Lockbox flat file containing information for a Deposit, and a Payment transaction
     2.- Launch the AR25001 delivered process to load the Lockbox file data into the EC Records
     3.- Launch the AR_PAYLOAD program to generate the Deposit Group, and its Payment information
     4.- Amend the Lockbox file so that the Lockbox ID value is different, as well as the Payment ID, and the Time, keeping all the rest the same
     5.- Launch the AR25001 delivered process to load the Lockbox file data into the EC Records
     6.- Launch the AR_PAYLOAD program to generate the Deposit Group, and its Payment information
     7.- Confirm that the new Deposit transaction is being held as duplicate

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. The 2 Lockbox flat files used on the test are also for download at the bottom section of this KM Document.

ACTUAL RESULT:

The Lockbox Deposit is being flagged as duplicate, and as such, it cannot be used for Payment Predictor, nor Payment Worksheets.

EXPECTED BEHAVIOR:

The Lockbox upload interface, along with AR Payload process, should only flag as duplicate when Deposit BU, Lockbox ID, Bank Code, Bank Account, Deposit Date, and Control Amounts are the same.

 

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.