IBM Support

IV52138: ERROR BMXAA1407E WHEN TRAYING TO ADD METERREADINGS TO ASSETS VIAINTEGRATION FRAMEWORK REST API / WEBSERVICES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Error 400: BMXAA1407E - The ASSETMETER object cannot be added
    because
    it already exists in the application. An integration message
    cannot cr
    eate an object that already exists.
    
    This issue happens either for formed URL or using a HMTL form to
    POST
    data to REST API.
    
    The MXMETERDATA object structure is being used.
    
    The URL used is this:
    http://myserver:9080/maxrest/rest/os/MXMETERDATA?_action=AddChan
    ge&asset
    num=11430&siteid=bedford&metername=O-PRESSUR&newreading=10&newre
    adingdat
    e=2013-08-26T00:01:00&_lid=wilson&_lpwd=wilson
    
    Also, L2 has tested the following HTML form:
    
    https://ecurep.mainz.de.ibm.com/rest/download/05433%2C756%2C000/
    mail2013
    0903-194350-macorrea/MXMETERDATA_Sample.html
    
    IMPORTANT:
    
    We can see the same error using a Regular WebService when the
    operation
    is Create.
    For Sync Operation, it works fine.
    
    It seemns the problem is in the MXMETERDATA object structure
    Create
    operation only.
    
    From the REST Logger we can see this message:
    
    <CreateMXMETERDATA xmlns="http://www.ibm.com/maximo">
      <MXMETERDATASet>
        <METERDATA>
          <ORGID>EAGLENA</ORGID>
          <ISDELTA>Y</ISDELTA>
          <NEWREADINGDATE>2012-04-23T12:00:01-03:00</NEWREADINGDATE>
          <CHANGEBY>MAXADMIN</CHANGEBY>
          <INSPECTOR>MAXADMIN</INSPECTOR>
          <ASSETNUM>ASSETIBM</ASSETNUM>
          <MEASUREMENTVALUE>110.0</MEASUREMENTVALUE>
          <ASSETMETERID>27</ASSETMETERID>Page 35 of 54
          <CHANGEDATE>2012-04-23T12:00:01-03:00</CHANGEDATE>
          <METERNAME>RUNHOURS</METERNAME>
          <DOROLLOVER>N</DOROLLOVER>
          <SITEID>BEDFORD</SITEID>
          <NEWREADING>110</NEWREADING>
        </METERDATA>
      </MXMETERDATASet>
    </CreateMXMETERDATA>
    
    
    Steps to replicate
    
    Create a new ASSET as ASSETIBM
    Add RUNHOURS meter
    Save
    
    Use the attached HTML Form to post a new Meter Reading to
    MXMETERDATA
    Object Structure
    
    The browser will return the error
    Error 400: BMXAA1407E - The ASSETMETER object cannot be added
    because
    it already exists in the application. An integration message
    cannot cr
    eate an object that already exists.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO MIF users who import meter readings.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Error 400: BMXAA1407E - The ASSETMETER object cannot be      *
    * added because it already exists in the application. An       *
    * integration message cannot create an object that already     *
    * exists.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply latest fix pack.                                       *
    ****************************************************************
    Error 400: BMXAA1407E - The ASSETMETER object cannot be added
    because it already exists in the application. An integration
    message cannot create an object that already exists.
    This issue happens either for formed URL or using a HMTL form to
    POST data to REST API.
    The MXMETERDATA object structure is being used.
    The URL used is this:
    http://myserver:9080/maxrest/rest/os/MXMETERDATA?_action=AddChan
    ge&assetnum=11430&siteid=bedford&metername=O-PRESSUR&newreading=
    10&newreadingdate=2013-08-26T00:01:00&_lid=wilson&_lpwd=wilson
    
    IMPORTANT:
    We can see the same error using a Regular WebService when the
    operation is Create.
    For Sync Operation, it works fine.
    
    It seems the problem is in the MXMETERDATA object structure
    Create operation only.
    
    From the REST Logger we can see this message:
    
    <CreateMXMETERDATA xmlns="http://www.ibm.com/maximo">
      <MXMETERDATASet>
        <METERDATA>
          <ORGID>EAGLENA</ORGID>
          <ISDELTA>Y</ISDELTA>
          <NEWREADINGDATE>2012-04-23T12:00:01-03:00</NEWREADINGDATE>
          <CHANGEBY>MAXADMIN</CHANGEBY>
          <INSPECTOR>MAXADMIN</INSPECTOR>
          <ASSETNUM>ASSETIBM</ASSETNUM>
          <MEASUREMENTVALUE>110.0</MEASUREMENTVALUE>
          <ASSETMETERID>27</ASSETMETERID>Page 35 of 54
          <CHANGEDATE>2012-04-23T12:00:01-03:00</CHANGEDATE>
          <METERNAME>RUNHOURS</METERNAME>
          <DOROLLOVER>N</DOROLLOVER>
          <SITEID>BEDFORD</SITEID>
          <NEWREADING>110</NEWREADING>
        </METERDATA>
      </MXMETERDATASet>
    </CreateMXMETERDATA>
    
    Steps to replicate
    1 Create a new ASSET as ASSETIBM
    2 Add RUNHOURS meter
    3 Save
    4 Use the attached HTML Form to post a new Meter Reading to
    MXMETERDATA  Object Structure
    
    The browser will return the error
    Error 400: BMXAA1407E - The ASSETMETER object cannot be added
    because it already exists in the application. An integration
    message cannot create an object that already exists.
    

Problem conclusion

  • "Error 400: BMXAA1407E - The ASSETMETER object cannot be added
    because it already exists in the application. An integration
    message cannot create an object that already exists." no longer
    occurs, import is successful.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	| release\fix pack\interim fix for Release 7.1.1.13 of Base
    Services and Release 7.5.0.6 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV52138

  • Reported component name

    INTEGRATION

  • Reported component ID

    5724R46I1

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-11-18

  • Closed date

    2014-01-09

  • Last modified date

    2014-01-09

  • 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

    INTEGRATION

  • Fixed component ID

    5724R46I1

Applicable component levels

  • R750 PSY

       UP



Document information

More support for: Maximo Asset Management

Software version: 750

Reference #: IV52138

Modified date: 09 January 2014