ITAB_ILLEGAL_INDEX_OP 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 program correction 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.
Index used to access a HASHED key.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
An index was used to access table <runtime parameter>. Key <runtime parameter> was used for this
access.
This key is of type HASHED however. Index operations are not permitted
on HASHED keys.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
ITAB_ILLEGAL_INDEX_OP - itab illegal index op ITAB_ILLEGAL_COMPONENT - itab illegal component ITAB_ILLEGAL_BINARY_SEARCH - itab illegal binary search ITAB_DYN_KEY_ILLEGAL_COMPONENT - itab dyn key illegal component ITAB_DYN_KEY_ID_MAX_EXCEEDED - itab dyn key id max exceeded ITAB_DUPLICATE_KEY_IDX_OP - itab duplicate key idx op