IV89868: TR 7610 - THE SYSTEM INDICATES THAT THE METER READINGS WERE EXPORTED. BUT IN THE ERROR COUNTS IT SHOWS A NUMBER 1.

APAR status

• Closed as program error.

Error description

• PROBLEM:
  
  Customer found out that there is a difference on the
  functionality regarding the application PLUSTLOGS
  (Registros(Tr)) located inside the ASSET module
  
  comparing the same functionality between MAXIMO 7.1 and MAXIMO
  7.6:
  
  In 7.1, whenever we try to add a new record in the PLUSTLOGS
  application for an asset, by default the system takes the last
  meter reading for the asset and
  
  the user only have to enter the new reading, and the system
  calculates the delta between the two readings.
  
  Now, in MAXIMO 7.6, whenever we try to enter a new record for
  an asset, by default the system takes the cumulative readings
  for the asset and puts that
  
  value in the inicial reading field, not the last reading as in
  7.1, which might be lower that the cumulative reading due to
  the meter can have a rollover point,
  so if the user enters a higher to the cumulative this can be
  higher than the rollover value and a message is displayed
  
  PERFORMANCE ISSUE: NO
  
  STEPS TO REPRODUCE:
  
  1) Go to Asset - Meter application and create 2 meters follow,
  if the meters are created, just change it accordingly:
  
   a) ODOMETRO:
  
  - Metername: ODOMETRO
  - Metertype: CONTINUOS
  - Readingtype: ACTUAL
  - Domainid: null
  - Measureunit : KM - kilometer (it must exist, otherwise
  conversion units and measures will be needed)
  
   b) HISTORICO:
  
  - Metername: HISTORICO
  - Metertype: CONTINUOUS
  - Readingtype: ACTUAL
  - Domainid: null
  - Measureunit : null
  
  2) Create the asset from Asset(Tr) application, only consider
  filling the required fields
  
  3) Add the 2 meters created in step 1. In the meter tab, click
  on new row and add one meter at a time
  
   a) ODOMETRO:
  
  On the Continuous meter Details section, enter the following
  data for Odometro meter:
  - Average Calculation Method: STATIC
  - Average Units/day: 1500
  - Initial Lif to Date: 629623
  - Initial Reading: 0
  - Rollover: 999999
  - Reading Type: Actual
  - Day Limit: 2000
  
   b) HISTORICO
  On the Continuous meter Details section, enter the following
  data for Historico meter:
  - Average Calculation Method: SLIDING-READINGS
  - Sliding Window Size: 12
  - Initial Lif to Date: 2999999
  - Initial Reading: 0
  - Rollover: 999999
  - Reading Type: Actual
  - Day Limit: null
  
  Save the asset record
  
  Change asset status to operating
  
  4) Go to Asset - Logs(Tr) application and create a new Log(Tr)
  record
  
  5) Go to Trip Detail section
  Trip number: 1
  Fuel Quantity: 10
  Meter units: KMS
  
  6) Go to Log Meter Readings and enter meter reading for
  Odometro meter
  Go to Meter reading Logs, click on New Row and enter the
  following data.
  - Trip number: 1
  - Meter: Odometro
  - Meter Start: 2.999.999,00
  - Meter Delta: null
  - Meter Units: KM
  - Reading date: Actual
  - Meter End: 3000100
  
  Save the record
  
  7) Select Action: Export meter readings In the popup window
  select Ignore Warnings
  Select the corresponding meter (ODOMETRO)
  Click on Export button
  
  CURRENT ERRONEOUS RESULT:
  The system indicates that the meter readings were exported. But
  in the Error counts it shows a number 1.
  BMXAA7095E - THE ENTERED VALUE 3.000.100,00 IS NOT VALID. ENTER
  A VALID DECIMAL VALUE
  
  EXPECTED RESULT:
  Export meter readings success
  
  ENVIRONMENT (SYSTEM INFO):
  Linux 2.6.32-431.el6.x86-64
  IBM WebSphere Application Server 8.5.5.3
  Oracle 12.1 (Oracle Database 12c Enterprise Edition Release
  12.1.0.2.0 - 64bit Production With the Partitioning, OLAP,
  Advanced Analytics and Real
  
  Application Testing options)
  
  Tivoli process automation engine 7.6.0.2 Build 20150903-2113
  DBBuild V7602-31
  IBM TPAE Integration Framework 7.6.0.2 Build 20150901-2100
  DBBuild V7602-05
  IBM Maximo for Transportation 7.6.1.0 Build 20150902-2035
  DBBuild V7610-03
  IBM Maximo Asset Management 7.6.0.2 Build 20150903-2113 DBBuild
  V7601-01
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Users that use Maximo Transportation 7.6.1.0             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * THE SYSTEM INDICATES THAT THE METER READINGS WERE            *
  * EXPORTED. BUT IN THE ERROR COUNTS IT SHOWS A NUMBER 1.       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fix incorrect Checking  and define correct locale
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MX TRANSPORTATI

• Fixed component ID

  5724R5500

Applicable component levels