Re: Generic delta timestamp problem

Hi,

It sound like a design issue.

Simplify your example it look like below:

Time 1: R3 Job - 1st Run

Time 2: BW Delta - 1st Run (Read data <= Time 2)

Time 3: R3 Job -  2nd Run

Time 4: BW Delta - 2nd Run (Read data > Time 2 and <= Time 4)

So your problem here is, why on earth for the "R3 Job - 2nd Run" will write a timestamp between time 1 and 2 while it is running at time 3? It should write a timestamp >= time 3.

So you can fix this by:

1) Fix the R3 Job to write the system time for the timestamp used in delta
OR

2) Change the delta to use another timestamp field (coz you seem to picked a transaction datetime field)

As it is a Z table, you can always create new field if you don't have any can use.

Regards

Bill