IJ37934: PM GENERATES WORK ORDER WITH NO DATA IN THE REQUIRED FIELD (ESTIMATED NEXT DUE DATE)

APAR status

• Closed as program error.

Error description

• PROBLEM:
  Error message is not being thrown for the required field
  (Estimated Next Due Date) when the PM is being generated from
  the Asset Template application.
  
  STEPS TO REPRODUCE:
  Before performing the following steps you will need to ensure
  that the Estimated Next Due Date field is changed to required
  for the PM application in the Application Designer.
  
  1. Open the Assets Template Application
  2. Create a new record
  3. Move to the PMs tabs and select the New Row button
  4. Select a Master PM record (1003)
  5. Save the record and change the status to Active
  6. Select the Generate New Assets action
  7. Select a site (BEDFORD)
  8. Populate the Location field (SAN203)
  9. Leave the PM State Date as blank (remove date value if one is
  populated)
  10. Populate the Quantity field with a value of 1
  11. Select the Generate Assets button
  12. Select the OK button
  13. Move to the PM application and filter for the asset that was
  generated
  14. Select the PM record
  15. Move to the frequency tab and see that the Estimated Next
  Due Date field is not populated
  16. Change the status of the PM to active
  
  RESULTS:
  The PM record gets changed successfully with no error
  
  EXPECTED RESULTS:
  Error message should appear that a required field is required
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * PM STATUS CAN BE CHANGED WITH NO DATA IN UI-REQUIRED FIELD   *
  * (ESTIMATED NEXT DUE DATE) LEADING TO ERRONEOUS WORK ORDER    *
  * GENERATION.                                                  *
  ****************************************************************
  PROBLEM:
  Error message is not being thrown for the required field
  (Estimated Next Due Date) when the PM is being generated from
  the Asset Template application.
  STEPS TO REPRODUCE:
  Before performing the following steps you will need to ensure
  that the Estimated Next Due Date field is changed to required
  for the PM application in the Application Designer.
  1. Open the Assets Template Application
  2. Create a new record
  3. Move to the PMs tabs and select the New Row button
  4. Select a Master PM record (1003)
  5. Save the record and change the status to Active
  6. Select the Generate New Assets action
  7. Select a site (BEDFORD)
  8. Populate the Location field (SAN203)
  9. Leave the PM State Date as blank (remove date value if one
  is
  populated)
  10. Populate the Quantity field with a value of 1
  11. Select the Generate Assets button
  12. Select the OK button
  13. Move to the PM application and filter for the asset that
  was
  generated
  14. Select the PM record
  15. Move to the frequency tab and see that the Estimated Next
  Due Date field is not populated
  16. Change the status of the PM to active
  RESULTS:
  The PM record gets changed successfully with no error
  EXPECTED RESULTS:
  Error message should appear that a required field is required
  {*}Note about this fix{*}: While some customers do generate work
  orders from PMs with null Estimated Next Due Date values, others
  may not want to allow this. One option is to make Estimated Next
  Due Date required in the UI. However, if PMs are created from
  the Asset Templates application, PMs can be created and saved
  with a null Estimated Next Due Date value as the Asset Templates
  application has no awareness of fields required in the PM
  application UI. In the PM application, the status of these PMs
  can be changed to ACTIVE because fields required in the
  application UI are not enforced from the Change Status dialog.
  Fields required in the application UI are only enforced when
  making modifications with the application tabs, for example, PM,
  Frequency, Seasonal Dates, Job Plan Sequence, etc. This is
  working as designed.
  For customers who do not want to allow work order generation
  from PMs with null Estimated Next Due Date values, this poses a
  problem. This APAR fix addresses this problem outside of the UI
  required field framework via the addition of a system property
  mxe.app.pm.requireNextDateForActiveStatus. By default, this
  property is 0 (false) meaning that users can change a PM's
  status to ACTIVE and generate work orders from PMs with null
  Estimated Next Due Date values as has always been the case. If
  this property is set to 1 (true), the status of PMs with null
  Estimated Next Due Date values cannot be changed to ACTIVE. This
  will prevent the generation of work orders from a PM that does
  not have an Estimated Next Due Date.
  

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