on ‎2021 Nov 26 3:46 PM
Request clarification before answering.
Hi andrew.mai ,
Yes, this happens if you're sending `if-match` or `if-none-match` headers and the respective entity has no etag configured. In future versions of @sap/cds (Node.js) we will ignore those headers. Currently, the error 'The requested resource is not concurrent' is thrown.
Best regards,
David
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrew,
I am not sure, but it seem it is related with some service we can find in tcode SICF. You can debug it, looking for the method you can check in SCIF. For more information, read the following blog: https://blogs.sap.com/2016/07/15/how-to-debug-the-bsp-application-a-tutorial/
As it seems also it is a end point, you need to know who is the SAP user ID this end point is running.
I did it for idocxml, usually it retunrs in the webUI or the other transaction sending an IDOC an error 409, but doint the debugging session I realized there were troubles related with parsing or others.
I hope it helps you
Regards
Eduardo Hinojosa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 6 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.