Skip to Content
Former Member
Oct 18, 2013 at 10:18 AM

Daylight Saving time issue between BPM and RFC call.


We are having a date issue between our BPM process and an RFC call.

We are receiving a date from SAP via the RFC call. The date here is correct, as we have created a web service for the RFC and tested the value that we receive.

However if we receive the date from the RFC directly into the BPM process, then the date is set to 1 hour behind. If we are using the Date type, this is an issue, as the time part of the date is not stored. So this then means that a date say of 1/6/2014 is set to 31/5/2014 (format dd/mm/yyyy). Because some of our logic relies on dates this is unacceptable.

We know it is a daylight saving time issue, as if we use a date after october the 27th, then the dates match up...

Any ideas on how to fix this. I have seen some issue with webdynpro and bpm; the result is to get the date as a string and parse it to date format in bpm. We can't really do this as RFC changes would affect a lot of other systems.

We have tried a few different server changes - is there a specific one that will fix this?

Thanks for any help.