Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  API error with PLUSDESTCONTROL object on MAS 9

    Posted 03/06/25 07:44 AM
    I need to get CU Estimate records via the Maximo REST API. When I add the PLUSDESTCONTROL object to an object structure, or use the out-of-the-box PLUSDESTCONTROL object structure, in a GET API call, I get the following error message:

    {
        "Error": {
            "errorattrname": "nprequestnum",
            "extendedError": {
                "moreInfo": {
                    "href": "http://localhost/maximo/api/error/messages/BMXAA0031E"
                }
            },
            "correlationid": null,
            "reasonCode": "BMXAA0031E",
            "message": "BMXAA0031E - The PLUSDESTCONTROL object is read only. Verify the business rules for the MBO or MBOSET object.",
            "statusCode": "400"
        }
    }

    This error is happening on MAS 9, but works fine on Maximo 7.6.1.3.

    Does anyone have any ideas what introduced this behavior, and what the correct fix is?

    -Theo Pozzy



  • 2.  RE: API error with PLUSDESTCONTROL object on MAS 9

    Posted 03/07/25 03:25 AM

    Have you checked that the user for the APIKey you are using has access to the Object Structure - in MAS most of the object structures used for API calls are called MXAPI<OBJECTNAME> - e.g. MXAPIWODETAIL. So for consistency I would create an MXAPIPLUSDESTCONTROL object structure for integration first. Then look at the security group for your API user and make sure that your object structure security is granted for your new object structure.



    ------------------------------
    Steve Lee
    Maximo Technical Sales Specialist
    IBM
    Leeds
    ------------------------------



  • 3.  RE: API error with PLUSDESTCONTROL object on MAS 9

    Posted 03/09/25 02:33 PM
    Steve,

    I checked the security and also added the PLUSDESTCONTROL object to an object structure that I was working via the API with other objects. It's only that object that causes this error. I noticed that the "nprequestnum" non-persistent field is referenced in the error message. I'm not sure that's relevant, but it's interesting that a non-persistent field is getting a "read-only" error.

    -Theo



    Original Message


Related Content