Non generic Delta Extraction with FM

[Former Member]

Hi

With the help of this forum i already got far in solving my problem.

I have created a FM for Delta Extraction, have changed the Table ROOSOURCE to use the extended interface EXMETHOD = 'F1', and now init and full is working. The problem is that delta is not deliviering data to bw. The strange facts are that my FM is working, and i activated the testdelta ROOSOURCE-READONLY and checked in RSA3 and it's delivering data. I have tried some Delta Types DELTA and NEWE in ROOSOURCE. I have debugged what r/3 is doing after my FM but i don't get a real clue out of this. I will investigate this further. But i believe someone of you has done this already and give me a quick clue what to look for.

(I think it's kind of strange that all this is not supported from sap itself. I mean change tables and this stuff, ok i like it but i don't have full insight in this now. )

If you need further details please ask. Maybe i could use generic delta but to be honest i want to know how all this is working and have "full" control.

Thanks for the respons.

[Former Member]

1. it will work based on Date or Time stamp or number pointer?

2. why did you update ROOSOURCE table?Never tuch standard tables with out proper reason.

3. Generic DS uses 'ADD' or 'After Images with New Records' as Delta Methods.

in simple words, Last Processed data or time or number pointer will be saved in standard table. with that help of that delta works. Take a look siggi weblog on FM Extractor.

Nagesh Ganisetti.

[Former Member]

ad 1.) it will work based on my own status table.

ad 2.) because without the change of the table it's only using the simple interface for fm. so you will not know if it's a delta full or init run.

So i don't want to go the standard generic delta mode. There should be the possibility to do the same as standardextractors from sap, they don't use date or time stamps for some reasons.

[Former Member]

For some update here. My problem was a real stupid one. I thought that the selection you do in an infopackage only affect the parameters for selection, not the data itself. That seams to be the case for full and init but not for delta. So i got data for all but not for the delta even if the fm does deliver (the same (for testing)) data.

Is there any reason behind this? Can i deactivate this?

Some other questions i have and i thought i could solve with changing the ROOSOURCE.

.)I want my status table to be update if data was successfully activated. (I think this can't be done, because at first i believed the ROOSOURCE-AFTERIMP would be that event, but i guess it's for transportation import.) Does the BW have any sort of solution for this. Ok this could be done with a process chain calling an rfc on core system after succesfully data transfer.

.)I want to update my status table if a repeat was requested or if the init entry has been deleted. I guess my way of doing this will be much simpler. I will simply reset my status table if it's an init.

But the more i look into it, the more i see it's not thought that way. I think there is some lack of functionality, which surely can be overcome with other aproches. I am more or less loosing my point why i want to do this. Maybe i wanted an interface controled from bw with less knowleage on user side.