SAPSQL_FETCH_WA_INCOMPATIBLE 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.
For all FETCH commands: Always use areas for a cursor that have the same
length and the same type.
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 INTO area has an incorrect length or type.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
At a further FETCH command, an area was specified in the INTO clause
that has a differing type or length as the preceding FETCH command for
the same cursor.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_FETCH_WA_INCOMPATIBLE - sapsql fetch wa incompatible SAPSQL_FETCH_RSQL_STACK_EMPTY - sapsql fetch rsql stack empty SAPSQL_ESCAPE_WITH_POOLTABLE - sapsql escape with pooltable SAPSQL_EMPTY_TABNAME - sapsql empty tabname SAPSQL_DYN_JOIN_WITH_STRING - sapsql dyn join with string SAPSQL_DUPLICATE_TABLENAME - sapsql duplicate tablename