on 12-19-2008 5:46 AM
hi all
one of the functional consultant executing general ledger report in FICO he got time_out error.the error is
What happened?
The program "SAPLFAGL_DOCUMENT_RELATION" has exceeded the maximum permitted
runtime without
interruption and has therefore been terminated.
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
After a specific time, the program is terminated to make the work area
available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
time limit is
exceeded, the system attempts to cancel any running SQL statement or
signals the ABAP processor to stop the running program. Then the system
waits another 60 seconds maximum. If the program is then still active,
the work process is restarted.
to correct the error
Programs with long runtime should generally be started as background
jobs. If this is not possible, you can increase the system profile
parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
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:
"TIME_OUT" " "
"SAPLFAGL_DOCUMENT_RELATION" or "LFAGL_DOCUMENT_RELATIONU05"
"FAGL_GET_DOC_DETAILS_OF_LEDGER"
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.
i already increased dialogue workprocess time.but i got same error.how can i solve the problem
by
srinivas
hi vasu,
your current setting for rdisp/max_wprun_time is 600 seconds. That report which is run by your functional consultant is running more than 600 seconds. That's why it's being terminated by SAP.
You could change your SAP parameter rdisp/max_wprun_time to more than 600 seconds or just ask your functional consultant to run that report to background job, not dialog work process.
ardhian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
you need to look at the report in details and see where it taking time. Could be large selection on non-optimized database tables..
- check query selection ( large dataset fetching)
- check database statistics for GL tables
- check proper indexes for GL tables
- check DB buffer / Filesystem IO performance...etc..
Hi,
Time out error can occur if the report is taking too long to complete due to non optimal explain plan. Check the SQL statement explain plan if the best access path is taken. Post the explain plan together with the available indexes. And do ensure you have set all the database parameters correctly. Refer to Note 830576 if you are on Oracle 10.2.
Cheers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.