IJ30145: NULLPOINTEREXCEPTION ERROR WHILE APPLYING DOWNTIME TO ASSET ON WORK ORDER APPLICATION

APAR status

• Closed as program error.

Error description

• Problem Description
  Users are reporting downtime in work order
  application and they are facing "BMXAA4214E - An unknown error
  has occurred." message when enter invalid format by mistake in
  Report Downtime dialog.
  
  STEPS TO REPRODUCE:
  .GO TO >> ASSETS
  >> ASSET
  .Create a new Asset (ie ASSET12)
  .Enter a
  description
  .Save
  .Change status to OPERATING
  .Create a new
  Asset (ie ASSET1)
  .Enter a description
  .Click on Spare Parts
  tab
  .In Subassemblies section, add the asset created in the
  second step (ie ASSET12)
  .Save
  .Change status to OPERATING
  .GO
  TO >> WORK ORDERS >> WORK ORDER TRACKING
  .Create a new work
  order
  .Enter a description
  .In Asset field, enter the parent
  asset (ie ASSET1)
  .In Multiple Assets,Locations and CIs
  section, enter the child asset (ie ASSET 12)
  .Both assets must
  to be in ACTIVE/OPERATING status and the flag ASSET UP must to
  be selected
  .Save
  .Approve the work order
  .MORE ACTIONS >>
  REPORT DOWNTIME
  .Status Date: one week ago
  .Downtime Code:
  BRKDWN
  .Click OK
  .In Multiple Assets,Locations and CIs section,
  click on detail menu in Asset field >> Report Downtime
  .Enter a
  invalid format data like 1/50/21 8:06 AM
  .Tab out or click on
  Downtime code field
  
  RESULTS: BMXAA4214E - An unknown error has
  occurred. Please contact your system administrator for
  assistance. Gather the logs from the <HOME> directory and
  determine where and why the error occurred.
  EXPECTED RESULTS:
  Expects an error message related to invalid format.
  
  REPORTED
  IN VERSION:
  Tivoli's process automation engine 7.6.0.10
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In Work Order Tracking on the Multiple Assets, Locations,    *
  * and CIs table window, if you use the asset's menu to bring   *
  * up Report Downtime and then change the status date, a null   *
  * pointer occurs on validation.                                *
  ****************************************************************
  Problem Description
   Users are reporting downtime in work order
   application and they are facing "BMXAA4214E - An unknown error
   has occurred." message when enter invalid format by mistake in
   Report Downtime dialog.
   STEPS TO REPRODUCE:
   .GO TO >> ASSETS >> ASSET
   .Create a new Asset (ie ASSET12)
   .Enter a description
   .Save
   .Change status to OPERATING
   .Create a new
   Asset (ie ASSET1)
   .Enter a description
   .Click on Spare Parts tab
   .In Subassemblies section, add the asset created in the second
  step (ie ASSET12)
   .Save
   .Change status to OPERATING
   .GO
   TO >> WORK ORDERS >> WORK ORDER TRACKING
   .Create a new work order
   .Enter a description
   .In Asset field, enter the parent asset (ie ASSET1)
   .In Multiple Assets,Locations and CIs section, enter the child
  asset (ie ASSET 12)
   .Both assets must to be in ACTIVE/OPERATING status and the flag
  ASSET UP must to be selected
   .Save
   .Approve the work order
   .MORE ACTIONS >> REPORT DOWNTIME
   .Status Date: one week ago
   .Downtime Code: BRKDWN
   .Click OK
   .In Multiple Assets,Locations and CIs section, click on detail
  menu in Asset field >> Report Downtime
   .Set the Status date to a couple of days ago by clicking on
  calendar button
   .Click OK
  
   RESULTS: BMXAA4214E - An unknown error has occurred. Please
  contact your system administrator for assistance. Gather the
  logs from the <HOME> directory and determine where and why the
  error occurred.
   EXPECTED RESULTS: Expects to report downtime with no error.
   REPORTED IN VERSION:
   Tivoli's process automation engine 7.6.0.10
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package:
  Release 7.6.1.3 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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels