DB_ERR_RSQL_00013 SAP ABAP Runtime Error db err rsql 00013

DB_ERR_RSQL_00013 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: & - Text Include (no Short Dump, only Text Module)

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.

DB_ERR_RSQL_00013 ABAP Runtime Error

The SAP Open SQL statement in question must be split into multiple statements.
If the problem was caused by using an oversized table in an IN [range tab] construct, the usage of the FOR ALL ENTRIES addition may be displayed instead.
If this addition is used, the statement is divided into suitably sized portions in accordance with the restrictions that apply in the relevant database system. Please see send to abap for more details about the possible cause of this runtime error and how it could be avoided.

Please see internal call code for more details about the possible cause of this runtime error and how it could be avoided.

An SQL statement violates restrictions imposed by the database system. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

The SQL statement generated from the SAP Open SQL statement violates a restriction imposed by the database system that ABAP system is based on.

Possible causes of error:
o The maximum size of an SQL statement has been exceeded. o The statement contains too many input variables.
o The memory requirement of the input data exeeds the existing memory.
o ...

You can usually find details in the system log (SM21) and in the developer trace of the corresponding work process (ST11).
If errors occur, the developer trace often displays the restrictions currently in force. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.