IJ41050: CONDITION MONITORING PMNUM FIELDS Go To PM DOESN'T FIND PM IF PRIORITY ON CM DIFFERS FROM PM PRIORITY

APAR status

• Closed as program error.

Error description

• In the conditioning monitoring application, When ?Upper Limit
  PM:? is selected, it sets ?Upper Limit Priority:? automatically
  as per priority value of Preventive Maintenance. When the
  priority of PM is changed, jump from the conditioning monitoring
  to the attached PM is not possible as it checks pmnum attribute
  and priority as search condition.
  
  STEPS to REPRODUCE:
  1.Go to Conditioning Monitoring Application
  
  2.Create a new record
    Enter Asset Value (e.g. CAL101) and ULPMNUM (e.g. 1008) and
  LLPMNUM (e.g. 1008).
  
    Select any PM which has a priority value other than 0
  
    Enter Meter Value (e.g. TEMP-C)
    Enter values for ?Upper Warning Limit:?, ?Lower Warning
  Limit:?, ?Upper Action Limit:? and ?Lower Action Limit:?.
  
  3.Save the record
  4.Go to the selected PM (e.g. 1008)
  
  5.Change the priority to any value than original value (e.g. 4)
  
  6.Go to the attached PM from the newly created Conditioning
  Monitoring record
  
  RESULT:
  
  It will show the list tab of PM, instead of PM
  
  EXPECTED RESULT:
  
  Jumping from Conditioning Monitoring record to the attached PM
  should be possible irrespective of priority
  
  REPORTED IN VERSION: Tivoli?s process automation engine 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IN CONDITION MONITORING FROM PMNUM FIELDS, Go To PREVENTIVE  *
  * MAINTENANCE DOESN'T FIND PM IF PRIORITY ON MEASUREPOINT      *
  * DIFFERS FROM PM PRIORITY. SAME ISSUE EXISTS WITH THE JPNUM   *
  * FIELDS AND JOB PLANS.                                        *
  ****************************************************************
  In the Conditioning Monitoring application, when Upper Limit
  PM is selected, it sets Upper Limit Priority automatically
  as per priority value of Preventive Maintenance. When the
  priority of PM is changed, jump from the conditioning
  monitoring
  to the attached PM is not possible as it checks pmnum attribute
  and priority as search condition.
  STEPS to REPRODUCE:
  1.Go to Conditioning Monitoring Application
  2.Create a new record
  Enter Asset Value (e.g. CAL101) and ULPMNUM (e.g. 1008) and
  LLPMNUM (e.g. 1008).
  Select any PM which has a priority value other than 0
  Enter Meter Value (e.g. TEMP-C)
  Enter values for Upper Warning Limit, Lower Warning
  Limit, Upper Action Limit, and Lower Action Limit.
  3.Save the record
  4.Go to the selected PM (e.g. 1008)
  5.Change the priority to any value than original value (e.g. 4)
  6.Go to the attached PM from the newly created Conditioning
  Monitoring record
  RESULT:
  It will show the List tab of PM, instead of PM
  EXPECTED RESULT:
  Jumping from Conditioning Monitoring record to the associated
  PM
  should be possible even if the priorities differ.
  The same issue exists with the JPNUM fields in Condition
  Monitoring when trying to Go To Job Plans if the priority values
  differ.
  

Problem conclusion

• The fix for this APAR will be contained in a future release.
  

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

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels