TSV_ILLEGAL_REFERENCE 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.
At the time of the termination, the content of the table reference was
as follows:
check : <runtime parameter>
index: <runtime parameter>
ShmId: <runtime parameter>
IsLockId: <runtime parameter>
To find the cause of the memory overwrite, you can try the following:
1) The structures before and after the corrupted table in the DATA
section are potential candiates for invalid access using ASSIGN.
2) In the ABAP Debugger, it is possible to set a watchpoint for the
administration data of an internal table. If the table is called ITAB
for example, you enter the field display ITAB[](8). The 8 byte
administration information is then displayed hexadecimally. You now
have to set a watchpoint for this field display and run the program. As
soon as this is overwritten, the ABAP Debugger stops.
The reference to an internal table is corrupt.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
This is probably an error in program <runtime parameter>. The administration data for
accessing the internal table was probably corrupted by a memory
overwrite. A memory overwrite of this kind is normally caused by one of
the following programming errors:
1) A dynamic ASSIGN whose offset and/or length specification was too
large, resulting in positioning beyond the end of the source field used
in the ASSIGN. Next time write access was made to the associated field
symbol, data was written beyond the borders of the source field.
2) A DO ... VARYING loop with incorrect step width or too large a
number of runs can also be positioned beyond the limits of the observed
structure and be overwritten.
3) Using the ASSIGN ... CASTING statement caused a memory area to be
interpreted with a different type and to be overwritten.
Please see abap error for more details about the possible cause of this runtime error and how it could be avoided.
The administration data for access to an internal table can no longer
be interpreted.