Maximo Rounding problems

Problem

Do you have a rounding problem?

If you use Maximo and are having rounding issues on the NUMVALUE attributes, the following solution could resolve the problem. The NUMVALUE attribute can be found on all the specification tables, such as ACTCISPEC, ASSETSPEC, ITEMSPEC, CLASSSPEC, CISPEC, etc. The NUMVALUE attributes are currently defined as the data type decimal(30,10). Decimals are handled as doubles, which are known not to be precise.

The rounding error is specifically noticeable on inserts. For example:

The value of NUMVALUE on an Actual CI specification is stored in the database as 999,999,999.0. When this Actual CI is promoted to a CI, the NUMVALUE in the CI Specification may be stored as 999,999,999.0000000200.

If your solution does not require the decimal precision of 10, the rounding error can be resolved by reducing the scale for the NUMVALUE attribute to 5 or less.

To reduce the scale of all NUMVALUE attributes in Maximo, complete the following steps:

1. Because the object NUMERICDOMAIN is an internal object, run the following queries on the Maximo database before you change the scale in the Database Configuration application:

   update maximo.maxobject set internal=0 where objectname='NUMERICDOMAIN';
   update maximo.maxobjectcfg set internal=0 where objectname='NUMERICDOMAIN';

2. In Maximo go to System Configuration > Platform Configuration > Database Configuration.
3. On the List tab in the Database Configuration application, select the NUMERICDOMAIN object.
4. On the Attributes tab, expand the row for the VALUE attribute.
5. In the Scale field for the VALUE attribute, specify a value of 5 or less.
6. Save the object.
7. From the Select Action menu, choose Manage Admin Mode.
8. Click Turn Admin Mode ON.
9. When Admin Mode is turned on, from the Select Action menu, choose Apply Configuration Changes.
10. To turn off Admin Mode, from the Select Action menu, select the Admin Mode option, and then click Turn Admin Mode OFF.
11. After the changes are applied, to set the object NUMERICDOMAIN back to an internal object, run the following queries on the Maximo database:

    update maximo.maxobject set internal=1 where objectname='NUMERICDOMAIN';
    update maximo.maxobjectcfg set internal=1 where objectname='NUMERICDOMAIN';