Hello SAP !
The syntax of
CONVERT TIME STAMP time stamp TIME ZONE tz INTO [DATE dat] [TIME tim] [DAYLIGHT SAVING TIME dst].
is a nice way of identifying if a given timestamp is a `DST` timestamp or not by looking at variable 'dst'. CL_ABAP_TSTMP has some methods to use this variable value (dst), to calculate the number of hours between two timestamps, even when clocks change. These methods are dependent on standard SAP entries in tables TTZZ, TTZD, TTZDV, etc.
But, there is a bug in these standard SAP tables for SAP_BASIS 750 / 022 for the UK entry of 'GMTUK'. Timezone 'GMTUK' is linked to the DST rule of 'EUROPE' and not 'UK'. This is fine, as the clocks in the UK and in Europe change during the same weekends. However, the clocks change at 03:00:00 in Europe, whereas the clocks change at 02:00:00 in the UK. That would mean that it would've been better to have the DST rule of 'GMTUK' linked to 'UK' instead of 'EUROPE'. But, then again, the sting in the tail - the DST rule of 'UK', in table TTZDV, has the clocks changing at 03:00:00 instead of at 02:00:00.
Could the privileged class of ABAP developers, in the UK, lookup the entries for 'GMTUK' in table TTZD and it's DST rule entry in table TTZDV to see if there are any anomalies in their respective systems, be it ECC or S/4 HANA ?
TIA,
Ash_ok.
