User reference Number is updated incorrectly while booking Securities Repo SR deal from External System
(Doc ID 2710480.1)
Last updated on JUNE 21, 2021
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.3 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Securities Repo Deal is booked from External System by sending a User reference number which is being replaced with Contract reference number after Save
EXPECTED BEHAVIOR
-----------------------
It is expected that the Repo deals should be booked with User reference number same as the value sent by User while booking
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Upload a new Repo deal from External source using CreateSRDeal Request
2. Ensure to pass User reference number
3. Verify if the contract is saved successfully
4. From SRDTRONL screen, query the contract using User reference number
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Users are not able to requery the booked repo deals using User reference number for reconciliation
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 |
Cause |
Solution |
References |