RTGS Transaction Initiated by NRE Users Fails Due to Incorrect SENDTORECEIVER1 Request Tag Value
(Doc ID 2590317.1)
Last updated on MAY 12, 2022
Applies to:
Oracle Banking Digital Experience - Version 18.1.0.0.0 to 18.1.0.0.0 [Release 18]Information in this document applies to any platform.
Symptoms
On : 18.1.0.0.0 version, Production Support
ACTUAL BEHAVIOR
---------------------------
SENDTORECEIVER1 Request tag contains /FAST/FAST when an NRE User Initiates an RTGS Transaction, due to which the Transaction fails at Core banking
EXPECTED BEHAVIOR
-----------------------
SENDTORECEIVER1 Request should contain /NRE/NRE when an NRE Customer Initiates an RTGS Transaction.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login into OBDX Application and Initiate an RTGS Transaction (the customer should be an NRE Customer)
2. Complete the Transaction and check the Request xml being sent to Core Banking
3. SENDTORECEIVER1 Request tag contains /FAST/FAST
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, NRE users cannot initiate an RTGS Transaction.
Changes
The only change that triggers this Issue is that the Particular User in Question is an NRE User
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 |