Delta Queue doesn't get update after initializaion

[Former Member]

Hi All,

Please help with the following problem. We recently updated our system to BI 7 and I tried to reinitialize some of the delta extractors(0FI_GL_4, 0FI_AR_3, etc). I was able to reinitialize fine on the BW side but when I go to R/3, I don't see any of the DS when I look into the delta Q(RSA7). We updated the BI 7 to SP 15, PI basis is 2005_1_700. All full load is working fine, it's just that I don't see any entries when I run RSA7 in R/3. Thanks for any info. you might give.

Vinh

[Former Member · Accepted solution]

There is a possibility that no delta is being generated in R3. Do some posting in R3 and check if delta is being collected in RSA7.

Thanks..

Shambhu

[Former Member]

Hi Vinh,

0FI_GL_4 is a so-called timestamp-based extractor. You can find more information of this in the SAP help. There are also some OSS messages to all this COPA/FI extractors. Just look for 0FI_GL_4 in service.sap.com. R/3 checks for new documents created or changed since the last delta plus a security delay of 2 hours and puts them in the delta queue.

Regards,

Anand Tej.

[Former Member]

Thanks for replying, you guys are fast. I tested the DS (0FI_GL_4) in RSA3, I am getting the data there. Regarding the data, I can see that it's working through initialization with data transfer. But my problem is the listing of the DataSources when you go into RSA7. Hopefully, you know what I mean. In the source system, when I go into RSA7, I would normally see all the DataSouces listed. I deleted all of them when I upgraded to BI 7, and decided to reinitialize them all. After sucessfull re-initialization on BW side, and, now when I go into RSA7, I don't see anything there,(no DataSource listed!) but my initialization says that everything is sucessfull.

Am I missing something with new BI 7? Do I have to manually create an DS entry on one of the tables?

Thanks to all for replying.

[Former Member]

No we dont create any entries in any of the table. If your initialization is proper then u need not to worry about that.

You just schedule your delta and check it tomorrow. Hopefully you will be able to see the entry of datasource in RSA7.

[Former Member]

Yes, this does matter. If there is no data in R3, it wont pick up any records. Te see the communication between BW and RSA7, check the source connection. Once the data is there in RSA7, it will show in RSA3 also. And delta load will give you records in the BW.

Thanks...

Shambhu

[Former Member]

Thank you all for helping.

Does it matter if there is no data in R/3? Usually, when I initialize the delta, I would immediately see an entry of that delta DS in the queue(RSA7). The DataSource would have 0 for its LUW. I went back and tried this in the BW 3.1 system and it created an entry in RSA7 when I initialized it. Is there a way to check or debug this to see if BW actually communicating with RSA7? Or where is the log for the source of errors would be. I also tried reactivating the Business Content, and that didn't really help. I also tried initializing with data transfer and that didn't create an entry in RSA7 either, though the data did get extracted successfully. I am at a lost right now. I appreciate all the help right now.

Thanks,

Vinh

[varma_narayana]

Hi...

In your case the Data sources are FI related.

For FI data sources the Delta extraction can be based on Extractor or Delta Queue.

Check it in the "RODELTAM" Table for the corresponding Delta methods of your Data sources (eg AIE or AIM...).

If it is Extractor based then the Delta queue may not have any entry.

Bcoz for FI Delta extraction there is a Time Stamp mechansm

(table BW0M2_SETTINGS).

So u need not to bother aboud Delta queue if the Delta extraction is happening successfully...

Cheers...

[Former Member]

Hi Vinh,

Your problem is that you are not getting delta data right ?

Now the various options that you can try out:

1. Check that data for delta extraction is really there or not, if there is no delta data then there is no point that you will be getting it. Try the delta option in production server.

2. Do init load first, that can be with data transfer as well without data transfer.

3. Once init is succesful then go for delta.

This is the procedure, we have done it like this and working fine.

Now for init make sure that setup fills are done if necessary.

Hope this helps you out.

Thanks

Dipika

[Former Member]

Hi,

All the Fi related data sources are based on the pull mechanism that is data is pulled by BW( kind of) and the R/3 system doesnt have any mechanism to push the data into the delta queue and is pulled to BW when delta load is triggerred.

Thats even there is delta records( changed records after last time stamp) you will not see them in RSA7 but will get pulled to BW when a Delta load is trigerred.

This could be attributed to the fact that FI data is dependent upon other modules and can be extrapolated by the companies for there need and is not created in real time unlike sales or deliveries data.

Whereas in case LO extractors they are based on push mechanism that is the data for this extractors are pushed to the delta queue by R/3 itself with the inbuilt mechanism and therfore you can always see them in RSA7.

hope it clears

Thanks

Ajeet

Edited by: Ajeet Singh on Jun 6, 2008 12:20 PM

[Former Member]

Hi Vinh,

Have you initalized your delta beforehand ???

May be ur not getting the delta's due to that, and also check wether the delta data is available or not in r/3.

Thanks

dipika

[varma_narayana]

Hi ...

Try these steps:

1. Post some documents in R/3 (related to the FI extractors that u are working)

2. Check the Extraction in RSA3.

Mode: D (Delta)

If it is extracting the records.

3. Create a Delta info Package in BI and Schedule.

cheers...

[former_member345199]

Hi,

Check this

Note 728687 - Delta queued: No data in RSA7

Hope this helps.

Thanks,

JituK