Hi All

I am using MXRECEIPT object structure to process the material receipt transactions received from an external system. I followed the instructions from the below note to build the requests in the json format. 

Material and rotating item receipt object

As mentioned in the note, I sent a request for a material receipt which created a receipt with the status WINSP. But when I tried with a follow-up request to complete the inspection with the inspection details I received the below error.

{

  "Error": {

    "extendedError": {

      "moreInfo": {

        "href": http://maximo-project/maxrest/oslc/error/messages/BMXAA1407E

      }

    },

    "reasonCode": "BMXAA1407E",

    "message": "BMXAA1407E - The MATRECTRANS object cannot be added because it already exists in the application. An integration message cannot create an object that already exists.",

    "statusCode": "400"

  }

}

 Note: When I included the inspection details in the first transaction, it successfully created both RECEIPT and TRANSFER transactions in Maximo. I just want to know if I can have this in two steps - first to indicate that items are received (waiting for inspection) and then followed up by the completion of the inspection as we do in Maximo. 

Another related question, is there anyway to get a response for an interface which is based on non-persistent object e.g MXRECEIPT?

Properties with '*' or field names will not fetch any thing as the object is non-persistent.

------------------------------
Manikanda Prabhu Alexander
------------------------------

Hi Manikanda,

I suggest using the header x-method-override=SYNC. I had a similar issue with Meter readings object structure and referred to this IBM article. Have you already tried including this or any other headers in your request?

Let me know if this helps!

------------------------------
Vijayalakshmi Mane
Technical Consultant
Bentley Systems Netherlands B.V.
sHertogenbosch, The Netherlands
------------------------------

Original Message:
Sent: Mon August 11, 2025 12:52 PM
From: Manikanda Prabhu Alexander
Subject: Material receipts through Rest API

Hi All

I am using MXRECEIPT object structure to process the material receipt transactions received from an external system. I followed the instructions from the below note to build the requests in the json format. 

Material and rotating item receipt object

As mentioned in the note, I sent a request for a material receipt which created a receipt with the status WINSP. But when I tried with a follow-up request to complete the inspection with the inspection details I received the below error.

{

  "Error": {

    "extendedError": {

      "moreInfo": {

        "href": http://maximo-project/maxrest/oslc/error/messages/BMXAA1407E

      }

    },

    "reasonCode": "BMXAA1407E",

    "message": "BMXAA1407E - The MATRECTRANS object cannot be added because it already exists in the application. An integration message cannot create an object that already exists.",

    "statusCode": "400"

  }

}

 Note: When I included the inspection details in the first transaction, it successfully created both RECEIPT and TRANSFER transactions in Maximo. I just want to know if I can have this in two steps - first to indicate that items are received (waiting for inspection) and then followed up by the completion of the inspection as we do in Maximo. 

Another related question, is there anyway to get a response for an interface which is based on non-persistent object e.g MXRECEIPT?

Properties with '*' or field names will not fetch any thing as the object is non-persistent.

------------------------------
Manikanda Prabhu Alexander
------------------------------