Issue Found In Common Group Messages Screen - OBTF
(Doc ID 2949305.1)
Last updated on MAY 17, 2023
Applies to:
Oracle Banking Trade Finance - Version 14.6.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.6.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Issue found in Common Group messages screen - OBTF
It is observed that system is not populating F20 of Common group messages as Contract / user reference of FCUBS. Instead it is having LOV in F21 to pick Contract / user reference of FCUBS in MSDTFCGM screen.
However it is populating F20 in common group messages at contract level correctly.
EXPECTED BEHAVIOR
-----------------------
It should not have incorrect behavior.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are facing issue in Common Group messages screen
Changes
1) Tag 20 is modified to an LOV; Lov will have both contract reference number and User reference number in search fields whereas only contract reference number can be return field.
2)Tag 20 is mapped with contract reference number
3)Tag 21 modified to text field where user can enter the reference number.
call form changes:
The size of narrative fields is increased (tag 79) to Row as 7 and width as 40.
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 |