Skip to Content

BAPI_ALM_CONF_CREATE Actual date(s) is in the future( Check Parameters).

I am calling BAPI_ALM_CONF_CREATE from a remote program.

On the DEV system it is working fine. I populated it with timetickets and made a commit.

On our production server this is not working. I am receiving a error from future dates: Actual date(s) is in the future( Check Parameters).

I made several tests and if I make the time 1 (one) hour delayed, the BAPI works. But the time is saved with this 1 hour delay.

I think that the timezone from production server is different from dev system.

So, how to pass a timezone in the BAPI_ALM_CONF_CREATE?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on May 30, 2019 at 08:21 PM
    -1
    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.