Transactions Wrongly Getting Posted with Wrong Value Date / Customer Name from Mock JSON Response Files
(Doc ID 2575182.1)
Last updated on AUGUST 12, 2019
Applies to:Oracle Banking Digital Experience - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 18]
Information in this document applies to any platform.
On : 126.96.36.199.0 version
Multiple Transactions are getting posted to Core Banking with Wrong Value Date / Customer Name getting Picked up from MOCK json response files, in Production
The Transactions are getting Rejected at Core Banking.
Observation is that the Value Date picked up is mostly 30-Jan-2015
The issue cannot be reproduced under Normal Circumstances. However Transactions Initiated with Current date / Next Value Date is Posted to Core Banking with Value Date as 30-Jan-2015
The issue has the following business impact:
Due to this issue, All the Current Dated Transactions are Posted with a BackDated Value Causing Multiple Rejections at Core Banking
No changes to Hardware/Account causes this Issue.
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