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

Issue with the timestamp under Agentry application during fetch

Hello Experts,

I am running the standard SAPWM 5.3 application on my local standalone agentry server.

Everytime I reset my client and connect to the server by starting the transmission, I see that the timestamp being sent to many BAPIs in the ECC is blank.

For e.g., while starting the transmission, the timestamp being sent for "Functional Locations" fetch comes as blank.

because of this, no filter is applied while fetching the data from ECC and it comes up with picking around 45000 records.

However, in the next subsequent transmissions, the timestamp is sent to the ECC. So it usually happens when the client is reset and run.

Is this a known issue? Is there anything we can do to overcome this?

Appreciate your help on the same.



TimeStamp.png (44.6 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on May 13, 2014 at 01:22 PM


    This is the expected and desired behavior. When the client first connects to the backend it has no data and no definitions loaded. Consequently there is no last update date since it has never synchronized before. Therefore, the first sync must download everything (i.e. no filter).

    As you noted, subsequent transmits will send the date/time of the last update so that the Complex Tables can only download what has changed since the last time the device was updated. This reduces the amount of data required to be sent since the majority has not changed.

    If you at some point then reset the client the next transmit will need to start from scratch and load everything again since you have removed all the data.


    Add a comment
    10|10000 characters needed characters exceeded

    • There are couple ways to look at it. Mainly date and time stamp is used by exchange objects to handle delta changes. Going by your example of editing equipment changes by different users on different Work orders. if change pointers are enabled for equipment object than any changes made to that equipment objects are recorded in SAP. It is more of how your SAP applicaition works and configured than mobile application. Mobile applicaiton will be using BAPI's to make such master data changes and you may have to implement error handling to manage any locking issues etc .

      If Standard BAPI have field holders to capture date and time when you create or update an object, you can pass client date and time to it.

      On the side note master data changes like Equipment changes are not suppported in Work Manager application..



  • Posted on May 13, 2014 at 12:02 PM


    In agentry.ini file configure the work manager server to SAP timezone.

    Here iam posting the content i found in one of the work manager documents,hope it may help.

    Procedure Overview

    This procedure describes how to configure the Work Manager Server to use the time zone in which the

    SAP system resides. Date and time values from the client are converted from their local time zones to

    those of the SAP system based on these settings by the Work Manager Server when such values are

    updated to the SAP system. Conversely, date and time values are converted from the SAP system’s time

    zone to the client’s time zone when being downloaded to the client by the Work Manager Server.

    RESTRICTION: Though not a common occurrence, operating system manufacturers occasionally change

    the name used by that operating system for a given time zone via a service pack or patch update

    to that system. When such a change occurs, the settings discussed in this procedure may need to

    be updated accordingly, should one of the configured time zone names or time zone aliases be


    TIP: Daylight Savings Time (DST) is respected in these conversions. Keep in mind that certain time zones

    do not respect DST and others may have different start and end dates concerning the observance

    of DST. Therefore, converting from one time zone to another where such differences in DST

    observance exist can result in correct, but otherwise unexpected values.


    1. Open the Agentry.ini file found in the directory the Work Manager Server was installed in.

    2. Navigate to the [Java-1] section of the file and set the following attribute to the time zone that the

    SAP system is set to:timeZoneName=SAP’s Time Zone Name

    Example: SAP Server Time Zone is: W. Europe Standard Time

    Set timeZoneName As:

    timeZoneName=W. Europe Standard Time

    Note: The time zone name value must match the time zone value on the OS of the SAP server

    exactly. The time zone setting can be found in the SAP sever’s registry setting:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones

    Note: The “Current time zone” equivalent time zone name can also be used. For example, “Eastern

    Standard Time” can be used instead of Eastern Time Zone.

    3. Conditional Step: If the mobile devices in an implementation have a different name for a time zone

    from the one used by the operating system for the same time zone, one or more time zone aliases

    must be created. Add one entry for each potential time zone in which client devices may be used to

    the [TimeZoneAlias] section of the Agentry.ini file in the format client time zone

    name=server time zone name. For example:


    Central European Summer Time=W. Europe Standard Time

    Where Central European Summer Time is the name the client device reports as its time zone and

    W. Europe Standard Time is the name the operating system of the Work Manager Server’s host

    system uses for the same time zone. Multiple entries can be added to this section if client devices are

    used in multiple time zones within the same implementation.

    Note: The time zone aliases are used to reconcile the time zone name the client reports it is in, which

    may be different from the name used by the Work Manager Server. It is from the client’s time

    zone to the SAP system’s time to which the date and time values are converted. For this

    reason, the Work Manager Server must know how a time zone is identified by the client device,

    thus the need for the time zone aliases. This is especially true for client devices running a

    different operating system from the Work Manager Server’s host system, but can also be

    necessary even when both are the same operating system family (i.e., Windows Mobile client

    device and Windows Server for Work Manager Server system).


    Sravanthi Polu

    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.