IJ07338: Changing the status of an eSIG enabled PM and if the PM has a forecast, the eSIG gets caught in a loop.

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  Changing the status of an eSIG enabled PM and if the PM has a
  forecast, the eSIG gets caught in a loop.
  
  STEPS TO REPRODUCE:
  Enable the eSig Action for the PM application:
  
  1. Go to the Database Configuration application.
  
  2. Find the PM object.
  
  3. In the More Actions section select Manage eSig
  Actions.
  
  4. In the dialog box, in the Applications section
  filter on PREVENTATIVE  to bring up the Preventative
  Maintenance application and click on it.
  
  5. In the Options for Clear Changes section, find and
  tick the check boxes for the  Change Status and
  Save PM options.
  
  6. Save.
  ESig will now be enabled.
  
  7. Go to the PM application.
  
  8. Create a PM and change its status - you will be asked for
  your signature and comment then the PM will be updated.
  
  9. Now generate a forecast for the same PM (More Actions,
  Generate Forecast).
  
  10. Now try to change the status as you did in step 8 above.
  
  ERRONEOUS RESULT:
  You are asked repeatedly, in a loop, for your signature.  The
  only way out of the loop is to cancel.
  
  EXPECTED RESULTS:
  There should not be any looping.
  
  PRODUCT VERSION:
  7.6.0.8
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users who enabled Esig on the PM app                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Esig and OK/Cancel dialog boxes were stuck in a loop when    *
  * changing status from active to inactive/draft on a PM with   *
  * forecast records.                                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• This is fixed in the code.
  
  The fix for this APAR is contained in the following maintenance
  package:
  	 | release\fix pack | Interim Fix for Release 7.6.1.1 Product
  

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

  PREVENTIVE MAIN

• Fixed component ID

  5724R46PM

Applicable component levels

• R760 PSY

     UP