Skip to Content

Can we identify initial sync in SAP Work Manager ?.


I want to log few details when initial sync happens in SAP Work Manager.

Please let me know if anyone has idea about this.

Thanks in Advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Mar 22, 2017 at 10:17 AM

    Hi Kumar,

    We can verify the details of sync in SMP logs.These logs capture information regarding the users,complex tables,data tables,work order download,notification download..etc.


    Sravanthi Polu.

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 06, 2017 at 12:05 AM


    Some techniques you can use is to see if the Complex Tables get rebuild. So in the logs you may check for something like these:

    See if you can find under the complex table:

    build()::rebuilding=true in the logs. This could be a hint that the complex table is building rebuild from scratch.

    Also see if you have a timestamp that is in the January 1900. This could mean that there was no prior sync that established the lastupdated time.

    Ex: clientLastDataUpdateTime=Mon Jan 01 00:00:01 PST 1900

    But relying on just the clientLastDataUpdatetime can be misleading as there could be an option in the complex table not to update it in the client.

    If you have breakpoints in the BAPI area, it may land on the Is Initial state. This is similar to the Java area.

    The other techniques used by other Agentry developers are to utilize the Agentry data tags. Normally seen again in a complex table rebuild state.

    In the link above, you have the following:

    <<rebuild>>Returns true or false, indicating whether or not the table is in a rebuild state. This is intended for use in synchronization to determine if the synchronization should retrieve only modifications to the table’s data, or if all records for the table should be retrieved. Returns true when a change to the complex table definition has been published to the Agentry Server; if the synchronization logic includes the data tag <<user.agentryID>> and the value of that tag changes from the previous transmit; or if the tables force reload logic indicates the table should be in a rebuild state.<<lastUpdate>>Returns the date and time provided by the client when the complex table was last synchronized. By default this value is provided by the Agentry Server based on a query of the back end system. However, synchronization of the complex table should include retrieving this value with the table’s data. The latest date and time retrieved during that process will be used as the complex table’s last update value. This tag supports the use of the named parameter format to format the time and date using date and time tokens.

    But you may follow the same guidelines to find the time stamp and if the value is not empty then it is a delta sync. But due to a date property in the database cannot be null, then there is a forced insert of Jan 01, 1900 in the backend. This strongly suggest that it was an initial sync.

    Hope this helps out.

    Best Regards,

    Mark Pe
    SAP Platinum Support Engineer

    Add comment
    10|10000 characters needed characters exceeded