cancel
Showing results for 
Search instead for 
Did you mean: 

Problems with changing ItemWarehouseInfoCollection trough Service Layer

sap-chris
Explorer
0 Kudos

Hi Everyone

We've a problem with Service Layer.


We want to change the value of "U_Lagerort" in the WarehouseInfoCollection of an Item. To do this we send the command below to https://xx.xx.xx.xx:50000/b1s/v1/Items('123456')

{
  "ItemWarehouseInfoCollection": 
  [
    {
      "WarehouseCode":"01",
      "U_Lagerort":"xx-xx-xx"
    }
  ]
}

If we do that with a user who have manager rights, everthing works fine. If we use another user with restricted rights, we get the error message below:

{
   "error" : {
      "code" : -2035,
      "message" : {
         "lang" : "en-us",
         "value" : " [OITM.SUoMEntry][line: 2] , 'This entry already exists in the following tables (ODBC -2035)'"
      }
   }
}

For us, the error message makes no sense, as we don't change any data who affect SUoMEntry. Furthermore the user has enough rights to change the datas of SUoMEntry when he use SBO Client.

Accepted Solutions (0)

Answers (3)

Answers (3)

sap-chris
Explorer
0 Kudos

Dear ankit.chauhan1

Thank for your reply.

Yes we can reproduce the issue every time.

Where can I find this component? I'm sorry but it's the first time we have to deal with such a problem.

Kind regards

Christian

ANKIT_CHAUHAN
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear sap-chris,

An incident can be created in SAP Business One Support Launchpad. This requires an S-User ID. You should contact to your SAP Business One Partner for the same. They should assist you in creating the incident and getting the S-User ID.

Kind regards,

ANKIT CHAUHAN

SAP Business One Support

sap-chris
Explorer
0 Kudos

Thank you ankit.chauhan1

ANKIT_CHAUHAN
Product and Topic Expert
Product and Topic Expert
0 Kudos

Dear sap-chris,

If you feel that all the configurations and the setups are fine and the issue can be reproduced every time, it would be better to raise an incident for SAP Business One Support Team under the component SBO-SDK-SVL to get it investigated/checked.

Kind regards,

ANKIT CHAUHAN

SAP Business One Support

sap-chris
Explorer
0 Kudos

Hi SAP-Team

Any Ideas how to solve this Problem/Bug?