‎2008 Dec 09 8:31 AM
Hi,
I am using following abap stactement to create the timestamp from date, time and timezone.
CONVERT DATE <dat> TIME <tim>
INTO TIME STAMP <time_stamp> TIME ZONE <tz>.
Here timezone is UTC.
today i found that, if time is equal to 24:00:00(240000) then irerespective of date the generated timestamp will be equal to 0.
I am not able to figure it out what is wrong with time 24:00:00
is it expected behaviour and if yes then what is the rationale behind this.
Thanks,
Rahul
‎2008 Dec 09 8:40 AM
hi,
The clock resets to 00000 at 2400 hrs.
Normally in international nomenclature, 12:00 am is denoted as 24:00 hrs or 00:00 hrs
Both are correct.
Hope this helps,
Rajat
‎2008 Dec 09 8:40 AM
Hi Rahul,
Why r u giving 24:00:00.. after 23:59:59 it shld be 00:00:00. Is there a need for 24:00:00.
Thanks
Mohan
‎2008 Dec 09 8:50 AM
‎2008 Dec 09 8:50 AM
User can enter 24:00:00 in time field. Framework doesn't report any error on 24:00:00.
Even if we give time equal to 00:00:00 then also timestamp get created successfully.
But if we give time equal to space then generated timestamp is equal to 0, which is similar to 24:00:00
Thanks,
Rahul
‎2008 Dec 09 8:54 AM
You can restrict it through the User Input validation..
Thanks
Mohan.
‎2008 Dec 09 9:18 AM
I found that in Window timefield you can not enter 24:00:00 as time not even in Nokia mobile
is there any way other then restricting user from entring the wrong time?
thanks,
Rahul
‎2008 Dec 09 9:20 AM
data: ccu_timestamp1 like CCUPEAKA-TIMESTAMP
The statement above means that ccu_timstamp1 is like field TIMESTAMP in
table CCUPEAKA.In this table timestamp is defined as NUMC14