Abap Dump RAISE_EXCEPTION
When I executive any Report Painter via GRR3 T-CODE . This dump comes RAISE_EXCEPTION "
Exception condition "PROGRAM_NON_EXISTENT" raised.
The current ABAP/4 program encountered an unexpected
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
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.
A RAISE statement in the program "SAPLSLDB" raised the exception
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct 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
"RAISE_EXCEPTION" " "
"SAPLSLDB" or "LSLDBU15"
"SAPMKES1 " "PROGRAM_NON_EXISTENT"
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
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
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
4. Details about the conditions under which the error occurred or which
Why this dump is comming . Plz help
Take the help of your ABAP developers to find out the reason why the dump is coming. They might be able to give the right direction to approach.
It looks like program SAPLSLDB is calling some other program which might not exist. if you can't find any standard note for the error, post the log as described in a customer message to SAP.