cancel
Showing results for 
Search instead for 
Did you mean: 

Chaning to UTC timezone

Former Member
0 Kudos

Hello,

I want to configure all our systems time zone to UTC to avoid daylight saving time switching. Just wondering if anyone have experience with that. Any issues encountered.

It would be great if anyone can share their experiences and steps that they took to configure it and test it.

Thanks

Accepted Solutions (0)

Answers (5)

Answers (5)

farkathulla_cikkanther
Active Participant
0 Kudos

Hello Bill,

    We have changed Our System time zone from CET to UTC-5, We dint face any issues and even we dint restart the system, The changes has take effect immediately. As per our experience...

Regards,

Farkath C

Former Member
0 Kudos

I guess, I just want to know if anyone encountered any issues in their SAP systems for e.g problems in time stamps in running some reports etc..

Any precautions to take?

0 Kudos

Hi Bill,

did you experience any issues after changing the time zone to UTC?

We currently planing the same in order to avoid DST switches.

In particular, do you make any application-related-changes for e.g. FI/MM scenarios?

See http://help.sap.com/saphelp_nw70ehp2/helpdata/en/2b/7ccd58129911d3952c0000e83dcfd4/content.htm?frame...

Have activated time-zone functionality for user depended time zones?

Thanks for your input.

Regards, Christoph

0 Kudos

Hi Bill,

Based on your descriptions. I suppose changing time zone from CET to UTC

is still at planning phase. Therefore, the data disply issue for Tcode

"ST03N and STAD" is not occuring at your PI7.1 system at the moment.

From system monitoring point of view, the key to avoide such issue

discussed with note 926290 is that

"

the system time zones (operating system and R/3) must have the same

offset for UTC.

"

In other words, given that your operating system is running at UTC, you

should change the SAP system time zone to UTC as well, as these two

time zones should be always in synch.

Actually I could not commend for other areas. But I try to provide some

info based on other customers experience, just for your reference.

Before changing the SAP system time zone please consider the

following points:

- As the change from CET to UTC implies a step back in time (CET is

  two hours ahead of UTC), there is some risk of 'duplicate times'

  in the SAP system.

- It is strongly recommend to ensure that the SAP system is not used by

  business after the change of SAP system for at least 2 hours to

  ensure that the system is not used during the 'duplicated time'.

- It is recommend to restart the SAP system after the changes so that

  buffing of old time zone settings is avoided.

Thank You.

Regards,

Deepika

DavidLY
Advisor
Advisor
0 Kudos

Hi Bill,

For the impact after changing system time zone:

Please be aware that changes in time zone settings always requires a system restart. The R/3 system time zone is only used in very rare cases. Nevertheless I would strongly recommend not to start any jobs or time critical processes during this time period.

When you change the time zone settings on R/3 system the time saved on database will not be recalculated. Nevertheless some documents might display another time because the calculation then starts with the creation time on database and the 'new' system time e.g.'CET'. But this should not cause any inconsistencies. But as mentioned we would recommend to avoid the creation of documents in the time period.

Regards,

David

Former Member
0 Kudos

Hello ,

U can follow following procedure to maintain your time zone :

1. Open the client where you are doing the changes (from both SCC4 and SE06), though it will affect all the client .

2. go in STZAC / SPRO-SAP Netweaver -Time Zone-maintain system setting and change the time setting

3. It will ask for transport request which you can use in other system (QUA/PRD) in your landscape.

Thanks ,

Sayan

Former Member
0 Kudos

Hi ,

U can use T-code STZAC to set the time zones

Regards

Deepak

Former Member
0 Kudos

Check note 101726 to configure timezone.