Skip to Content
author's profile photo Former Member
Former Member

ABAP Dump TABLE_INVALID_INDEX

Hi all,

I would like to know what this error is all about ?

Runtime Errors TABLE_INVALID_INDEX

Occurred on 04.01.2007 at 00:28:59

Error in ABAP statement when processing an internal table.

What happened?

Error in ABAP application program.

The current ABAP program "SAPMYM015" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

When changing or deleting one or more lines of the internal table

"PROGRAM=SAPMYM015DATA=T_MTD[]" or when inserting in the table

"PROGRAM=SAPMYM015DATA=T_MTD[]", 0 was used as

the line index. An index less than or equal to zero is not

allowed.

The error can occur when using the following options:

1. "INDEX idx" for specifying the line number in the table

"PROGRAM=SAPMYM015DATA=T_MTD[]"

where you want to change, insert or delete.

2. "FROM idx" for specifying the start index when deleting a line

area from or inserting a line area into the table

"PROGRAM=SAPMYM015DATA=T_MTD[]".

3. "TO idx" for specifying the end index when deleting a line

area from or inserting a line area into the table

"PROGRAM=SAPMYM015DATA=T_MTD[]".

When the program terminated, the table had 2 lines.

How to correct the error

If the error occurred in one of your own programs or in an SAP program

that you modified, try to correct it yourself.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"TABLE_INVALID_INDEX" C

"SAPMYM015" or "MYM015F01"

"FCODE_DELETE_ROW"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

SAP Release.............. "620"

Application server....... "r3pap2"

Network address.......... "172.16.14.17"

Operating system......... "AIX"

Release.................. "5.2"

Hardware type............ "000B422F4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 3

Short dump setting....... "full"

Database server.......... "r3db"

Database type............ "ORACLE"

Database name............ "PRD"

Database owner........... "SAPR3"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "640"

Created on............... "Jul 4 2005 21:10:18"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "80"

Patch text............... " "

Supported environment....

Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE

10.1.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"

User, transaction...

Client.............. 999

User................ "AKDTE37"

Language key........ "E"

Transaction......... "YMFG25 "

Program............. "SAPMYM015"

Screen.............. "SAPMYM015 9001"

Screen line......... 94

Information on where termination occurred

The termination occurred in the ABAP program "SAPMYM015" in "FCODE_DELETE_ROW".

The main program was "SAPMYM015 ".

The termination occurred in line 209 of the source code of the (Include)

program "MYM015F01"

of the source code of program "MYM015F01" (when calling the editor 2090).

Source code extract

001790 *-BEGIN OF LOCAL DATA *

001800 data l_table_name like feld-name.

001810 data l_no type i.

001820

001830 field-symbols 2nd level extension part <<<<<

tabhBack = Not allocated

delta_head = Not allocated

pb_func = Not allocated

pb_handle = Not allocated

Directory of Application Tables

Program

Name................ Contents....1........2........3........4........5....+.. ..

SAPMYM015

SYST 00000000000x04000x0200000000000

RSJOBINFO 00000000000000

AUFK 999000122002250PD0110 AKDTE33 20060822AKDTE

PA0003 99900035929 999912311800010100020061226BALRFC

SAPSHDTV

SHDSTU

SHDSTCIU

CL_GUI_PROPS_CONSUMER=========CP

EUDB %C00084000459B02283CAF006A00000000AC100E11 0000

SAPLSCA5

TFACD Z11997201211111100Z100000 SAP_AG 20061225105847X00000

SAPLYMFG_PP

CRHD 999A 10004377200304039999123120030613SSVAIDYA 20030403D

JEST 000

T100C

Directory of Application Tables (Administrative Information)

Program

Name.......................... Time.......... Length.. .

SAPLYMFG_PP

SYST 00002404

RSJOBINFO 00000084

AUFK 00000748

PA0003 00000222

SAPSHDTV

SHDSTU 00000053

SHDSTCIU 00000050

CL_GUI_PROPS_CONSUMER=========CP

EUDB 00003940

SAPLSCA5

TFACD 00000061

SAPLYMFG_PP

CRHD 00000522

JEST 00000034

T100C 00000040

ABAP control blocks CONT

Include Line source code

Index Name F1 Co Par01 Par2. Par3. Par4. Tabl

MYM01 5 F01 193 concatenate p_table_name '[]'

3299 COND 03

3300 PAR1 82

3301 PAR1 82

3302 PAR1 83

MYM015F01 194 assign (l_table_name) to -lines = w_loopc.

3324 mvqw 04 00 0038

MYM015F01 211 cur_flag = 'X'.

3326 mlq1 01 0058

MYM015F01 220 endform. " FCODE_DELETE_ROW

3328 ENDF 00

3329

MYM015 F01 230 form compute_scrolling_in_tc u

3330 PERP 00

3331 PERP 00

3332 PERP 00

End of runtime analysis

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Jan 04, 2007 at 05:49 AM

    hi raj,

    try puttin in the search string TABLE_INVALID_INDEX at the below location.

    https://websmp101.sap-ag.de/notes

    this serach would provide u a wide variety of notes on this topic. read them and check if any thing suits for your requirement.

    Br,

    sri

    award points for helpful answers

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 04, 2007 at 12:36 PM

    Hi ,

    Could you please run DB Stat.

    Regards

    Ben

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 25, 2014 at 10:47 AM

    Hi there,

    I received this issue because I changed the ABAP routine on one of the rules of an Infopackage of the Export Datasource of an DSO. I changed the ABAP routine on the rule and afterwards the data loaded again to the PSA and target Infocubes.

    Therefor check the infopackage. I wish you all the best with this information.

    Regards,

    Michel

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 01 at 02:03 PM

    Hi

    We had a similar problem the issue is you are using ZERO for your SY-INDEX. Check the contents of system fields.

    Contents of system fields

    Name Val. SY-SUBRC 4

    SY-INDEX 0

    SY-TABIX 0

    SY-DBCNT 1

    SY-FDPOS 0

    SY-LSIND 0

    SY-PAGNO 0

    SY-LINNO 1

    SY-COLNO 1

    PROGRAM=SAPMYM015DATA=T_MTD[]", 0 was used as

    the line index. An index less than or equal to zero is not

    allowed.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.