Symptom
ABAP runtime error 'SYSTEM_NO_ROLL' occurs when fetching error logs in the "OData Error Log" app.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the app "OData Error Log" app.
- Filter the "Time" frame example "Past 2 Weeks".
- Observe that the app displays "ABAP runtime error 'SYSTEM_NO_ROLL'" .
Cause
The query spans a time range that returns too many log entries, and the app may not be able to query them reliably.
Resolution
The error can occur when the query returns a large number of log entries, resulting in high memory consumption.
To resolve the issue, apply a time filter and search for error logs using smaller time intervals, for example, the last 24 hours. If the required logs are not found, gradually expand the time range, such as to the past week and then the past two weeks, until the relevant data is retrieved.
Avoid querying large time ranges in a single search, as this may cause the application to attempt to retrieve an excessive number of log entries and lead to the error.
See Also
Keywords
odata error log, abap runtime error, SYSTEM_NO_ROLL, no log entries, app error on open, gateway error log, /IWFND/ERROR_LOG, large time range, too many log entries, time filter, incremental search, message monitoring, query volume, performance, troubleshooting , KBA , BC-SRV-AIF , Application Interface Framework , Problem
SAP Knowledge Base Article - Public