Amount Column Within AsSupsense Table Contains Values Beyond 2 Decimals
(Doc ID 2935154.1)
Last updated on MARCH 16, 2023
Applies to:
Oracle Insurance Policy Administration J2EE - Version 11.3.1.13 and laterInformation in this document applies to any platform.
Symptoms
DESCRIPTION OF ISSUE
--------------------
When creating new Suspense items, some Suspense Amounts are stored into AsSuspense.Amount with values that go beyond 2 decimals.
As a result, these Suspense Items incorrectly remain in an Open status after the Suspense Item is applied to a Policy.
Example amounts that cause the problem:
1. 289,098.59 gets saved as 289,098.5900000001
2. 417,119.84 gets saved as 417,119.8400000001
3. 557,271.43 gets saved as 557,271.4300000002
4. 329,445.34 gets saved as 329,445.3400000001
STEPS TO REPRODUCE
-------------------
1. Navigate to the Suspense Screen.
2. Create a Suspense item using an amount of 289,098.
3. Query the DB, you will find that the AsSuspense.Amount is saved as 289,098.5900000001 instead of 289,098.59.
4. Workaround is to clean-up this bad data manually.
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 |