Skip to Content
author's profile photo Former Member
Former Member

SAP Work Manager. Actual date(s) is in the future (check parameters) error.

Hi All

When I try to pass confirmed hours from SAP Work Manager to the SAP the system shows next error.

--

Logging user into server

Logged in

Sending client info

Sending time info...

Receiving time info...

Sending OperationEdit...

Sending LaborAdd...

LaborAddSteplet - Actual date(s) is in the future (check parameters)

Server error - please contact your administrator (13)

Logging user out

--

Date-Time on Client, SMP Server and in the SAP Server is same and correct.

Time zone and daylight saving time is the same and correct.

I set the work time in the past.

But it works inly when the time is set to yesterday or earlier.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Oct 16, 2015 at 03:23 PM

    In the file

    C:\SAP\MobilePlatform3\Server\log\agentry\events.log

    I found next lines

    ---

    10/16/2015 14:49:46, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:49:46, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:49:48, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:49:48, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:51:45, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:51:45, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:54:53, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' alias was not found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:54:53, 0, 20, 154, Thr 4616, Client Time Zone 'RTZ 2 (зима)' is not recognized and no alias was found in TimeZoneAliases in Agentry.ini

    10/16/2015 14:54:54, 1, 20, 26, Thr 4616, com.syclo.agentry.BusinessLogicException: Measurement time cannot be in the future

    ---

    What it could be? I don't have Agentry.ini file on the SMP Server Computer.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 08, 2015 at 03:14 PM

    Hello Konstantin,

    which version of work manger you are using and on which client r u testing?

    Also try to add the proper timezone parameter in the Agentry.ini file

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 09, 2015 at 07:49 AM

    See at SAP note:

    "0002185367 SAP Work Manager error on transmit - AddLaborTime - Actual date(s) is in the future”

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Oct 09, 2015 at 09:05 AM

    Hi Konstantin Kulikov ,


    This is general issue, when SMP server & SAP Servers are located in different time zone. To resolve this issue, maintain the time zone in tcode SU01. Refer the following screen shot.


    Hope this will help you.

    Regards,

    Ravi


    pastedImage_0.png (31.0 kB)
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Nov 17, 2015 at 11:19 AM

    Former Member

    Former Member

    Hello Experts,

    I am also facing same Issue. I did changes in SMP Application backend

    Time Zone=(UTC+05:30) Chennai, Kolkata, Mumbai, New Delhi.

    But getting same error on first transmit. But after transmitting 2-3 times it get transmitted successfully. This scenario happens with all operations.

    So where exactly we are missing???

    Thanks & Regards,

    Ashish Sarode


    timezone.png (31.0 kB)
    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.