IZ25949: A-00001: UNIQUE CONSTRAINT (MAXIMO.WOANCESTOR_NDX1)MESSAGE IN LOG FILE FOR A DUPLICATED UNSAVED WO

APAR status

• Closed as program error.

Error description

• This incident is only reproducible in Maximo 6.2.0,
  (The error is not appearing in the screen but in the log file.
  On the front end of Maximo no message or error. Only in the log
  file)
  
  You can not reproduce this against Maximo 6.2.1, Maximo 6.2.2
  
  Steps to reproduce:
  
  1. Create a WO, populate all values
  2. Create a material line in plans
  3. Enter a Condition Enabled Item (btw. later it was found it's
  not necessary to have cond-enabled item)
  4. Populate all mandatory fields (leave it as a stocked item
  so you
  have to populate Condition code)
  5. Save WO
  6. Duplicate WO (do not save yet!)
  7. Remove any mandatory value from item line (to make Maximo
  displays message that field is mandatory etc.)
  8. Try to save, Maximo wont allow
  9. Re-populate the missing value
  10. Save
  11. Wo saves, but with woancestor exceptions
  
  
  The Product Manager (D.Havican)has commented that IBM should fix
  this bug and that this will not be a problem
  
  Business case received from IBM Team Lead for BP(=end client) as
  follows:
  
  "When in a system an error appear ,it means the system is not
  working properly and therefore:
  -Can affect the performance because log need to be updated and
  the system is trying to do something it shouldn't.
  -System expects something to happen and it's not therefore could
  have hidden consequences.
  -Multiple users(we are expecting over a 1000 in NAG) generating
  the same error in multiple records on the same time could have a
  potential effect on the system.."
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Maximo users                             *
  ****************************************************************
  * PROBLEM DESCRIPTION: This incident is only reproducible in   *
  *                      Maximo 6.2.0,                           *
  *                                                              *
  *                      (The error is not appearing in the      *
  *                      screen but in the log file.             *
  *                                                              *
  *                      On the front end of Maximo no message   *
  *                      or error. Only in the log               *
  *                                                              *
  *                      file)                                   *
  *                                                              *
  *                      You can not reproduce this against      *
  *                      Maximo 6.2.1, Maximo 6.2.2              *
  *                                                              *
  *                      Steps to reproduce:                     *
  *                                                              *
  *                      1. Create a WO, populate all values     *
  *                                                              *
  *                      2. Create a material line in plans      *
  *                                                              *
  *                      3. Enter a Condition Enabled Item (btw. *
  *                      later it was found it's                 *
  *                                                              *
  *                      not necessary to have cond-enabled      *
  *                      item)                                   *
  *                                                              *
  *                      4. Populate all mandatory fields (leave *
  *                      it as a stocked item                    *
  *                                                              *
  *                      so you                                  *
  *                                                              *
  *                      have to populate Condition code)        *
  *                                                              *
  *                      5. Save WO                              *
  *                                                              *
  *                      6. Duplicate WO (do not save yet!)      *
  *                                                              *
  *                      7. Remove any mandatory value from item *
  *                      line (to make Maximo                    *
  *                                                              *
  *                      displays message that field is          *
  *                      mandatory etc.)                         *
  *                                                              *
  *                      8. Try to save, Maximo wont allow       *
  *                                                              *
  *                      9. Re-populate the missing value        *
  *                                                              *
  *                      10. Save                                *
  *                                                              *
  *                      11. Wo saves, but with woancestor       *
  *                      exceptions                              *
  *                                                              *
  *                      The Product Manager (D.Havican)has      *
  *                      commented that IBM should fix           *
  *                                                              *
  *                      this bug and that this will not be a    *
  *                      problem                                 *
  *                                                              *
  *                      Business case received from IBM Team    *
  *                      Lead for BP(=end client) as             *
  *                                                              *
  *                      follows:                                *
  *                                                              *
  *                      "When in a system an error appear ,it   *
  *                      means the system is not                 *
  *                                                              *
  *                      working properly and therefore:         *
  *                                                              *
  *                      -Can affect the performance because log *
  *                      need to be updated and                  *
  *                                                              *
  *                      the system is trying to do something it *
  *                      shouldn't.                              *
  *                                                              *
  *                      -System expects something to happen and *
  *                      it's not therefore could                *
  *                                                              *
  *                      have hidden consequences.               *
  *                                                              *
  *                      -Multiple users(we are expecting over a *
  *                      1000 in NAG) generating                 *
  *                                                              *
  *                      the same error in multiple records on   *
  *                      the same time could have a              *
  *                                                              *
  *                      potential effect on the system.."       *
  *                                                              *
  *                      LOCAL FIX:                              *
  *                                                              *
  *                      n/a                                     *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  A-00001: UNIQUE CONSTRAINT (MAXIMO.WOANCESTOR_NDX1)MESSAGE IN
  LOG FILE FOR A DUPLICATED UNSAVED WO
  

Problem conclusion

• The problem is that the first failed save already created
  woancestor etc record throught the postcommitaction  and the
  second save do it again which cause the error.
  
  Issue 06-16290((Improper and inefficient use of EventListener
  in Asset, MatUseTrans, LabTrans, PM and WO Mbos.) fixed this
  problem by call postcommitaction through listerner in most
  releases except 620. In this ssue , it only fixed woancestor
  piece.
  

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

  WORK ORDER TRAC

• Fixed component ID

  5724R46WO

Applicable component levels

• R620 PSY

     UP