09-09-2010 3:28 PM
Dear SAP friends,
We encountering, quite often, run time error "BIF_RSQL_INVALID_RSQL"
Possible errors:
o The maximum size of an SQL statement has been exceeded.
o The statement contains too many input variables.
o The space needed for the input data exceeds the available memory.
o ...
From the ST22 I found that the user has inputed 7869 specific delivery numbers at the multiple selection (probably with a copy from clipboard. ( SP$00011[] Table IT_76[7869x46]).
Is there anywhere documented, that there is a limitation up to how many values can a multiple selection can handle?
Or it there a logic to use in order to guide the end users, of how to fill in the multiple selection?
Thanks in advance for yr support.
BR,
Elly Leondi
09-09-2010 3:50 PM
Hello Elly,
You're getting this error because maximum length of SQL statement has exceeded. These notes might throw some insight:
1. Note 13607 - Termination of an ABAP with DBIF_RSQL_INVALID_RSQL
2. Note 1002491 - Maximum length of SQL statements in R/3
3. Note 635318 - Open SQL: Size restrictions for commands
BR,
Suhas
09-09-2010 3:33 PM
Is this a standard? this happens when the select option has many entries and when its used with in statement query.
09-09-2010 3:50 PM
Hello Elly,
You're getting this error because maximum length of SQL statement has exceeded. These notes might throw some insight:
1. Note 13607 - Termination of an ABAP with DBIF_RSQL_INVALID_RSQL
2. Note 1002491 - Maximum length of SQL statements in R/3
3. Note 635318 - Open SQL: Size restrictions for commands
BR,
Suhas
09-09-2010 3:51 PM
We normally get his kind of error, if we give more than 5000 records in the selection screen.
09-09-2010 3:59 PM
This is being asked occasionally (please search for "DBIF_RSQL_INVALID_RSQL" before posting), a limit in terms of number of entries cannot be given, as the limit is in KBytes, see the notes referenced by Suhas.
Depending on the length of the selection field we are talking about a few thousand single entries.
Ask your users to split the selection into smaller chunks. If it is a custom program, and mass selection by single values is the norm, you can look into using FOR ALL ENTRIES instead of a range in the SQL query.
Thomas
09-10-2010 7:51 AM
Thomas,
Thnk you fr yr reply, it was very helpful.
Unfortunately I searched only at SDN and missed to see ......... the STD SAP notes. ... my mistake. Sorry for that.
Suhas,
Yr reply was what I needed, thanks again a lot.
BR,
Elly