delta methods

[Former Member]

Hi,

can anyone clarify me some doubts on this.. i read Roberto's weblog still im confusing

<b>serialized V3 Update.</b>

This is a normal update method. here Doc data is collected in the order it was created &transfered into BW as a batch job. the transfer seq is same as the order in which the data was created in all scenarios.

<b>Direct delta</b>

In this Method, extraction data is transfered directly from the doc postings into the BW delta queue. The transfer seq is the same as the order in which the data was created.

<b>Queued delta</b>

In this Method, extraction data is transfered directly from the doc postings is collected in an extraction Queue, from which a periodic collective is used to transfer the data into the BW delta queue.

<b>In this method, whther the transfer seq is the same as the order or Not?</b>

<b>Unserialized V3 Updated</b>

This method is almost exactly identical to the serialized update method. the only diff is that the order of doc data in the BW delta queue does not hav tobe same as the order in which it was posted.

Correct me if i am wrong? pl's clarify me on this

here my ques is.. if im getting data from diff languages how these 4 methods are handling ?

what is Logical unit work(LUW)? how they are differ fro these 4 methods ?

Which method is efficient and why? how come we know that which method we hav to used?(queued,direct,unserial..)

Correct me if i am wrong? pl's clarify me on this..

pl's send me docs to linda.biw@gmail.com

Thanks in Adv

Linda

[edwin_harpino]

hi Linda,

regarding luw, take a look oss note 380078-FAQ: BW delta queue (RSA7): Questions and answers

...

Question 2:

What is an LUW in the delta queue?

Answer:

An LUW from the point of view of the delta queue can be an individual document, a group of documents from a collective run or a whole data packet from an application extractor.

...

which method is efficienct, another note 505700-LBWE: New update methods as of PI 2002.1

...

new direct delta

This update method is recommended for the following general criteria:

a) A maximum of 10,000 document changes (creating, changing or deleting documents) are accrued between two delta extractions for the application in question. A (considerably) larger number of LUWs in the BW delta queue can result in terminations during extraction.

b) With a future delta initialization, you can ensure that no documents are posted from the start of the recompilation run in R/3 until all delta-init requests have been successfully posted. This applies particularly if, for example, you want to include more organizational units such as another plant or sales organization in the extraction. Stopping the posting of documents always applies to the entire client.

new queued delta

This update method is recommended for the following general criteria:

a) More than 10,000 document changes (creating, changing or deleting a documents) are performed each day for the application in question.

b) In future delta initializations, you must reduce the posting-free phase to executing the recompilation run in R/3. The document postings should be included again when the delta Init requests are posted in BW. Of course, the conditions described above for the update collective run must be taken into account.

unserialized v3 update

This update method is recommended for the following general criteria:

a) Due to the design of the data targets in BW and for the particular application in question, it is irrelevant whether or not the extraction data is transferred to BW in exactly the same sequence in which the data was generated in R/3.

and let's wait Roberto's reply

[Former Member]

Hi A.H.P/Amit,

Thanks a Lot...

but u dint mentioned.. if we are getting data from diff languages how these 3 methods(direct,queued,unseri)are handled..??

Thanks,

linda

[Former Member]

Hi Linda,

Here are some excerpts from SAP's content itself about the Deltas in SAP BW.

Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.

Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each DataSource into the BW delta queue, depending on the application.

Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.

For LUWs:

http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4c2a79e11d1950f0000e82de14a/frameset.htm

Hope it helps!!!!

Do not forget to assign points, if helpful.

Amit

Message was edited by: Amit

Message was edited by: Amit