IJ47936: CHANGES TO PM RECORD MADE WITH 'APPLICATION IMPORT' OF A CSV FILE ARE IGNORED WHEN THE PM HAS A FORECAST GENERATED

APAR status

• Closed as program error.

Error description

• STEPS TO REPRODUCE: 
  1. Go to Security Groups, select group (eg MAXADMIN).
  2. In Applications tab, find PM application and grant access to
  Application Import and save.
  3. Go to PM application
  4. Create a new record with a Location, a Job Plan and a 3-month
  Frequency
  5. Save and approve the PM.
  6. Do Generate Forecast for next 400 days.
  7. [this message appears: BMXAA2798E - Workflow has been
  enabled for PM work order generation, but there is no active
  work order workflow process. BMXAA2798E - Workflow has been
  enabled for PM work order generation, but there is no active
  work order workflow process. BMXAT0019I - Forecasting for PM
  1040 in site BEDFORD successful. ]
  8. There are 5 entries in the Forecast tab.
  9. Create a CSV file (PM_Change.CSV) with the following values
  matching the testing data (the idea is to have a different
  Frequency value from the original one for this PM) :
  FORECASTEXISTS,FREQUENCY,FREQUNIT,PMNUM,SITEID
  1,2,MONTHS,1040,BEDFORD
  
  10. Go to Object Structures application.
  11. Create a new record TEST-TG-PM with Consumed By =
  INTEGRATION and Support Flat Structure?=checked
  12. Add main Object PM, then child Objects ASSET, PMMETER and
  PMMSEQUENCE (each with PM as parent object)
  13. Save record and reload application.
  14. Select option Add/Modify Application Import Support.
  15. Add PM application for this Object Structure and Default
  File Type = Flat file and OK.
  16. Select option Add/Modify Application Import Support again
  and open the row for PM, it always goes back to Default File
  Type = XML File, even after I select Default File Type = Flat
  File and click OK.
  17.  Force the value to be Default File Type = Flat File via the
  back-end by running the following script:
  [ update MAXINTOBJAPP set FILETYPE='FLAT' where intobjectname=
  'TEST-TG-PM' ]
  18. Go to Preventive Maintenance application.
  19. Select Application Import option. 
  20. Open lookup for Object Structure field. It shows
  'TEST-TG-PM' and select it.
  21. It gives an error:  "BMXAA6130E - Selected End Point not
  allowed due to Publish Channels object structure having Alias
  conflicts."
  
  22. To avoid this error, go to Object Structures application
  and select record TEST-TG-PM
  23. Select Add/Modify Alias option
  24. Select PM object and for all rows with Duplicate=checked ,
  change Alias value by adding _1 at end of value and click OK.
  25. Select next object ASSET and for all rows with
  Duplicate=checked , change Alias value by adding _2 at end of
  value and click OK.
  26. Select next object PMMETER and for all rows with
  Duplicate=checked , change Alias value by adding _3 at end of
  value and click OK.
  27. Next object PMSEQUENCE has no rows with Duplicate=checked.
  Click OK.
  28. Go to Preventive Maintenance application.
  29. Select Application Import option. 
  30. Open lookup for Object Structure field. It shows
  'TEST-TG-PM' and select it.
  31. This time, the Object Structure field is correctly populated
  with this value. Operation = Sync (default value)
  32. Click Select File and fetch the PM_Change.CSV file,
  Preview Result = UNchecked and OK.
  33. I get this error message:
  BMXAA5804E - Import of data in file PM_Change.CSV was
  unsuccessful.
  BMXAA5598E - Processing of an inbound transaction failed. The
  processing exception is identified in document 1 which starts at
  line 2 and ends at line 2.
  BMXAA8082E - A forecast exists for this PM or its PM hierarchy.
  Modifying this field will make the dates within the  forecast
  inaccurate. This forecast will be deleted on save. Do you want
  to continue?
  34. Click OK (no other button available)
  35. Select the relevant PM record.
  36. The Frequency value has not changed and the Forecast values
  are still there.
  37. So the changes from the CSV file and 'Application Import'
  are not applied to the PM record(s) due to the forecast.
  
  For comparison purposes, use other method to update the PM
  records Frequency via the Maximo UI:
  a1.  Go to Preventive Maintenance application and select the
  same PM.
  a2.  Change Frequency value from 3 to 2 and save the record.
  a3.  You get error message: BMXAA8123E - Errors exist in the
  application that prevent this action from being performed.
  Correct the errors and try again. 
  a4.  Click on the (i) icon that appeared on the Frequency tab.
  a5.  It shows: A forecast exists for this PM or its PM
  hierarchy.  Modifying this field will make the dates within the
  forecast inaccurate. This forecast will be deleted on save. Do
  you want to continue? (BMXAA8082) [Yes] [Close]
  a7.  Click Yes and save the record.
  a8.  The Frequency value has been changed accordingly and the
  Forecast values have been removed.
   
  RESULTS:
  The changes to the PM record made with 'Application Import' and
  the CSV file are ignored when the PM has a forecast generated,
  and these changes from the CSV file and 'Application Import' are
  therefore not applied to the PM record.
   
  EXPECTED RESULTS:
  
  The changes from the CSV file and 'Application Import' should
  be applied to the PM record, regardless whether it has a
  forecast on it or not.
   
  REPORTED IN VERSION:
  
  Maximo TPAE 7.6.1.3-IFIX20230117-1942
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CHANGES TO PM RECORD MADE WITH 'APPLICATION IMPORT' OF A CSV *
  * FILE ARE IGNORED WHEN THE PM HAS A FORECAST GENERATED        *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 8.x 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:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels