ABAP Runtime Errors

TABLE_INVALID_INDEX SAP ABAP Runtime Error table invalid index







TABLE_INVALID_INDEX 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.


TABLE_INVALID_INDEX ABAP Runtime Error

Please see abap 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.

Error in ABAP statement while processing an internal table. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.

When changing or deleting one or more rows in internal table <runtime parameter>-NAME or when inserting rows into table <runtime parameter>-NAME, <runtime parameter> was used as the row index. An index less than or equal to zero is not allowed.

The error can occur when using the following additions:
1. "INDEX idx" for specifying the row number in table <runtime parameter>-NAME where the row is to be changed, inserted or deleted.
2. "FROM idx" for specifying the start index when deleting a row area from or inserting a row area into table <runtime parameter>-NAME.
3. "TO idx" for specifying the end index when deleting a row area from or inserting a row area into table <runtime parameter>-NAME.

When the program terminated, the table contained <runtime parameter>-FILL rows. Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.