I have a question about pub.date:currentDate.
I am running:
SAPBC 4.6 (IS 4.6) with patches (SAPBC references) 520423 (SR1) and 516504 (running IS as a win2000 service)
I have been using pub.date:currentDate with the pattern yyyy MM dd HH:mm:ss SSS and no other Service In settings. My assumption is that the time should be based upon the time of the box that SAPBC (IS) is running on and up until Sunday 25th this seems to have been the case.
The returned date/time is then used to timestamp a log entry written to a flat file using a java buffered writer service (based on sample.IO.utils.fileWriter java services) that appends data to a file thus giving me a history of the running of the process.
I have a scheduled task in SAP that calls SAPBC (IS) at 04.30 am every day. Up to and including Saturday 24th August, the timestamp in the log has been correct (well, give or take a bit because the different servers are never on the same time). From Sunday 25th August onwards, the time has been reported in the log file as an hour ahead of the actual time and when I look at the SAP logs, the run time is still 04.30 (am). The Win2000 box that SAPBC (IS) runs on is at the local time and has not been changed.
For example: dates in yyyy/mm/dd (I’m in Melbourne, Australia)
2002 08 23 04:28:33 953
2002 08 24 04:27:47 296
2002 08 25 05:28:01 175
2002 08 26 05:29:35 187
2002 08 27 05:27:43 453
So anyone got any ideas? I have read the BuiltInServicesGuide and cannot see anything that could explain this but I could be missing something very simple. Do I need to do anything else?
Could it be that for some reason SAPBC (IS) thinks that summer time has arrived here in Australia?
Any help greatly appreciated.