EXSQL_VARIABLE_TOO_BIG 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.
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.
A variable in a Native SQL command is bigger than 64 KB.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
A data object is larger than 64 KB, or an internal table is wider than
64 KB.
1. The length of a data object in a Native SQL command must not exceed
64 KB.
This situation only occurs if a large type C field (larger than 32767
characters) is used in a Unicode system.
2. If an internal table is used in a Native SQL command, the defined
width of the table must not exceed 64 KB.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
EXSQL_VARIABLE_TOO_BIG - exsql variable too big EXSQL_UNSTRUCTURED_INTO - exsql unstructured into EXSQL_UNKNOWN_CONNECTION - exsql unknown connection EXSQL_TOO_MANY_VARS - exsql too many vars EXSQL_ILLEGAL_DISCONNECTION - exsql illegal disconnection EXSQL_ILLEGAL_CONNECTION - exsql illegal connection