My Oracle Support Banner

Numeric Value Transformed to Exponential Form and Cause Invalid Number Error (Doc ID 2404206.1)

Last updated on MARCH 06, 2019

Applies to:

Oracle Financial Services Revenue Management and Billing - Version and later
Information in this document applies to any platform.


On RMB v2. against FW v4.3.0.1, numeric value with 7+ decimal numbers transformed to exponential form and when scientific notation is displayed on the UI, Invalid Number error is thrown.

Actual behavior:
An object with a numeric field is saved with a very small value (ex. 0.0000001), this value is transformed into exponential form in the approval transaction data schema when an approval transaction is created. This is causing a crash for invalid value in the application.

Expected behavior:
Decimal format should not get converted to scientific notation in the first place.

Steps to Reproduce:
1. Plugin an audit algorithm on the audit spot of the Business Objects, such that the BO schema has Number type field with high precision(18,18)
2. In this Audit Algorithm we take data from boNewRequest/boRequest and put it in the CLOB and store it in a separate table.
3. Add entity containing number type field, provide the input in decimal format (ex. 0.0000000043).
4. When the audit algorithm gets invoked, this data is saved in the CLOB, in scientific format instead of decimal format
5. When this CLOB data is used to render input and display UI maps, we get scientific notation in UI

Business Impact:
Due to this issue, users cannot use such value and it impacts actual calculation.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.