SCAN_AS_NO_ROLL is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.
Short Dump Classification: O - Resource Shortage
You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.
Also check out the Comments section below to view or add related contributions and example screen shots.
Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.
Please see search hints for more details about the possible cause of this runtime error and how it could be avoided.
Please see send to sap for more details about the possible cause of this runtime error and how it could be avoided.
SCAN ABAP-SOURCE: No memory available for key word list.
Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.
Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.
If you use the SCAN ABAP-SOURCE statement with the KEYWORDS FROM
<runtime parameter>-NAME, you require main memory space to generate the list of key
words to be returned. In this case, <runtime parameter> bytes was required, but this
was not available.
Please see not enough roll for more details about the possible cause of this runtime error and how it could be avoided.
Please see capacity error for more details about the possible cause of this runtime error and how it could be avoided.
SCAN_AS_NO_ROLL - scan as no roll SCAN_AS_LEVEL_TAB_DESTROYED - scan as level tab destroyed SCAN_AS_FROM_NEGATIVE - scan as from negative SAPSQL_WRONG_OBJECT_REFERENCE - sapsql wrong object reference SAPSQL_WRONG_CREATING_ENTRY - sapsql wrong creating entry SAPSQL_WHERE_UNKNOWN_OPERATOR - sapsql where unknown operator