on 03-02-2011 11:04 AM
Hello everyone,
this question might sound simple but I couldn't find any answer for it in SAP Marketplace, sdn, help.sap.com and the great, wide internet: when does the processed time in SM50 turn to red?
I found some information that it's managed by the rdisp/max_wprun_time parameter. But today I saw a red process in SM50 that had a runtime (approx. 370sec) much less than the configured parameter size (3600).
Many thanks for any help.
Best wishes
Marie Renneke
Correcting myself:
IF TIME > 300 AND WP_TABL_ALV-WP_ITYPE <> TH_BTC_WP.
TMP_FIELD_COL-FIELDNAME = 'WP_ELTIME'.
TMP_FIELD_COL-COLOR-COL = COL_NEGATIVE.
TMP_FIELD_COL-COLOR-INT = 0.
TMP_FIELD_COL-COLOR-INV = 0.
APPEND TMP_FIELD_COL TO WP_TABL_ALV-FIELD_COL.
ENDIF.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Never thought about looking at the source code of SM50... thanks Jan
Just a note: between WP_TABL_ALV-WP_ITYPE and TH_BTC_WP the not-equal brackets <> are missing .
So it seems there is really no way that the time column gets red when a BTC process runs for a long time.
Really weird...
Many thanks for all your replies!
Best
Marie
Well, nothing at all, it's hardcoded:
IF ( TIME > 600 ) AND
( WP_TABL-WP_ITYPE <> TH_BTC_WP ) AND
( WP_TABL-WP_IWAIT <> 9 ) .
WRITE: 55 wpinfo-wp_eltime COLOR COL_NEGATIVE.
ELSE.
WRITE: 55 wpinfo-wp_eltime COLOR = colour.
ENDIF.
MOVE WPINFO-WP_ELTIME TO GS_OUTPUT1-WP_ELTIME.
Best regards
Jan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
A redstatus (ERR) in a workprocess overview is indicated if it was cancelle/restarted.
To verify, Incase if you feel a situation(eg if cancelling a work process PRIV mode status if it demands) of cancelling a work process , then after cancellation/termination, the same work process is now has a red entry. These red entries gets accumulated as days go on and by the situation stated above.
Frequent cancellations have to checked w.r.t inadequate memory or any programs/data loads exhausing the systems, which needs to be taken care.
The entries will however be cleared (SM50 without red) when there is a SAP restart.
Hope this answers your query.
Regards,
munassar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Dialog processes exceed the time limit then sap system throw the sap dump to dialog user and set the number 1 in error(Dumps) column in SM50 t'codes. Error column show the errors or sump for work processes.
If Sap system admin kills particular process then it will also effect colum of Error.
Thanks,
Rahul S.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think it turns red if work process gets restarted becuase of an error
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The color of the field will change to red when the execution time of the workprocess exceeds 300 and the process type is not batch.
Nearly !
The color of the field will change to red when the ABAP execution time of the workprocess exceeds the value of parameter
rdisp/max_wprun_time (the default value is 300s ) and the process type is not batch.
From RZ11 help for rdisp/max_wprun_time :
This parameter limits the maximum runtime of a process step within
a dialog process. This ensures that dialog processes are not blocked
by programs with long runtimes which hinder online activity.
Often, the most time is required by a long-running SQL statement.
During processing, such SQL statements do not permit interruptions in
the database level. So that each time an SQL is successfully processed
the system is not interrupted, each process has a second chance, that
the maximum runtime is double the value of the parameter.
Regards,
Olivier
Hello again,
many thanks for the quick replies.
It is correct that the error column gets red when an error occured but I don't think that there is a relation to the time column.
300 sec. sounds appropriate for DIA processes. Do you also know the time when a BTC process time turns red?
Is there any kind of documentation about such things? Can these values be maintained somewhere?
Many thanks and best wishes
Marie
Hi Oliver,
this cannot really be right because first of all the default value of rdisp/max_wprun_time is 600 (ECC 6.0) and secondly the rdisp/max_wprun_time is set to 3600 in our system though the process time turns red when it's just 370sec or the like.
So 300sec. sounds more appropriate to me. But though I'd really like to know where this is set and documented.
Best
Marie
Hello,
yes I have - that's why I'm asking.
Our monitoring tool is maintained to show us longrunning BTC processes after 3h.
But there is no relation to the SAP warning in SM50.
I'm only asking because I'm just setting up some CCMS monitores for informing our customer when a Dialog process turns red. And I think that he'll be also interested in batch processes turning red after the implementation of the first step
And as far as I know there is no standard monitore for such an alert - that's why I'll maintain the alert for longrunning DIA-processes to 300sec turning red now.
Many many thanks for your help so far!
If anybody knows how long btc processes run before getting red in time column, please let me know.
Best wishes
Marie
Hello,
are you sure? Because I'm really sure I've already seen a red cell for BTC processes in time column - this is why I'm asking. It's been a really high runtime due to heavy performance problems - I couldn't reproduce this by now (fortunately ).
And this is not about the "error" column - my question regards the "time" column.
Best
Marie
Edited by: Marie Renneke on Mar 30, 2011 9:06 AM
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.