Delta Transfer into BW

转自: http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm

 

Delta Transfer into BW

The following update modes are at your disposal in the BW Scheduler:

Full Update

A Full Update requests all data that meet the selection criteria set in the Scheduler.

Delta Update

A Delta Update only requests data that has appeared in the source system since the last load.

Initializing the Delta Process

You need to initialize a delta method before it can work. The initialization selections are taken for the loading of delta records.

With large data volumes, a performance-friendly extraction of data from the source system is only possible using a delta method.

In the maintenance of the generic DataSource, you can set up a delta for master data attributes and texts. You can also set up a generic delta using a (delta-relevant) field with a value increasing monotonously.

Setting Up an ALE Delta for Master Data Attributes or Texts

Master data attributes or texts for which the delta transfer is to be used must meet two prerequisites:

...

1.      Data extraction must take place generically using a transparent table or a database view.

2.      A change document object must be available that is able to update the complete key for table used in the data extraction (or the table for the view) in combination with one of the tables based on the change document object.

The required control entries are supplied for the most important master data attributes or texts. By integrating a maintenance interface for control entries into the maintenance of generic DataSources/InfoSources, you can use the delta update for other master data attributes or texts.

Carry out the following procedure to generate the control entry for master data attributes/texts:

...

1.      For an attribute- or text-DataSource, choose DataSource  ®  ALE Delta.

2.      Enter the table and the change document object that you want to use as a basis for the delta transfer.

An intelligent F4 help for the Table Name field searches all possible tables for a suitable key.

3.      Confirm your entries.

With a usable combination of table and change document object, the extract structure fields are listed in the table below.  The status in the first column displays whether or not a field leads to a transfer of the delta record when master data is changed in this field.

4.      Save the settings to generate the required control entry.

Delta transfer is now possible for master data/texts.

After the DataSource has been generated, you can see this from the selection of the Delta Update field in the screen DataSource: Edit Customer Version.

You need two separate entries if you want to transfer delta records for texts and master data attributes.

Generic Delta

If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system.  Only the data that has newly arrived is transferred.

To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.

The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.

Determining the Generic Delta for a DataSource

...

1.      Choose Generic Delta.

2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.

3.      Maintain the settings for the generic delta:

a.      Specify a security interval.

The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.

You have the option of adding a security interval to the upper limit/lower limit of the interval.

A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.

b.      Choose the delta type for the data to be extracted.

The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.

With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.

With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.

4.      Save your entries.

Delta transfer is now possible for this DataSource.

After generating the DataSource, you can see this from the marking for the fieldDelta Update on the DataSource: Customer Version screen.

In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.

Example for Determining the Selection Interval for a Generic Delta

Safety Interval Upper Limit

The delta-relevant field is a timestamp.

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.

Safety Interval Lower Limit

The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.

The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.

Source(s):

            http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm