‎2022 Jun 01 7:51 PM - edited ‎2024 Feb 04 3:54 AM
Request clarification before answering.
Hi Ruchi,
The error occured at the SAP end itself.
The API process data that requires more memory - failing which it creates memory dump. That is why you get the 500 Inernal server error.
The Error code SYSTEM_NO_ROLL will occurs when the inernal memory error.
You can ask from SAP side to see ST22 t-code and analyze the dump.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ruchi,
Its difficult to confirm without letting us know how you have formed your query, but I'm quite sure, the error has occurred due to fetching of large volume of data where you have not applied any filters( and is an open ended query) because I see that the query timed out after 1 minute and 15 seconds.( the time out is set to 6 sec). To resolve this problem, you should leverage 'pagination' in your Odata query in other words, apply filters to reduce the size of the output.
Here is a nice blog to understand the concept better.
Hope this helps. Thanks! Amith Nair
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Unfortunately, I cannot help further because you've hidden the business object that you're using to form the query in postman, if you can share that I should be able to give some direction.The business Object will help me determine the metadata. Also I noticed that you've used ''&GLAccount=..." at the end of the query- I don't think this is correct since you already have filter applied at the beginning of the query.
Thanks! Amith Nair
| User | Count |
|---|---|
| 22 | |
| 10 | |
| 9 | |
| 5 | |
| 5 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.