IV62061: BMXAA4214E ERROR ENTERING METER READING WOTRACK

APAR status

• Closed as program error.

Error description

• Problem Title:  7506 BMXAA4214E error when Entering Meter
  Reading in WOTRACK
  
  
  Product Version #:
  
  Tivoli's process automation engine 7.5.0.6 Build 20140404-0005
  DB Build V7506-33,
  
  
  IBM Maximo Asset Management 7.5.0.6 Build 201404181006 DB Build
  V7506-00,
  IBM Maximo Asset Management Scheduler 7.5.2.0 Build
  20140404-0005 DB Build V7520-158,
  
  IBM TPAE Integration Framework 7.5.1.1 Build 20140411-2000 DB
  Build  V7511-01
  
  
  
  IBM Websphere Application Server 7.0.0.15
  
  Microsoft SQL Server 11.0 (11.00.2100)
  
  Operating System: Linux 2.6.32-358.el6x86_64
  
  
  
  
  Problem Details:
  
  When entering meter reading in WOTRACK application results in
  NullPointerException
  
  
  When attempting to add a meter reading to an asset based meter
  on a
  workorder the user is receiving a null pointer exception.
  
  "BMXAA4214E - An unknown error has occurred"
  
  
  This issue was present always and happens All the time.
  
  
  The systemout.log has the following exception details:
  
  Key part of exception.
  
  [6/13/14 7:21:20:942 PDT] 00000027 SystemOut     O 13 Jun 2014
  07:21:20:
  942 [ERROR] [MXServer] [] java.lang.NullPointerException
  java.lang.NullPointerException
   at
  psdi.app.meter.DeployedMeter.maintainWOMeter(DeployedMeter.java:
  2075)
   at psdi.app.meter.DeployedMeter.save(DeployedMeter.java:2497)
   at psdi.app.asset.AssetMeter.save(AssetMeter.java:988)
   at psdi.mbo.MboSet.saveMbos(MboSet.java:7465)
   at psdi.mbo.MboSet.validateTransaction(MboSet.java:7446)
   at
  psdi.txn.MXTransactionImpl.validateTransaction(MXTransactionImpl
  .
  java:375)
   at
  psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.jav
  a:
  207)
   at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
   at psdi.mbo.MboSet.save(MboSet.java:7119)
   at psdi.mbo.MboSet.save(MboSet.java:7059)
   at
  psdi.webclient.system.beans.DataBean.save(DataBean.java:3008)
   at
  psdi.webclient.system.beans.DataBean.execute(DataBean.java:6481)
   at
  psdi.webclient.beans.common.AutoWogenBean.execute(AutoWogenBean.
  java:109)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at sun.reflect.NativeMethodAccessorImpl.invoke
  (NativeMethodAccessorImpl.java:60)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke
  (DelegatingMethodAccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
  
  
  Steps to replicate: Reproduced by L1 & L2:
  
  1. Create Meters for Differential pressure of type Gauge
  )
  
  
  Meter 1: FDIFFPRESS - Feed Differential Pressure
  
  
  
   2. Put meters onto Assets
  
  i.e.
  
  Asset 11300 - Reciprocating Compressor- Air Cooled/100 CFM
  
  
  
  3. Create a new Route (EMEAWW)
  
  - Add Assets (11300 plus add another 2-3 Assets that are in
  Active
  state) to a Route -
  
  Enable tick Option for Route stops to become: "Entries in the
  Work
  Order's Multi Asset, Location and CI Table"
  
  
   4. Put Route (EMEAWW) and Building Location onto a newly
  created PM
  record
  (Same issue if only ROUTE is added with no Location on the PM
  record)
  
  
   5. Remove Frequency tick and Generate workorders from PM
  record.
  
  Make note of new WONUM created
  
   6. On Workorder Tracking app, locate the new WO & change
  workorder status to INPRG.
  
  
   7. Using menu option from an Asset in the "Multiple
  Assets,Locations section, select option to "Enter Meter Reading"
  
   8. In dialogue box that appears enter meter reading and
  date/Time for reading and click OK
  
  
  
  New Reading: 20
  New Reading Date: 30/06/14 1:30
  
  
  Have confirmed that this is an issue in an OOB system.  We have
  also tested that this works as expected in a 7.5.0.4 version
  system.
  
  
  Expected behaviour:
  Dialogue box disappears and meter reading is entered into
  system.  If same process followed last meter reading will be
  seen in dialogue box.
  
  Actual behaviour: When entering meter reading in
  WOTRACK application error message appears as follows "BMXAA4214E
  - An unknown error has occurred..."
  

Local fix

• Workaround: Meter reading could be entered on the Asset
  screen; however, this is limited to a few people in the
  organisation and increases the complexity and time taken to
  enter meter reading rendering the benefits of the use of the
  system moot.
  
  Dev to provide Fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Null pointer exception when entering meter readings. Problem *
  * exists in Release 7.5.0.6, Release 7.1.1.13 and Release      *
  * 7.1.1.12 IFIXes from 20140214-1646 through 20140625-1402.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply latest fix pack.                                       *
  ****************************************************************
  In Work Order Tracking, if user attempts to enter a meter
  reading from the detail menu on the Asset field in the Multiple
  Assets, Locations and CIs table window, the following null
  pointer exception occurs:
  
  [6/13/14 7:21:20:942 PDT] 00000027 SystemOut O 13 Jun 2014
  07:21:20:942 [ERROR] [MXServer] []
  java.lang.NullPointerException
  java.lang.NullPointerException
   at
  psdi.app.meter.DeployedMeter.maintainWOMeter(DeployedMeter.java:
  2075)
   at psdi.app.meter.DeployedMeter.save(DeployedMeter.java:2497)
   at psdi.app.asset.AssetMeter.save(AssetMeter.java:988)
   at psdi.mbo.MboSet.saveMbos(MboSet.java:7465)
   at psdi.mbo.MboSet.validateTransaction(MboSet.java:7446)
   at
  psdi.txn.MXTransactionImpl.validateTransaction(MXTransactionImpl
  .java:375)
   at
  psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl.jav
  a:207)
   at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
   at psdi.mbo.MboSet.save(MboSet.java:7119)
   at psdi.mbo.MboSet.save(MboSet.java:7059)
   at
  psdi.webclient.system.beans.DataBean.save(DataBean.java:3008)
   at
  psdi.webclient.system.beans.DataBean.execute(DataBean.java:6481)
   at
  psdi.webclient.beans.common.AutoWogenBean.execute(AutoWogenBean.
  java:109)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at
  sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor
  Impl.java:60)
   at
  sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
  AccessorImpl.java:37)
   at java.lang.reflect.Method.invoke(Method.java:611)
  

Problem conclusion

• Code fix addresses problem introduced by fix for APAR IV52631 in
  Release 7.5.0.6.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	| release\fix pack\interim fix for Release 7.5.0.7 of Base
  Services
  

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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  WORK & MTRL APP

• Fixed component ID

  TIVOWRKMM

Applicable component levels

• R750 PSY

     UP