Here I am going to discuss some issue in ST03N data missing due to DST time switch. The issue is more known but the solution provided everywhere is very confusing and not very clear . The ST03N data is more important to client as well as for a Basis administrator to determine the system performance .
1. First check that the SAP standard job is running or not. SAP standard job name ,"SAP_COLLECTOR_FOR_PERFMONITOR" should be running with DDIC user in 000 client. The JOB should be scheduled with one hour interval. There is a SAP standard note 16083 describes the standard job that needs to be scheduled properly.
2. Next we need to check that the report SWNC_CONFIG_TIMEPROFILE , and then check that SWNC time profile , it should be calculate all hours separately.
Check the point , calculate all hours separately and execute. It will calculate your all hours separately.
The results should be look like this,
3. After a Daylight Savings Time change or Time-zone change, not all data is collected in ST03 anymore. You are also missing data in transaction
STAD.The root cause must be like ,The Operating System time and the SAP system time (especially in client 000) are not the same. Both the OS and the SAP system time (client 000) must both be correct and the same in order for the ST03 statistics to work correctly. For this issue , please do the step given below,
For doing this you must need to follow the SAP note 919538 , to enter the entry to see
This entry should be added in the table TTZDV , from SE16 . But before that make sure all the changes should be done in 000 client and the clientmust be open. To give the input in TTZDV table you need few details like below field. he database table TTZDV contains a list of variable summer time rules in column DSTRULE. The column YEARFROM contains a year number for every rule, saying in which year the rule applies. The columns MONTHFROM, WEEKDFROM, WEEKDCFROM, TIMEFROM, MONTHTO, WEEKDTO, WEEKDCTO, and TIMETO contain the month, week, day, and time for the beginning and end of summer time.Now you need to check the report TZCUSTHELP to check if everything is setup correctly. When you run the report (in client 000) you should see the line "System time zone seems to be correct".
The output of the report should be like this.When all time-zone settings have been corrected, allow the collector (job SAP_COLLECTOR_FOR_PERFMONITOR) to run for some time in order to collect and total the statistics again. A full run of all collector jobs is 24 hours.Finally, check if the full 24 hours of data for the last complete days are collected:Important:
Next
Phase is to check that the SWNCMONIINDEX table , in this table the AGR_TZONE should be equal to the time zone you set for the system.
that AGR_TZONE you need to check in STZBD transaction with summer time zone rule as well.
The time specified for the beginning of summer time in the tables TTZDF and TTZDV identifies the time when the clock is put forward by the summer
time difference when the winter time ends. The first second of summer time is the time you get when you add the summer time difference to the
specified time.
An composite SAP note is also there to find out the time zone related issue.
198411 - Current data and information about time zones
101726 - Incorrect times and time zone setting
Must
Remember: When you change all those settings in 000 client ,then you
should run the job SAP_COLLECTOR_FOR_PERFMONITOR atleat 24 hours to
collectthe data in correct time zone.
Thanks and Regards,
Basis Administrator
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
10 | |
9 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 |