IV97882: COUNTER FOR PM RECORD IS NOT RESET WHEN WORK ORDER CREATED FROM METER READING IS CREATED

APAR status

• Closed as program error.

Error description

• STEPS TO REPRODUCE:
  
  1. Create a new pm record.
  
  2. Hyper link over to the assets application, create a new
  asset, add any location you like and save.
  
  3. Move to the meters tab, add a meter group using the
  available meter group, save and we should now see meters
  present. Return to the PM application.
  
  4. Move to the frequency tab, then select the meter based
  frequency tab, press new row and add a the runhours meter. Set
  the frequency to 700, set the generate WO ahead by to 240.
  Place a check mark in the generate work order based on meter
  reading and in the generate work order when meter frequency is
  reached box. Save.
  
  5. Move back to the asset created earlier and enter a meter
  reading for the runhours meter, use a value of 800. The 800
  value will cause a work order to be generated.
  
  6. Move back to the PM application, bring up the PM and notice
  that the counter has increased to by 1. To find the generated
  work order, press the chevron next to the asset field and
  select view work details, the work order will show. Hyper link
  over to the work order application and cancel the created work
  order. You will be asked if you wan to reinstate the PM, answer
  yes to this. Once that is done, return to the
  PM application. Recall the PM, notice that the counter did not
  get reset to 0.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users generating work orders from Meter based PM             *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PM counter is not reset when Work Order created from meter   *
  * based PM is cancelled.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

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

  ASSETS

• Fixed component ID

  5724R46AS

Applicable component levels

• R760 PSY

     UP