CHECK_SELOPT_ILLEGAL_OPTION 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.
If <runtime parameter>-NAME was actually filled in the program, the corresponding ABAP
code needs to be corrected.
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.
Incorrect OPTION in SELECT-OPTIONS or RANGES table.
Restart the program and note the following guidelines:
If you made selection options for filling table <runtime parameter>-NAME, some of these
are probably illegal.
Only the following selections are allowed:
"EQ", "BT", "LE", "GE", "CP", "NE", "NB", "GT", "LT", "NP".
Otherwise:
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
An attempt was made to run a CHECK on internal table <runtime parameter>-NAME, which
was created with SELECT-OPTIONS or RANGES. The table contained a row
with the illegal value <runtime parameter> for field <runtime parameter>-NAME-OPTION however.
Only the following values are allowed for this field:
"EQ", "BT", "LE", "GE", "CP", "NE", "NB", "GT", "LT", "NP".
The error might have occurred because the table was filled in the
program instead of by user input on the selection screen for program
<runtime parameter>.
There are several possibilities:
End user error
You have made an entry that is not accepted by the program or system.
The selection options that you have made for a selection screen might
be incorrect.
Or:
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.