cancel
Showing results for 
Search instead for 
Did you mean: 

LO extraction

Former Member
0 Kudos

Hi Gurus

As we need to stop document posting during set up table compilation run , would you pl tell me how can we stop this document posting? Do we need to block something?

Also when we load R/3 data to BW for the first time we select Dirrct delta in update method of LBWE and for delta load we select "Queued delta" AM I right? I went thro all weblogs but this is confusing me a lot.pl guide me.

Thanks

KK

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Krishna Kumar,

Don't confuse yourself too much.

First you need to do Init Load.

After sucecssful init load, you need to activate delta in LBWE. Here you will choose whether direct delta or queued delta ONLY once. There is no first time, second time etc.

When the document posting is not much, you can do 'direct delta'. If the document posting is high, you will go for queued delta.

In any case, it is ideal to stop document posting during delta load. You can schedule the delta data collection in such a way that there is no document posting at that time.

hope this helps...

Thanks,

Raj

Answers (3)

Answers (3)

Former Member
0 Kudos

Dear Krishna,

To add to the above details...

when to go for direct delta, queued delta, unserialized V3:

-


During the first load, if it either init or full, data will come from setup table.

1. When no. of document changes between two delta extractions is relatively small, choose "Direct delta". The recommended limit is 10000 i.e. If the number of document changes between 2 successive delta run is within 10000, direct delta is recommended.

In this case, the no. of LUWs (Logical Unit of Work) is more as they are not clubbed into one one LUW.

2. Queued delta is used if no. of document changes is high ( more than 10000). In this case, data is wriiten into an Extraction Queue and from there it is moved to delta queue. Here upto 10000 document changes are cummulaed to one LUW.

3. Unserialized V3 upadte method is chosen ONLY when it is not important that data to be transferred to BW in the exactly same sequence as it was generated in R/3.

Thanks,

Raj

Former Member
0 Kudos

Thanks all for clearing my doubt.

Points given .

KK

Former Member
0 Kudos

Hi Krishna,

you doubt was cleared? I don't think that everything was said.

When you want to initialize LBWE-datasoures you have to stop booking during the filling of the setup tables.

So here is a step-by-step solution:

- Stop booking (e.g. block user, do this on weekends)

- Fill setup tables (found in SBIW)

- Initialize delta in BW

- after initialization booking can start normally

- Set up quered delta (or direct, depends on the amount of data)

- Schedule job for quered delta and align it with the daily delta update in BW

Hope this makes things a bit clearer.

Greetings,

Frank

Former Member
0 Kudos

Hi Krishna,

Adding to the above. You can do all these things during weekends.

Regards

Sajeed

Former Member
0 Kudos

Hi Krishna,

There are 4 Update methods of LBWE:

Direct Delta

Queued Delta

Serialized & Unserialized

These are the update methods defined from the Application tables like VBAK VBAP etc to Delta Queue

so Direct Delta : daily transactions(Delta)data that has been Populated into App tables will be Synchronously updated to Delta Queue.

Queued Delta : Here there will be a Intermideary queue in between the Delta Queue and the Application tables.so the daily deltas posted will be synchronously updated to Queued Delta. Depending upon the delta frequency a job needs to defined explictly which will then updates data from queued delta to Delta Queue

So the main differece between Direct Delta and Queued delta is how the data updates the Delta Queue

Serialized Update mode is in nurture as it will not appear in 3.1 or 3.5 Version

Unserialized is used where the sequence of records that has generated in source system is of not so important to that of the records that has been transferred to bw.

Former Member
0 Kudos

Hi Anupama

Thanks for your answer but my question is if we need to stop document posting during queued delta or not.

and..

When we load the data from R/3 to BW for the first time what we need to select in update method in LBWE?

and when we load the data second time what we need to choose under update tab of LBWE?

pl help

KK

Former Member
0 Kudos

For the first time when we load the Historic data from R/3 to Bw we will use the concept of setup tables. Normally you use a user free time to run a setup for all historic data. After setup you schedule a initilization of delta (with or without data transfer). After that all transaction data is posted to the delta queues in the source system. After a sucessful full upload you can delete the setup tables. They only use disc space. If you once will do another full load, you can easily start another run to fill the setup tables without any effect to the delta mechanism.

so once the initialization has done then comes the picture of Deltas and update modes of delta's

so when we load data from R/3 to BW for the first time the data source need to initialized to automate deltas Mechanism

is it clear or any doubts Let me know Please.....

Former Member
0 Kudos

Hi Krishna,

The Update method depends upon the volume of data you have for the extractor. Generally Direct Delta is not preferable for the large volume of data.

Queued Delta is the best update method for the large volume of data.

Hope it answers your question.

Regards,

Srikanth.