Issue with the timestamp under Agentry application during fetch
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.
Bill Froelich replied
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.