Former Member

# Safety interval upper and Lower limit

Hi Gurus,

Im very new to the FI extraction. Please clarify my understanding is correct?

Safety Interval Upper Limit

Suppose the timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.

1 Q: For the next extraction , the delta begins at 12:28:00 ( because the pointer is set to 12:28:00), As the safety interval for the upper limit is 120 seconds. The delta request will from 12:28:00 to 12:58:00 and the pointer is set to 12:58:00.

Is this correct?

If yes, then what is the use of giving this upper limit. Anyhow its going to extract the half hour data. Instead of extract the data from 12:00;00 to 12:30:00 and 12:30:00 to 13:00:00 , it is extracting from 12:00:00 to 12:28:00 and 12:28:00 to 12:58:00.

If no, how will the next delta extraction take place.

2 Q : In 0FL_GL_4 datasource, how to find the safety interval limit. I checked in RSAO2 but i could not find it. I have activated the datasource and it existing in RSA6 also. Is there any per-requistie to see the safety interval limit?

10|10000 characters needed characters exceeded

### Related questions

• Former Member
Posted on Jun 22, 2012 at 06:30 PM

Hi

You understand it in reverse.

Saftey Upper limit:

Lets take your upper limit is 120secs and your last extraction time is 12:00. now if you start extraction at 12:30 then what is the intervals that system picks for extraction.

system will pick from 11:58 to 12:30 and new delta pointer sets to 12:30.

So in this case we will get duplicate records. in this scenario you have to load data to DSO and then to Info Cube to avoid duplicate records.

Safety lower limit works exactly opposite to this.

RSO2 is for generic data source. check in ROOSOURCE table, you will get the information

10|10000 characters needed characters exceeded
• Posted on Jan 06, 2014 at 04:39 PM

For safety, the delta process uses a lower interval setting of one hour
(this is the default setting). In this way, the system always transfers
all postings made between one hour before the last delta upload and the
current time. The overlap of the first hour of a delta upload causes any
records that are extracted twice to be overwritten by the after image
process in the ODS object with the MOVE update. This ensures 100% data
consistency in BW.

662055 - NewGL/FI-SL/EC-PCA extractors: Security interval is

For DataSources with delta mode AIED (for example, 0FI_GL_14 and
0FI_GL_10), you can work with the lower safety interval (default) or
with the upper safety interval, and also with a combination of both
intervals.
For AIED DataSources, we recommend that you set the upper interval as
high as possible and the lower interval as low as possible.
However, the total of both intervals must not fall below 3600 seconds.

See the below note:

1523670 BW delta extraction: Setting the safety intervals

The parameter DELTASAFE1 from table ROOSOURCE controls

only the lower limit on time selection, while for the

upper limit DELTASAFE2 is responsible with default 0.

The value 3600 for DELTASAFE1 means, it reads with overlap

of 1 hour in the past of the prior extraction. This is

to ensure that propably not yet committed records in the

actual extraction due to data base posting delays are

at last extracted then in the next delta upload.

regards,

Colin