KB 220 - TREAD_DYN: Timestamp Issue in Records with Longtimestamp Field Condition (Microseconds > 499)

Description

The Timestamp field in the filter are used to capture delta data by comparing the values of the timestamp field between the last run and the current runtime. The timestamp value of the extracted records is set to match the value of the timestamp field specified in the condition. An issue arises when the timestamp field used in the condition is in Long Form(YYYYMMDDhhmmssmmmuuun), such as the UPD_TMSTMP field in the VBAK table, and its microseconds(mmm) value exceeds 499. In this case, the timestamp value is populated with the current timestamp.

For example, if the VBAK table is configured as shown below, and the microseconds value in the two records is 623 and 810, both of which are above 499.

Workaround

This issue is more impactful for historical records. However, for data flowing daily into the VBAK table, the date will remain the same, but there may be differences in the time for some records.

Additionally in such cases, customers can filter or report/make dashboard based on the UPD_TMSTMP field. For example, they can select a time range spanning two days, and within that range, sorting and reporting can be done based on UPD_TMSTMP.

Resolution

The permanent fix of the issue will be available for version.

Product version