SAPSQL_CANT_SET_STATEMENT_ID 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 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.
With every db_rsql2() call, a statement ID is included identifying the
current Open SQL statement.
This statement ID is provided by calling macro DB_SAP_STMTID(). This
macro reported an error.
Parameters of the failed macro call:
Program name: <runtime parameter>
Time stamp: <runtime parameter>
Statement number: <runtime parameter>
Pointer to statement ID: <runtime parameter>
Internal error: Statement ID cannot be set.
Please see internal error for more details about the possible cause of this runtime error and how it could be avoided.
Please see sapsql internal error 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_CANT_SET_STATEMENT_ID - sapsql cant set statement id SAPSQL_BOXED_NOT_SUPPORTED - sapsql boxed not supported SAPSQL_BOUND_LONG_STRING - sapsql bound long string SAPSQL_BETWEEN_MISSING_AND - sapsql between missing and SAPSQL_ARRAY_WRONG_ALIGNMENT - sapsql array wrong alignment SAPSQL_ARRAY_INSERT_DUPREC - sapsql array insert duprec