SCAN_AS_LEVEL_TAB_DESTROYED 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: I - Internal Kernel Error
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 internal error for more details about the possible cause of this runtime error and how it could be avoided.
At the beginning of level <runtime parameter>, row <runtime parameter> was created in level table
<runtime parameter>-NAME. At the end of level <runtime parameter>, row <runtime parameter> coult not be read in the
level table.
Internal error with SCAN ABAP-SOURCE: Row not found in level table.
does not exist.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
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 SAPSQL_WHERE_QUOTES - sapsql where quotes