full to delta load in generic extration

[Former Member]

Hi All,

I am loading the data form R/3 to BW with full load by using the generic data sources.

Now I need to change the full load to delta. But I get the data 2 views and one FM.

Some what I have got the solution, that is going RSO2 there generic delta will be available

If I click I will get the one wind there 3 deltas form there I took time stamp. Then I need

Select the field name.

1) Now only my problem started in that field name there is no creation

Date and last changed data, based on this we need to get the data from R/3 to BW.

2) In that 3 datasorce I used the one DS function module in this also that field name is not

available .

3) In safety interval what I need to give.

Please help on above 3 issues.

Thanks

kumar.

[Former Member · Accepted solution]

Hi Friend.

1. You can have Generic Delta based on one of these:

a. Numeric pointer

b. Calendar Day

c. Time Stamp

If Calendar Day (Creation Date) is not available then think of using Numeric Pointer. Run a Delta daily and run a Full on weekends.

2. You need to check this. Check whether there is Date or Time Stamp field present in the underlying table or not.

3. For this and other questions regarding Gen.Delta you can refer [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]

Hope this helps.

Regards

Hemant Khemani

[Former Member]

Hi,

plz check with this most proberly it works.

Go to RSO2 >> Now select the right option(Transaction data,Master data attributes or texts) >> Now in the next screen enter the Application Component >> enter the descriptions >> Now select how you want to populate data in your data source .....following options are there :

View/table >> Choose the extraction from view button if you want to want to extract the data from a transpatrent table or database view,and enter the name of the table or view...the extraction structure of the generated datasource is then identical to that of view or table.......

SAP Query/Infoset>> Choose the extraction from query button if you want to use SAP query infoset as datasource..then select the required infoset from the infoset catalog...you can go to the screen for maintaining an existing infoset by double click on its name...

Function Module

To make your datasource delta enable >> Click on Generic Delta on the top >> Here first give the field name .This field from the extract structure of a DataSource meets one of the following criteria:

1. The field has type: time stamp. New records to be loaded into the BW using a delta upload have a higher entry in this field that those which have already been loaded.

2. The field has type: calendar day. The same criteria applies to new records as in the time stamp field.

3. The field has another type. This case is only supported for SAP Content DataSources. In this case, the maximum value to be read must be displayed using a DataSource-specific exit when beginning data extraction.

Now choose one of the three options :

Time Stamp

Calender day

Numeric pointer...

Safety Interval Upper Limit >>This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.

The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.

Leaving the value blank increases the risk that the system could not extract records arising during extraction.

Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.

A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.

For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).

Safety Interval Lower Limit >> This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.

For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.

Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.

DataSource Is Real-Time Enabled

The "Real-time enabled" indicator determines whether a delta-enabled DataSource can supply data for a real-time demon.

If the DataSource finds the delta generically using a delta-relevant field, observe the following with regard to the safety intervals:

The safety interval at the lower limit may cause redundant data to arrive in BW. This data is not suitable for InfoCubes and ODS objects with key figures that are updated in appended order. With real-time updates, the redundancy of the data is increased by the short time spans between the individual runs of a real-time demon. With a lower safety interval of 2 minutes and a demon frequency of one per minute, all data may potentially arrive in the PSA three times. This can lead to database and runtime problems.

The safety interval at the upper limit makes the data less up to date. How up to date the data is with real-time is always the sum of the upper safety interval and the time span between two runs of the demon.

The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.

A distinction is made between the following:

1. Additive delta

The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.

2. New status for changed records

Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.