5/10/2015

ST03commonissuesxtimezoneinconsistencies|SCN

GettingStarted Newsletters

Hi,Guest

LogOn

JoinUs

Store

SearchtheCommunity

Products

Services&Support

AboutSCN

Downloads

Industries

Training&Education

Partnership

DeveloperCenter

Activity

LinesofBusiness

UniversityAlliances

Events&Webinars

Innovation

Browse

Communications

Actions

SAPNetWeaverAdministrator

ST03commonissuesxtimezoneinconsistencies
PostedbyIanSegobioinSAPNetWeaverAdministratoronMay8,20158:03:26PM
Share

Tweet

4 Like

Helloguys,

ProblemsrelatedtothelackofdatainST03duetimezoneincorrectsettingsarehighly
recurrent.ImeanHIGHLY.Therootcauseforthosewrongsettingsare,inthemajorityof
thetimes,relatedtotwoscenarios:

>WrongtimezonesettingsatSAPlevel(transactionsSTZBC,STZAC,etc...)

>MismatchbetweenthetimezoneusedbytheOSlevelandSAPsystem.

ThereisaprocedurethatIoftenuseto"navigate"throughthepossibilitiesandfindout
whetheratimezoneissueexistsand,incaseitdoes,whereit'slocated.Itisfairlysimple
andhashelpedforinseveraloccasionswhileworkingwithrelatedscenarios.

Theflowofthetroubleshooting/decisionmakingfollowthesesteps,startingwiththe
symptomsseeatST03:

ST03doesnotreportdata/doesnotreportcurrentdata(lasttwodays)/ST03seems
odd...

Inordertoconfirmorruleoutatimezoneissueastherootcausefortheabovetopic,the
firstthigtodoisgotoSTADtransactionandrunitwiththedefaultsettings.Justgetintoit
andexecute:

http://scn.sap.com/community/netweaveradministrator/blog/2015/05/08/st03commonissuesxtimezoneinconsistencies

1/5

5/10/2015

ST03commonissuesxtimezoneinconsistencies|SCN

IncaseSTADdoesnotreportanydatawhatsoever,thenwemostlikelyhaveawinner.In
caseworkloaddataisreturned,thentheissueshouldbeapproachedthorughdifferent
ways.Wefollowassumingthatnothingreturnedtothequery.

TheverynextthingtodoistocheckOSleveltimezonesettingsandcrossitwithR/3
level(client000).Theprocedurevarydependingontheoperatingsystembutonunix
platforms,thecommand"date"willbringthedesiredinformation.Forwindows,
"systeminfo":

UNIX:

WINDOWS:

ThenyoucrossthatinformationwithR/3level(client000),transactionSTZAC.Thesame
timezonenamemustbeseenthere.TheSAPsystemusedforthisanalysisishostedata
linuxserver(above)sotheOFFSETsarematching.

Thatwastheeasiestchecktodo.Nowcomesthetrickypart,whichweapproachincase
theoutputspresentcorrectsettingsbutevensoST03andSTADarepresentingissues.

Firstweneedtounderstandthethesystemhasitsowntimezonebutusershaveitas
well.Usertimezonecanbethesameasthesystem's(forcasesinwhichbotharelocated
atthesameregion)ordifferent(likeseenabove)whereserverislocatedatoneplaceand
http://scn.sap.com/community/netweaveradministrator/blog/2015/05/08/st03commonissuesxtimezoneinconsistencies

2/5

5/10/2015

ST03commonissuesxtimezoneinconsistencies|SCN

usersinanother.Weareusingthatfeatureinouradvantageinthisanalysis.
FortheaboveSTZACsituation,thewouldbetheexpectedoutputforSYSTEM>STATUS
menu:

The"Systemtime"fieldwillpresentthetimezonefromthesystemitselfandthe"Time
Zone"issuewillreportthetimezone*ONLYINCASE*theuserhaveadifferentthanthe
system.Ifbothhavethesametimezoneset,thefieldTimeZonewillnotappearatall.

Nowherestartsthe"trick"...Wheneverfacingtimezoneissuesonyoursystem,you'll
noticethattheextra"Timezone"fieldwillbethere,andwe'lluseitinouradvantagein
thisanalysis.

Assoonasyouknowwhatisthedefaulttimezonebeingusedbythesystem(transaction
STZAC,client000)yougoto:enu

>Menusystem>Userprofile>Owndata.Then,youchangetotab"Defaults"

InsideoftheDefaultstab,we'lllookforthesection"PersonalTimeZone",wherethe
currentusertimezonesettingscanbechanged.Firstthingtocheckiswhetherthesame
isbeingused.Incaseitsnotsetatall(assumingthesystemtimezone)orsettoanother
value,pleasesetittothesamevalue:

http://scn.sap.com/community/netweaveradministrator/blog/2015/05/08/st03commonissuesxtimezoneinconsistencies

3/5

5/10/2015

ST03commonissuesxtimezoneinconsistencies|SCN

Afterthat,youhavetosavethechanges,logoutandinagain.Assoonasyoulogin
again,youneedtocheckmenu"System>Status"onemoretime.Mostlikelyyou'llsee
somethinglikethis:

Abovewecanseethatevenusingtheverysametimezoneasthesystem,theoutputstill
showsonehourdifference.Nowwhatwehavetodoitschangetheusertimezone
settingsagainand,insteadofCET(whichshouldbeequivalentforUTC+0100)usethe
OFFSETdirectlyinthefield.WealreadyknowthattheOFFSETisnotproperlyequivalent
toUTC+0100asitshould,becauseifitwere,theextrafield"Timezone"wouldnotappear
at"System>status"menu.

FinallyyoujusthavetotryanotherUTCOFFSET,letsSAY"UTC+0200"inthefield,log
outandloginagainuntilthe"Timezone"filedceasestoappearat"System>status"
menu.ThenyoucanfinallyaccessSTZBCtransactionandcheckwhythetimezoneset
forthesystem(inthiscaseCET)isnotbehavingcorrectlyasUTC+0100butas
UTC+0200insted.

Thisproceduremightappearcomplicatedforfirsttimersbut,intime,you'llgetthehangof
it.Icanassure
Cheers,
IanSegbio.

209Views

AverageUserRating

http://scn.sap.com/community/netweaveradministrator/blog/2015/05/08/st03commonissuesxtimezoneinconsistencies

4/5

5/10/2015

ST03commonissuesxtimezoneinconsistencies|SCN

(0ratings)

Share

Tweet

4 Like

0Comments
Therearenocommentsonthispost

SiteIndex
Privacy

ContactUs
TermsofUse

SAPHelpPortal
LegalDisclosure

Copyright

http://scn.sap.com/community/netweaveradministrator/blog/2015/05/08/st03commonissuesxtimezoneinconsistencies

FollowSCN

5/5