Skip to Content

Inbound date loses a day due to timezone issues

I have an inbound "create deep entity" process that passes a date to the SAP Gateway. The target field is a date field of type "EDATU_VBAK". When it goes into the "create deep entity" process I do a " read_entry_data" method on the data. In this method it does a "transformation" statement to transform the date from RAW XML into the deep structure which accepts it. At this point the date has one day less than what was entered on the UI.

How do I get the Gateway system to treat the date correctly and process it into the correct time zone? In the attachment you can see the first line, this is how the date is passed into the Gateway (1470744000000) and it shows the date if parsed by the browser to be Wed 10th August. Once it is transformed into my deep structure in the Gateway it is Wed 9th of August. So clearly a day has been lost due to the time zone issue.

Any advice on this would be appreciated.

Note: I know this might sound rude but if you don't have the answer please don't post on this thread. In the past when I have posted questions I have had multiple people post suggestions and wild proposals that they had no idea if they worked. They simply wanted me to go and try them and see what happens. I actually am hoping someone can give me some concrete advice which can solve the problem instead of sending me on a wild goose chase.

Thanks, any good advice will be appreciated.

Regards, Martin.

Date issue1.JPG (12.7 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Aug 03, 2016 at 09:52 PM

    Any suggestions for this one? Advice will be much appreciated.

    Martin.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Aug 24, 2016 at 03:19 AM

    I did not get to follow this up as the issue was closed with the client so I will close this thread.

    Martin.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.