Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from R. N. Wilhite on Jan 12 at 9:19 AM As in, the calling program did not put in "SYSTEM_FAILURE" as one of its
handled conditions. What was the calling program? If it was standard,
look for OSS notes. If it was yours, then fix it...
Neal
| | | ---------------Original Message---------------
From: rakesh
Sent: Thursday, January 12, 2012 7:43 AM
Subject: Raise_Exception and System_Failure
Runtime Errors RAISE_EXCEPTION
Date and Time 11.01.2012 12:12:00
Error analysis
A RAISE statement in the program "SAPLOLEA" raised the exception
condition "SYSTEM_FAILURE".
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 occurs 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:
"RAISE_EXCEPTION" " "
"SAPLOLEA" or "LOLEAU10"
"AC_FLUSH_CALL_INTERNAL"
or
"SAPLOLEA" "SYSTEM_FAILURE"
or
"SDV_VIEWER " "SYSTEM_FAILURE"
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)". |
| Reply to this email to post your response. __.____._ |   _.____.__ |
