IJ16728: UPPER OR LOWER LIMIT PRIORITY SHOULD BE SET FROM THE UPPER/LIMIT JOB PLAN OR PM

APAR status

• Closed as program error.

Error description

• Problem Summary:
  
  In the Condition Monitoring Application, When entering an upper
  or lower limit job plan or PM, the priority should be set from
  the job plan or PM. If the job plan or PM has a null priority,
  the upper or lower limit priority should also be null. The same
  applies to Characteristic Action Values on Measure Points that
  have characteristic meters.
  
  
  
  Steps to Reproduce:
  
  1. Create a new Numeric domain (i.e. WOPRIORITY) and add the
  values 1, 2, 3, 4 (without orgid and siteid)
  
  2. On the Database Configuration, open the MEASUREPOINT object
  > Attribute tab
  
  3. Filter ULPRIORITY and LLPRIORITY attributes.
  
  4. Set the filtered attributes' domain to WOPRIORITY.
  
  5. Apply Configdb.
  
  6. Go to Job Plan application and create a new record with
  ORGID, SITEID, and set the Priority to null.
  
  7. Save the Job Plan record and change the status to ACTIVE.
  
  8. Go to Condition Monitoring application and create a new
  record with the same SITEID as the Job Plan record created
  earlier.
  
  9. On the Upper Limit Job Plan (and/or Lower Limit Job Plan),
  select the Job Plan we created earlier.
  
  10. At first no error occurs - but if you delete the job plan
  from the field and reapply the same job plan the error
  "BMXAA4190E - Upper Limit Priority 0 is not in the value list."
   occurs.
  
  
  
  Current Results:
  
  If WO Priority field is Null and the Job plan is attached to
  the Upper Limit Priority/Lower Limit Priority Job plan field,
  the Priority field is 0, instead of Null. Also, if a Job plan
  is revised, and the WO Priority is updated, the new WO Priority
  will not be applied to the Upper/Lower Limit Priority.
  
  
  
  Expected results:
  
  When entering an upper or lower limit job plan or PM, the
  priority should be set from the job plan or PM. If the job plan
  or PM has a null priority, the upper or lower limit priority
  should also be null. The same applies to Characteristic Action
  Values on Measure Points that have characteristic meters. Also,
  Revised WO Priority should be updated when the job plan is
  reattached to the Upper/Lower Limit Job Plan or PM.
  
  
  
  Reported in Version:
  Tivoli's process automation engine 7.6.1.0
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users of Condition Monitoring                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * In the Condition Monitoring Application, job plan and PM     *
  * priority is not always set from the job plan or PM provided  *
  * as the upper or lower limit job plan or PM. Additionally,    *
  * the job plan and PM priority is not always made null if the  *
  * job plan or PM provided as the upper or lower limit job plan *
  * or PM has a null priority.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In the Condition Monitoring Application, When entering an upper
  or lower limit job plan or PM, the priority should be set from
  the job plan or PM. If the job plan or PM has a null priority,
  the upper or lower limit priority should also be null. The same
  applies to Characteristic Action Values on Measure Points that
  have characteristic meters.
  
  Steps to Reproduce:
  1. Create a new Numeric domain (i.e. WOPRIORITY) and add the
  values 1, 2, 3, 4 (without orgid and siteid)
  2. On the Database Configuration, open the MEASUREPOINT object
  and filter for the ULPRIORITY and LLPRIORITY attributes on the
  Attributes tab.
  3. Set the filtered attributes' domain to WOPRIORITY.
  4. Apply configuration changes.
  5. Go to Job Plan application and create a new record with
  ORGID, SITEID, and set the Priority to null.
  6. Save the Job Plan record and change the status to ACTIVE.
  7. Go to Condition Monitoring application and create a new
  record with the same SITEID as the Job Plan record created
  earlier.
  8. On the Upper Limit Job Plan (and/or Lower Limit Job Plan),
  select the Job Plan we created earlier.
  9. At first no error occurs - but if you delete the job plan
  from the field and reapply the same job plan the error
  "BMXAA4190E - Upper Limit Priority 0 is not in the value list."
  occurs.
  
  Current Results:
  If WO Priority field is Null and the Job plan is attached to the
  Upper Limit Priority/Lower Limit Priority Job plan field, the
  Priority field is 0, instead of Null. Also, if a Job plan is
  revised, and the WO Priority is updated, the new WO Priority
  will not be applied to the Upper/Lower Limit Priority.
  
  Expected results:
  When entering an upper or lower limit job plan or PM, the
  priority should be set from the job plan or PM. If the job plan
  or PM has a null priority, the upper or lower limit priority
  should also be null. The same applies to Characteristic Action
  Values on Measure Points that have characteristic meters. Also,
  revised WO Priority should be updated when the job plan is
  reattached to the Upper/Lower Limit Job Plan or PM.
  
  Reported Version:
  Tivoli's process automation engine 7.6.1.0
  

Problem conclusion

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

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels