Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Run time error invalid_table_index

Former Member
0 Likes
857

Hi,

below program I am getting dump when running background in production. The yarrow mark showing exactly the PERFORM trace_change .Can some body help me I think modify commmand only creating dump where index is zero..need help

What I got from dump[:

Short text Error in ABAP/4 statement when processing an internal table.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLVED4" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

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

\PROGRAM=RBDAPP01\DATA=DOCNUM[] or when inserting in the table

"\PROGRAM=RBDAPP01\DATA=DOCNUM[]", 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=RBDAPP01\DATA=DOCNUM[]"

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=RBDAPP01\DATA=DOCNUM[]".

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

area from or inserting a line area into the table

"\PROGRAM=RBDAPP01\DATA=DOCNUM[]".

At the time of the termination, the table contained 0 lines.

How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

TABLE_INVALID_INDEX " "

SAPLVED4 or "ZUEXIT01"

INCREASE_CUMS_RECEIVED

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

*********************************************************************************************************

WRITE vblb-abefz TO abefz. "NO-SIGN.

READ TABLE xidoc

WITH KEY segnam = 'E1EDP10'.

tmp_e1edp10 = xidoc-sdata.

tmp_e1edp10-akuem = abefz.

xidoc-sdata = tmp_e1edp10.

MODIFY xidoc

INDEX sy-tabix.

PERFORM trace_change USING 'AKUEM'

space

abefz

'Rule 5.1: No Cml.qty received sent by Customer.'.

ENDFORM. " INCREASE_CUMS_RECEIVED

Hi,

below program I am getting dump when running background in production. The yarrow mark showing exactly the PERFORM trace_change .Can some body help me I think modify commmand only creating dump where index is zero..need help

What I got from dump[:

Short text Error in ABAP/4 statement when processing an internal table.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLVED4" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

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

\PROGRAM=RBDAPP01\DATA=DOCNUM[] or when inserting in the table

"\PROGRAM=RBDAPP01\DATA=DOCNUM[]", 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=RBDAPP01\DATA=DOCNUM[]"

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=RBDAPP01\DATA=DOCNUM[]".

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

area from or inserting a line area into the table

"\PROGRAM=RBDAPP01\DATA=DOCNUM[]".

At the time of the termination, the table contained 0 lines.

How to correct the error

If the error occurred in your own ABAP program or in an SAP

program you modified, try to remove the error.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

TABLE_INVALID_INDEX " "

SAPLVED4 or "ZUEXIT01"

INCREASE_CUMS_RECEIVED

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

*********************************************************************************************************

WRITE vblb-abefz TO abefz. "NO-SIGN.

READ TABLE xidoc

WITH KEY segnam = 'E1EDP10'.

tmp_e1edp10 = xidoc-sdata.

tmp_e1edp10-akuem = abefz.

xidoc-sdata = tmp_e1edp10.

MODIFY xidoc

INDEX sy-tabix.

PERFORM trace_change USING 'AKUEM'

space

abefz

'Rule 5.1: No Cml.qty received sent by Customer.'.

ENDFORM. " INCREASE_CUMS_RECEIVED

2 REPLIES 2
Read only

Former Member
0 Likes
650

Hi

Put a Sy-SUBRC check after your READ statement to check whether you got the right record in your internal table before using MODIFY.


WRITE vblb-abefz TO abefz. "NO-SIGN.

READ TABLE xidoc
WITH KEY segnam = 'E1EDP10'.
if sy-subrc = 0.                                    " Added the line
tmp_e1edp10 = xidoc-sdata.
tmp_e1edp10-akuem = abefz.
xidoc-sdata = tmp_e1edp10.

MODIFY xidoc
INDEX sy-tabix.
endif.                                                   " Added the line
PERFORM trace_change USING 'AKUEM'
space
abefz
'Rule 5.1: No Cml.qty received sent by Customer.'.
ENDFORM. " INCREASE_CUMS_RECEIVED

Regards

Ranganath

Read only

Former Member
0 Likes
650

This message was moderated.