Would anybody be willing to point me to specific documentation to how the function sap_extractor_delta_initialize() works?
I have entered my datastore and extractor name and got it successfully to run using a script in DS 4.0. However I do not see anything in ECC that indicates a subscription or request (specifically in odqmon) has occurred (as opposed to running a initial delta from the extractor).
We currently have our warehouse being loaded through open hub extracts from BW. We now want to switch to running the extractors directly in DI. No need to reload all that data from an initial delta perspective.
Thanks for your response! However I am confused…indicating it as an initial load will bring all the data across for that extractor. Correct?
I am looking to have the delta marker set without brining any data across. Most of that data already resides in our data warehouse. I only want to bring new/changed records across as of when we implement the change of having DI use the extractors directly. For some extractors like 0FI_AP_4 and 0FI_GL_6, there are a high number of records I would prefer to not load those over again.
Another post on the forum stated to use the sap_extractor_delta_initialize() function. However it does not seem to do anything for me.
I don’t know how to avoid this, but here’s an idea:
you could try kicking off a full load to a temporary table and killing it after it starts to return data, and then try a delta. Not sure if this will work or not…
I will not be able to pull that off in a production environment.
When you converted from Open Hub to Data Services, did you reload all your targets?
I have tried putting CDC filters on and taking them off after the “initial”. That did not work very well as the 1st “delta” run just picked up everything else that was not loaded initially.
0FI_AP_4 uses a delta table called BWOM2_TIMEST, you will have to use a report to change this. There is a report called BWOM2_TIMEST to switch the last loaded timestamp record
Thanks! This is very helpful. Now I have to take this into account too!
Looking at the table, it does not look like you can run multiple deltas against the same extractor (one from BW and one using Data Services) since there is no way to distinguish between subscriptions/requests. Even if it be on a temporary basis. Not really a big deal to stop the BW extract. Just needs to be coordinated.
Is there a way to force a subscription in ODQMON for the Data Services usage of the 0FI_AP_4 extractor (without doing any extract of data) and have it simply use the latest delta timestamps from the BWOM2_TIMEST?
Each extractor’s queue is managed based on its name. So you can import the extractor into data services twice, but giving it a difference name the second time. Same thing happens with openhub.
I do not understand how that is possible based on what I am looking at. I must still be missing something in the process. We have imported the same extractor multiple times into data services giving each one a different name. And I can see the different subscriptions in ODQMON.
However, looking specifically at delta extractors from Finance (AR, AP, GL, etc.) driven by the BWOM2_TIMEST table, it does not differentiate between subscription. The table provides the datasource, date, time, extract low datetime, extract high datetime, and an indicator of what was the latest delta extract of a particular datasource. Using the 0FI_AR_4 extractor as an example, we have two entries in the table for a particular run date. One from SAPBW running against ECC (which ran first), the other from Data Services running against ECC(which ran a few hours later). The extract low and high datetimes for the first run were 7,493,202,870,000 and 7,493,697,640,000 respectively. The second run was 7,493,697,640,000 and 7,493,763,780,000 respectively. In addition, the latest extract indicator moved from the first run to the second run. The second run did not contain records from the first run and vice versa. In that scenario, both targets are missing data because the delta datetimes are stepping on each other.
However that is still not the core of my issue. I want to exclusively use Data Services to run extractors. I need to get a subscription into ECC, bypassing the initial load and extract deltas using what is currently in the BWOM2_TIMEST table (at least for the Finance extractors). Unlike SAPBW Infopackages, I do not see a way to run an Initialize delta process without data transfer in Data Services.
(BOB member since 2012-01-17)
(BOB member since 2008-07-17)