IJ48300: MAXIMO IS ALLOWING A COUNT BOOK WITH A OBSOLETE ITEM TO BE DUPLICATED

APAR status

• Closed as program error.

Error description

• PROBLEM:
  
  Maximo should check the item STATUS when we try to duplicate
  the Count Book, just like it checks when we try to create one.
  
  PERFORMANCE ISSUE: N/A
  
  STEPS TO REPRODUCE:
  Maximo should check the item STATUS when we try to duplicate the
  Count Book, just like it checks when we try to create one.
  
  Steps to reproduce:
  Identity a Count Book record that has a item that is OBSOLETE
  Or create a Count Book with a ACTIVE item, than change this item
  to OBSOLETE or PENDING
  
  If we try to create a new Count Book with this same item, Maximo
  won't allow.
  
  But if we choose to duplicate the Count Book, then the OBSOLETE
  item will be in this new Count Book.
  
  CURRENT ERRONEOUS RESULT:
  
  Count Book application doesn't check if there's a OBSOLETE item
  in there if we use the duplicate action.
  
  EXPECTED RESULT:
  
  When you try to duplicate a Count Book that has a OBSOLETE item
  in there, Maximo should not allow the Count Book to be
  duplicated.
  
  ADDITIONAL INFO: N/A
  
  ENVIRONMENT (SYSTEM INFO):
  
  Tivoli's process automation engine 7.6.1.3-IFIX20230324-1804
  Build 20220823-0909 DB Build V7613-344 HFDB Build HF7613-67
  
  SECURITY IMPACT (Y/N): N/A
  

Local fix

• To work around that problem, you need to recreate the Count Book
  Line doing this:
  
  - Open the Count Book
  - Change the "Selection Type" field
  
  If you have ALL for example, change it to BIN, save it, then
  change it back to ALL.
  - Check the Count Book line again, the OBSOLETE item won't be
  there.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * _MAXIMO_                                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * MAXIMO IS ALLOWING A COUNT BOOK WITH A OBSOLETE ITEM TO BE   *
  * DUPLICATED                                                   *
  ****************************************************************
  

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