IJ46151: USING MIF OR APPLICATION IMPORT TO UPDATE SERIALNUM FIELD FOR ASSETS THAT HAVE A GROUPNAME RESULTS IN THE ERROR: BMXAA8665W - DO

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION:
  Using MIF or Application Import to update serialnum field for
  assets that have a groupname results in the error:
  BMXAA8665W - Do you want to allow sequence number duplication?
  
  Even using interactive=0 for OSLC or mxe.int.interactiveimport=0
  the question is not suppressed.
  
  Updating serialnum from UI does not result in the error.
  
  STEPS TO REPRODUCE:
  The steps below use MAXDEMO as an example:
  
  1)Go to Asset and search for asset 13150.
  Fill in the field Meter Group with the value CLASS8.
  
  Save.
  
  2)POST the information below:
  
  URL: http://MXSERVER/maximo/oslc/os/mxasset?lean=1&interactive=0
  
  
  
  x-method-override: SYNC
  
  Payload:
  {
  "assetnum":"13150",
  "siteid":"BEDFORD",
  "groupname":"CLASS8",
  "serialnum":"TEST123"
  }
  
  RESULTS:
  {
  "yncuserinputoptions": {
  "no": "16",
  "yes": "8"
  },
  "Error": {
  "extendedError": {
  "moreInfo": {
  "href":
  "http://mxserver:80/maxrest/oslc/error/messages/BMXAA8665W"
  }
  },
  "yncerror": true,
  "reasonCode": "BMXAA8665W",
  "message": "BMXAA8665W - Do you want to allow sequence number
  duplication?",
  "yncuserinputid": "duplicateMeterSequence",
  "statusCode": "400"
  }
  }
  
  Stack:
  [3/16/23 10:23:07:504 PDT] 00002269 SystemOut O 16 Mar 2023
  10:23:07:504 [ERROR] [MAXIMO] [CID-MXOSLC-281220] BMXAA8665W -
  Do you want to allow sequence number duplication?
  psdi.util.MXApplicationYesNoCancelException: BMXAA8665W - Do you
  want to allow sequence number duplication?
  at psdi.app.asset.Asset.checkForDuplicateMeterSequenceValues(As
  set.java:6384)
  at psdi.app.asset.Asset.generateAssetMetersForMeterGroup(Asset.
  java:6333)
  at psdi.app.asset.Asset.save(Asset.java:1201)
  at psdi.mbo.MboSet.saveMbos(MboSet.java:7914)
  at psdi.mbo.MboSet.validateTransaction(MboSet.java:7894)
  at psdi.txn.MXTransactionImpl.validateTransaction(MXTransaction
  Impl.java:375)
  at psdi.txn.MXTransactionImpl.saveTransaction(MXTransactionImpl
  .java:207)
  at psdi.txn.MXTransactionImpl.save(MXTransactionImpl.java:156)
  at psdi.iface.mos.MosProcessImpl.save(MosProcessImpl.java:2605)
  at psdi.iface.mos.MosProcessImpl.processExternalData(MosProcess
  Impl.java:392)
  at psdi.iface.mos.MosProcessImpl.processObjectStructureService(
  MosProcessImpl.java:251)
  at psdi.iface.mic.MicService.processObjectStructureData(MicServ
  ice.java:917)
  at
  psdi.iface.mic.MicService.processOSLCAsJSON(MicService.java:621)
  
  at com.ibm.tivoli.maximo.oslc.provider.OSPOSTRouteHandler.handl
  eRequest(OSPOSTRouteHandler.java:876)
  
  
  EXPECTED RESULTS:
  no error should return.
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.2
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * USING MIF OR APPLICATION IMPORT TO UPDATE SERIALNUM FIELD    *
  * FOR ASSETS THAT HAVE A GROUPNAME RESULTS IN THE ERROR:       *
  * BMXAA8665W                                                   *
  ****************************************************************
  Problem:
  When trying to update an asset record using MIF or Application
  import, that already has a group name results in the duplication
  error.
  Change 1: On UI, while updating the record, the user can allow
  duplication or disallow duplication as required by selecting
  yes/no options. This selection is not available for MIF cases,
  thus by default in the non-interactive form (non-ui / updation
  by MIF) the default user input allows the duplicate sequence
  number.
  Change 2: If the meter group is already added and the one that
  is being updated has a similar meter associated, then the
  validation on the field leads to the deletion of the duplicate
  meters, as well as the deletion of the previous meter associated
  which leads to missing meters from the record, thus for MIF like
  conditions with the flag of suppressing duplicate value, the
  meter names won't be validated for the duplicate values.
  

Problem conclusion

• This will be fixed 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