cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in setting a Model Attribute of type Time

Former Member
0 Kudos

Hi,

I have two model attributes of type time(I mean corresponding structure R/3 fields are of type time).

I do

wdContext.currentModel1().setTime(wdContext.currentModel2.getTime);

Till yesterday, this was working fine.

Today it assigns a "time+GMT Offset" to the Model1 timefield. (Yesterday it Model1.getTime gave 15:30:00

Today its gives 23:30:00, I am in Singapore 8+ time zone).

Any ideas why this is happening. And any solutions to prevent this. Also what are the places where we need to correct the time zones if any?

Regards,

Shubham

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

Jus a suggestion.. set your local pc time to GMT...and check the session locale.,.,.

<b>Did u try this suggestion ? :)</b>

Message was edited by: Bharathwaj R

Former Member
0 Kudos

I believe you are retrieving time from the R/3. I feel that some one has made changes in the R/3.

Please check

Former Member
0 Kudos

Yes I am retrieving time from R/3, but when I check Model2.getTime() in Debugger in WebDynpro, it still shows 15:30:00

Any more ideas?

Regards,

Shubham

Former Member
0 Kudos

Hi,

How are u checking tat the value is 23.00.00?

Did u check the result in R/3 after executing model1..

Former Member
0 Kudos

Hi Bharathwaj,

I have debugging activated both in WebDynpro and R/3. Both places time is 23:30:00 after copy from model2 attribute that has 15:30:00

I will try to use your first suggestion.

Any ideas, time attribute in Context is depenedent on local PC or on the Server?

Regards,

Shubham

Former Member
0 Kudos

Hi,

Local PC ! (Thank god .. there are no negative points for wrong answers ! )