How to specify a safety interval for DS 0UC_SWTACTIVITY ?

[Former Member]

Hi Gurus,

I need to specify a safety interval for DS 0UC_SWTACTIVITY.

The fact is that we always miss the data that are created in the source system during the extraction process ; and data are created at anytime.

Any suggestion ?

Thanks in advance,

Regards,

Thomas

[Former Member]

Hi,

We can define delta for generic data source using 3 different fields.

1) Time stamp

2) Calendar Day

3) Numeric Pointer

The use of safety intervals is to make the system to extract delta records which might missed in last extraction (they might not saved at the time of extraction)

Now we will discuss this with delta field as “Numeric Pointer”

Safety Interval Upper Limit: Let’s assume in the last extraction delta pointer set to 1000(numeric pointer). Now in source system we have 100 new/changed records, so new numeric pointer in source system is 1100. If the safety interval upper limit is set to 10, the selection interval set by the system is 1000 to 1090(system will subtract from new numeric pointer value).

Note: If you use upper limit, it doesn’t result in duplicate records. So you can directly load the data from Data source to Info Cube.

Safety Interval Lower Limit: In same situation instead of upper limit, if lower limit is set to 10, then selections set by the system is 990 to 1100 (system will subtract from last delta numeric pointer).

If the delta field is Time stamp instead of Numeric Pointer, we can set the safety intervals in seconds (say 300s or 1800s etc..).

Note: If you use lower limit, it results in duplicate records. So you should not load this data directly from Data source to Info Cube. It is mandatory to use DSO in your data flow and then load the data to Info Cube.

Regards,

Aravind.

[former_member186082]

Hi Thomas,

DS : 0UC_SWTACTIVITY (delta) also takes SPRAS: language key into consideration for selection criteria. Hence check the records based on this, records might be missing.

Determining Selection Intervals with a Generic Delta:

1. For every delta extraction, there is a selection criteria generated:

    "last extraction status (RSA7)” < x <= Today.

2. Offsets for upper and lower delimiter are subtracted from the respective sides

3. Example 1 shows the normal behavior (both offsets = 0), example 2 shows both safety

intervals (offset for lower delimiter = 2, offset for upper delimiter = 1)

4. Offset for lower delimiter can only be defined for delta method “new status for changed

records

Tips:

1. If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.

This will load Delta in BW as of yesterday. Leave Lower limit blank.

2. If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes).

This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.

3. If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use

Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10

records will be loaded again. If a record is created when load was running, those records

may get lost. To prevent this situation, lower limit can be used to backup the starting

sequence number. This may result in some records being processed more than once;

therefore, be sure this DataSources is only feeding an ODS Object

Regards
Chandu