Unable to Modify the Precision of Fields in the Ship Unit Line Grid or the Precision of any Field in VIEW Mode
(Doc ID 798987.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Transportation Management - Version 5.5 to 5.5 [Release 5.5]
Information in this document applies to any platform.
***Checked for relevance on 29-Dec-2010***
-- Problem Statement:
The precision of the Ship Unit Line's fields are changed to something greater than 3 (this is done by updating the custom Manager Layout). This is done to allow 3 or more decimal places to be viewed/edited when updating the Ship Unit Line. It is found that when editing the Ship Unit Line, directly from the Ship Unit tab of the Order Release, that this precision has not changed (it still defaults to two decimal places). When three or more decimal places are attempted, the following PopUp error is presented:
"Gross Weight per Ship Unit precision must be less than 3"
Furthermore, it is noticed that any field where the Precision is updated, does not change the displayed precision for any field that is displayed in VIEW mode. For example, the Ship Unit's "Gross Weight per Ship Unit" can be updated to 3 decimal places. When the Ship Unit tab of the Order Release is displaying the Ship Unit data, it is noticed that the number of decimal places is still the default of 2.
-- Steps To Reproduce:
1. Navigate to Order Release Finder screen
2. Search for and Edit Order Release
3. Go to Ship Unit tab
Notice that all fields are displayed in a Precision of 2. Even though one or more have been modified to have a precision of 3 or more.
4. Edit the Ship Unit
5. Scroll down and edit the Line
Notice the "Gross Weight" is 3 decimals...that is good.
6. Click "Save" to go back to Ship Unit edit
7. Click "Save" to go back to Ship Unit grid
8. Now click the Ship Unit Line directly from here
Notice that the "Gross Weight" is precision 2 - That is the problem.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|