IV91123: ERROR BMXAA8229W WHEN GENERATING WO FROM A PM PAGE WITHOUT USING THE PUBLICFREQUENCY

APAR status

• Closed as program error.

Error description

• TITLE
  When generating WO from a PM page without using the public
  frequency you get error BMXAA8229W - The WorkOrder
  registration:  Site = AEL Intervention =2530538  has been
  updated by another user.
  
  PROBLEM DESCRIPTION
  After upgrading from 7.1.1.7 to 7.5 client is encountering an
  issue When generating WO from a PM page without using the public
  frequency criteria, we have the following error message:
  BMXAA8229W - The WorkOrder registration:  Site = AEL
  Intervention =2530538  has been updated by another user.  Your
  changes have not been saved.  Update registration and try again.
  
  REPRODUCTION STEPS
  1. Go To Preventive Maintenance > Preventive Maintenance > List
  Tab
  Filter for PM: 8505 (The selected PM has to be a top-level
  record with multi-level children PMs)
  Click the Frequency Tab
  The fields below display;
  Frequency: 0
  Frequency Unit: Days
  Alert Lead (Days) 0
  
  2. Click the PM Hierarchy tab
  Select Action
  Generate Work Orders
  Generate WOs Due Today Plus This Number of Days: 0
  Use Frequency Criteria: Uncheck the box
  Run Work Order Generation in the Background: Uncheck the box
  Notification E-mail for Work Order Generation:
  Click OK
  
  Current Erroneous Result:
  Having a multi-level parent-children hierarchy in PMs, which
  uses different settings (specifically WOSTATUS) for WO
  generation, causes the PM WOGEN process to fail presenting the
  following message:
  
  BMXAA8229W - Record WORKORDER : Site=AEL Work Order=2530538 has
  been updated by another user. Your changes have not been saved.
  Refresh the record and try again.
  
  
  Expected Result:
  No error messages should be displayed and the applicable Work
  Order records must be created for the PM and its children.
  
  General Comments:
  If the children are removed, the parent PM creates WO correctly.
  If PM is generated on the children (when detached from the
  parent!), the generation is correct.
  
  If the parent is generated with with PM-01 S8817B child is OK.
  If parent is generated with the child N8871B-03, then an error
  message occurs, nothing is generated.
  
  
  
  
  
  System Information:
  Maximo /SCCD release MAM 7.5.0.7
  WebSphere Release and fixpack level IBM WebSphere App Server
  7.0.0.15
  TPAE 7.5.0.7 IFIX 20150305-1634
  Microsoft SQL Server 10.50
  Windows Server 2008 R2 6.1 build 7601 SP1
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Users of the Preventive Maintenance application.      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Maximo prevents WO creation using PM Work Order generation   *
  * action in Maximo 7.5.                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• A fix has been made and delivered to the stream.
  

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

• R750 PSY

     UP