SAPSQL_ANNEX_ILLEGAL_CODE 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 illegal code 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.
At the end of the SQLS control block sequence for the optional
dummy SQLS follow-on control blocks, the flag byte has resulted
in different optional additions.
The flag byte <runtime parameter> is unknown.
Internal error: Unknown flag combination in SQLS follow-on control block
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see illegal code 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.
SAPSQL_ANNEX_ILLEGAL_CODE - sapsql annex illegal code SAPSQL_AMBIGUOUS_TABNAME - sapsql ambiguous tabname SAPSQL_AMBIGUOUS_FIELDNAME - sapsql ambiguous fieldname SAPSQL_ALIASNAME_TOO_LONG - sapsql aliasname too long SAPSQL_AGGREGATE_NOT_ALLOWED - sapsql aggregate not allowed SAPSQL_AGGREGATE_LOB - sapsql aggregate lob