CYDCCYLS MXN Values Missing & Error - Greater Precision Than What Is Allowed For The Currency JPY
(Doc ID 2875913.1)
Last updated on JUNE 14, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - 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
CYDCCYLS MXN values missing & Error - greater precision than what is allowed for the currency JPY
1. v14 has a completely blank value for MXN for a few of the boxes in CYDCCYLS whereas v12 has values in all including 0.00.
2. Further inspection of the JPY values in the report show they have decimals. The amounts should be displayed without decimals as they have a minimum precision in whole numbers.
Note: JPY should display with out decimals, MXN should display with decimals , because of MXN filed data Null error popup getting displayed as JPY had more precision
ERROR
-----------------------
greater precision than what is allowed for the currency JPY
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Navigate to CYDCCYLS screen and query for a particular branch
2. Verify if data is displayed correctly as per defined decimal values
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot view the correct values for JPY and MXN ccy
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 |