Problem with Generic delta timestamp and init timestamp

[Former Member]

Hello,

When creating a generic extractor in delta mode in R/3, is it possible when there are 2 BW destination systems and only one R/3 source system, that the timestamp of the Init of one of the destination systems takes over the timestamp of the Delta in the other system?

Could this cause records to be resent in the following Delta?

Is there a way to handle the destination system in the timestamp table too?

Thank you in advance for you help.

[Former Member · Accepted solution]

Not sure whether the timestamp would be based on the source server or requesting server clocks. If the latter I can see that there is an argument in your suggestions assuming the times of the receiving server clocks are different

[Former Member]

Thank you for you replies!

[former_member205352]

I dont think so it will happen like that.

If there are two BI systems say BI1 and BI2 and one R3 system.

Doing a init from BI1 will create a delta queue with BI1 as target and on doing init from BI2 there will be one more entry in delta queue with BI2 as target.

They both will get independent delta.

Hope this helps.

[Former Member]

Hello,

But suppose you did one Init load in BW1 and then let deltas run every 30 minutes. After a couple of hours in BW2 you make a new init without stopping the delta in BW1. The timestamp of that second init happens to be at the same time as the delta is running (few seconds difference) could it then cause problems?

Thanks !

[Former Member]

Hi,

Explanations are in SAP note 775568.

Rgds,