Long running init -- impact on delta

Question

Hello experts,
      I know that this is something of a basic question, but I'd still like someone to clarify.
The question that I have is regarding the time stamp that is set for the delta records. I have an initialization job that runs for a long time (let's say 4 hours). My question is if the timestamp for the delta is set at the start of the init job or at the end of it? If there are any transactions that occur during the time the init job is running, are they captured in the delta queue (RSA7) or do they form a part of the init job and the delta marker/timestamp is set at the end of the init job such that the new/changed records get picked up in the queue later on.
I know that the other alternative is to run an init without data transfer and get the rest of the records in full repair requests. I'd like to know the impact of the long running init job before I choose which way to go.
Thanks in advance for the responses.

Answer 1

Hi,
For the timestamp data sources like FI,Co you cannot maintain the safelty interval delta as this is maintained by SAP.
The table names are BWOM2_TIMEST for controlling and for FI data sources in BWOM_SETTINGS tables.
The note 416265 tells you how to change it for CO and 1012874 for FI... but SAP strongly reccomends not to change these settings.
In case of FI-CO data sources you will not be able to see the data into the delta queue as there delta records are not pushed into delta queue by SAP but are pulled by BW system when the delta is scheduled.
So even if the delta is created you cannot see it in the delta queue.
For CO data source as I told you the records which got changed 2 hours before the initialization of the data sources only will come into delta queue and will get picked into delta.
The same is maintained for FI datasources.
Thanks
Ajeet