IV00905: BMXAA4129E - RECORD ALREADY EXISTS FOR ATTRIBUTE / AFTER CHANGE

APAR status

• Closed as program error.

Error description

• BMXAA4129E - Record already exists for Attribute=SIZE,
  Asset=11430,
  Section=, Site=BEDFORD, Linear Specification Id=0.
  
  Error happens after changing an attribute from the Item Master
  specifications tab and hitting save.
  
  ---
  I tested this issue in Core 7118 and I confirmed it happens.
  
  
  
  ---
  STEPS TO REPLICATE: (From Live Meeting)
  ==I used PUMP100 on this example and changed the value for
  "STAGE"
  attribute==
  
  1) In Item Master, choose any Item with one or more
  Specification
  attributes (It Master, Specifications tab).
  2) Change the attribute "Description" field and hit "Save".
  
  This message is displayed:
  
  BMXAA4129E - Record already exists for Attribute=SIZE,
  Asset=11430,
  Section=, Site=BEDFORD, Linear Specification Id=0.
  

Local fix

• No Workaround has been found.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: MAXIMO                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: BMXAA4129E - RECORD ALREADY EXISTS FOR  *
  *                      ATTRIBUTE / AFTER CHANGE                *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  *                                                              *
  *                                                              *
  *                                                              *
  ****************************************************************
  BMXAA4129E - RECORD ALREADY EXISTS FOR ATTRIBUTE / AFTER CHANGE
  

Problem conclusion

• <I could not replicate this problem in the internal 7119
  base-service build - Base Services 7.1.1.9 Build 20110618-0100
  DB Build V7119-52. I could save the Item with no index error in
  ASSETSPEC_NDX1. I tested this in ORACLE, SQLSERVER, and DB2.
  However, I could replicate this problem in HF7118# SQLServer
  only. >
  
  
  
  
  
  The fix for this APAR is contained in the following maintenance
  package:
  
    | release\fix pack | REL 7.1.1.9 - BS
  

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

  ASSETS

• Fixed component ID

  5724R46AS

Applicable component levels

• R711 PSY

     UP