Hi Gurus
One of my user is getting following dump while uploading the data.
"TSV_ILLEGAL_REFERENCE"
could you plz tell me what could be the reason n how to resolve?
=========================================================================
Runtime Errors TSV_ILLEGAL_REFERENCE Date and Time 07.04.2009 11:00:23
Short text
The reference to an internal table is destroyed.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLBUBA_4" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The administration data for the access to an internal table can no
longer be interpreted.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
This is probably an erro in program "SAPLBUBA_4". The administration data for
accessing an internal table was probably destroyed by a memory
overwriter. Such a memory overwriter is usually caused by one of the
following programming errors:
1) A dynamic ASSIGN with too great an offset and/or length specification
was positioned beyond the end of the source field used in the ASSIGN.
In the next write access to the corresponding field symbol, the
system wrote past the limitis of the source field.
2) A DO ... VARYING loop with an incorrect increment or too large a
number of passes can also be positioned beyond the limits of the
structure and be overwritten.
3) In using the statement ASSIGN ... CASTING a memory area was
interpreted with a different type and consequently overwritten.
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"TSV_ILLEGAL_REFERENCE" " "
"SAPLBUBA_4" or "LBUBA_4U02"
"BUPA_ADDRESS_CHANGE"
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)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "SFAQAAPP"
Network address...... "10.16.36.27"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 17
Shortdump setting.... "full"
Database server... "sfadatabase"
Database type..... "ORACLE"
Database name..... "PQC"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Nov 21 2008 01:03:37"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 185
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 243550600
Heap.... 0
Page.... 32768
MM Used. 4294967295
MM Free. 4294967295
=========================================================================
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.