SAPSQL_STMNT_TOO_LARGE SAP ABAP Runtime Error sapsql stmnt too large

SAPSQL_STMNT_TOO_LARGE 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: A - ABAP Programming 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.

SAPSQL_STMNT_TOO_LARGE ABAP Runtime Error

Please see sapsql internal error 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.

The memory area where the comparison values from the WHERE, ON and HAVING clause are stored is restricted to 64 MB. Depending on the system configuration, this means that upwards of 130,000 comparisons can be stored there.
There is no sense in increasing this limit, as none of the database systems currently supported by SAP could process a statement anything like this big. The Open SQL command is too big. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

Size restriction violated for SQL commands.
The reason for this could be one of the following, depending on the database system in use:.
- The statement text is too long
- The statement contains too many words
- The statement contains too many conditions
- The statement contains too many comparison values
- Taken together, the specified comparison values require more than 64 MB of memory.
Errors like this usually occur if the ON-, WHERE- or HAVING clause has at least one IN condition with an internal table (RANGE table, SELECT OPTION) that contains too many entries. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.