But in the 7.02/7.30-7.40-7.50 Release line, timestamps are stored in type p numbers: In another ABAP world, in NGAP, that is Release 8.x, in fact they have and we wouldn’t have to bother. Timestamps don’t have an own built-in ABAP type. Timestamps are not foreseen for more and you cannot do more! Especially, you should never do direct calculations with timestamps itself: You can do some simple calculations with the methods of class CL_ABAP_TSTMP:ĭATA (seconds ) = cl_abap_tstmp => subtract (Īnd that is it.You can serialize/deserialize timestamps, if their datatype refers to a special domain:.
You can format timestamps in string processing:Ĭl_demo_output=>display( | | ).You can directly compare different timestamps of the same type:.In order to handle timestamps, you can do the following: The format of such ABAP timestamps is YYYYMMDDHHMMSS.fffffff with 7 fractions of a second in case of type TIMESTAMPL.Īs a rule, you use such timestamps to mark data with – well – timestamps (time of creation, time of update, …). Those are are POSIX timestamps that are independent of a time zone. Here ts has the dictionary type TIMESTAMP and the result might look like 20160829131515.Īnd a timestamp accurate to a small fraction of a second with: In ABAP you get a timestamp accurate to a second with the statement A timestamp is a sequence of characters or encoded information identifying when a certain event occurred, usually giving date and time of day, sometimes accurate to a small fraction of a second.
0 kommentar(er)
