SAPSQL_SQLS_INVALID_CURSOR 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.
Cursor already closed or not yet open.
a cursor that has already been closed or not yet been opened.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The cursor used in a FETCH or CLOSE CURSOR command is
not open. It was either not yet open or has already
been closed. You can close the cursor explicitly with
the CLOSE CURSOR command, implicitly with the COMMIT WORK command,
or with a screen change.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
SAPSQL_SQLS_INVALID_CURSOR - sapsql sqls invalid cursor SAPSQL_SQLS_INVALID_CONNECTION - sapsql sqls invalid connection SAPSQL_SQLS_ILLEGAL_CODE - sapsql sqls illegal code SAPSQL_SET_UNKNOWN_OPERATOR - sapsql set unknown operator SAPSQL_SET_QUOTES - sapsql set quotes SAPSQL_SET_PLUS_MINUS_TYPE - sapsql set plus minus type