Maximo Open Forum

 View Only
  • 1.  Maximo Mobile EAM 9.0

    Posted 9 hours ago

    Hi Team,

    Hope you are doing well.

    Has anyone come across this issue in Maximo Mobile EAM 9.0 (Maximo 7.6.1.3)?

    This is related to the Inventory Receiving mobile app. The refresh/sync is failing with the below error. I checked in Maximo, and the saved query mentioned below is not explicitly configured.

    Error details:

    Sync failed
    BMXAA1649E – A programming error resulted in a null pointer exception.

    Total records: 0
    Total pages: 0
    Completed pages: 0
    Total size: 0.00 KB
    Elapsed time: 1s
    Start time: 2/10/2026, 6:01:43 AM
    End time: 2/10/2026, 6:01:43 AM
    Average speed: 0.00 records/s

    Object Structure: MXAPIRECEIPT
    Saved Query: CREATEDLOCALLY
    Trigger Source: irmobile

    Please let me know if anyone has seen this issue before or has any insights/workarounds.

    Thanks,
    Rajkumar Selvaraj


    #EverythingMaximo
    #MaximoUserGroups
    #Mobility

    ------------------------------
    Rajkumar Selvaraj
    ------------------------------


  • 2.  RE: Maximo Mobile EAM 9.0

    Posted 8 hours ago
    Edited by Steven Shull 8 hours ago

    This is a known issue in some versions of Maximo Mobile 9.0. I reported this but it was when I was at my previous job and I'm not sure if it was ever a public defect (I'm struggling to find it). 

    The MXAPIRECEIPT is a special object structure that is only designed for processing receipts. The issue was the load was being called on this dataset which would trigger the request to retrieve data from the server which would always fail. I remember the framework was enhanced to support loading from device storage (to not make the network request) which I think is what was done here but it's been too long. I would try and apply a later IFIX if you haven't already. 



    ------------------------------
    Steven Shull
    Naviam
    ------------------------------



  • 3.  RE: Maximo Mobile EAM 9.0

    Posted 8 hours ago

    Thanks, Steven, for the response. We are planning to open a ticket with IBM, or alternatively apply the latest iFix as you suggested, to try to see if that resolve this issue. In the meantime, if you find any additional information, please share it with us.

    Thanks again!



    ------------------------------
    Rajkumar Selvaraj
    ------------------------------