My Oracle Support Banner

OTM/GTM ATTRIBUTE_NUMBER Fields Are Storing Number Values With Larger Precision In Database (Doc ID 2949923.1)

Last updated on MAY 18, 2023

Applies to:

Oracle Transportation Management Cloud Service - Version 19.3 and later
Information in this document applies to any platform.


In OTM / GTM user interface (Manager Layout/Screensets) when user is entering a number value on a field which is being saved in one of the available ATTRIBUTE_NUMBER fields on the corresponding Backend Table, then there is an observation that, in Database, that data is actually saved with larger precision than entered. 

For an Example:

One of the Order Release fields is mapped with backend column ATTRIBUTE_NUMBER1 on this table ORDER_RELEASE.

User enters a value as "81.08" through that custom manager layout for an Order Release.

However, if user executes a select SQL on Servlet to check the value on the backend table/column level- it shows the value as "81.0799999999999982946974341757595539093" in the backend table/column.

Expected Behavior
In the backend table/column the data must be saved exactly same as customer is entering in UI.

Error Message (If Any)
No error

Steps to Reproduce
The issue can be reproduced at will as per the mentioned example above.

Business Impact
Due to this issue observation-
1. Incorrect number value is getting saved on backend/database
2. Mathematical operations for such fields sometimes results in incorrect/wrong outcome
3. It display wrong data on Reports and user needs to use available workarounds to display correct data 




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.