MMDMATCH Screen Does Not Show Contract Details Of New Version After ROLLOVER
(Doc ID 2881786.1)
Last updated on JULY 14, 2022
Applies to:
Oracle Banking Treasury Management - Version 14.5.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Production Support-SET
ACTUAL BEHAVIOR
---------------
MMDMATCH screen does not show contract details of new version after ROLLOVER
After MM Rollover confirmation matching, the MMDMATCH screen does not show the new version of the MM contract after ROLLOVER and only version 1 is shown.
EXPECTED BEHAVIOR
-----------------------
System should show all version details on navigating to the particular version number
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Input a MM Placement contract for 1 day tenor (for testing, put back value date 1 day and maturity today). System generates outgoing MT320. Version of the contract is 1.
2. Incoming MT320 is received and matched with the above contract (FULL MATCH)
3. User does a Rollover of this contract and increase principal by GBP 1000. New MT320 message is generated for the Rollover. Version of the contract is 2.
4. Incoming MT320 message is received and matched with above Rollover (FULL MATCH).
5. However, when user visits the MMDMATCH screen to compare the message and contract details for ROLLOVER, the contract details shows the DETAILS of version 1 (before ROLLOVER), whereas the Message is shown as that of the ROLLOVER.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see the correct contract version details
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 |