Custom Extractor FM with Delta mode

I have looked a few blogs that dont seem to address the whole picture.
the online help looks to be wrong?
http://help.sap.com/saphelp_nw70/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Im trying to set up an FM to do generic extraction.
Declare Datasource in RSo2. With Generic delta... all looks BUT
RSa3 can call th FM.
Seems the ROOSOURCE entry was with type F2.
If I copied a "proper" generic delta with complex interface and not the simple interface,
the entry in roosurce looks wrong to me.
What is the normal way to maintain the data source so that generic extraction works and can be tested in RSa3.
I also found this blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
again the issue of deltas is over looked.
The demo function is RSA3_GEN_GET_DATA
BUT when create a dat source with rso2, the function interface used to call teh function
matches function RSAX_BIW_GET_DATA_SIMPLE
and not RSA3_GEN_GET_DATA.
The helpd refers to delta mode, but the interfae does NOT have the upmode flag.
Am i missing something or is this a whole in the RSo2 process.
Custom FM based extractors CAN NOT be called with delta mode.
surely someone knows what the trick is here ?
Cheers
Phil.
Edited by: Phil Soady on Aug 25, 2009 7:00 AM

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas, ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Similar Messages

ODP Extractor failing in Delta Mode

Hi, We are calling an extractor from ECC (ZBW_DMORDERS_BI) using SAP Data Services. Extractor was working fine for last 1 year but suddenly on 31 Mar it started failing. We checked with SAP BASIS team and nothing changed on that day. When I reimport Extractor and select Query mode then it works fine. When I reimport using CDC ( with out selecting any field as it was previously) then again ift fails. When we execute ABAP program RODPS_REPL_TEST in PROD then it works fine in DELTA and FULL mode. When we try to connect/run to PROD from QA SAP Data Services then also it fails.
We get below error on failure.
5220    7500    VAL-030977    4/3/2015 1:40:54 PM    |Data flow ECC_DM_ORDERS_STAGE_DF|Reader Query_1-Mapping1
5220    7500    VAL-030977    4/3/2015 1:40:54 PM    ODP source returned error: <E: MESSAGE - Error during delta extraction: DataSource ZBW_DMORDERS_BI. MESSAGE_V1 -
5220    7500    VAL-030977    4/3/2015 1:40:54 PM    ZBW_DMORDERS_BI. I: MESSAGE - START_EXTRACTION ZBW_DMORDERS_BI. MESSAGE_V1 - START_EXTRACTION. MESSAGE_V2 - ZBW_DMORDERS_BI. I:
5220    7500    VAL-030977    4/3/2015 1:40:54 PM    MESSAGE - INIT_PHASE ZBW_DMORDERS_BI. MESSAGE_V1 - INIT_PHASE. MESSAGE_V2 - ZBW_DMORDERS_BI.>.
Any idea what to try next?
Thanks,
Kalpesh

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a
No reference here either.
my conclusion that without using pseudo deltas,   ie adding a field called delta mode, to the structure
and programming over the simple interface with a extra field
or
build a full F1 complex datasource definition tool,
there is no good standard solution.
Im still interested if anyone has a good approach to this.
regards
phil

Problem: Exchange rate in Update rules with DELTA mode

Hi experts,
During the loading since the ODS13BIL towards the CUBE, I use in the update rule the function
"CONVERT_TO_LOCAL_CURRENCY" to convert a currency.
The loading mode is DELTA.
If I modify an invoice in the system source (R/3) for example: "change on" (0CH_ON), during the loading delta since the ODS towards the cube, the exchange rate is reversed (sign), which implies that the values of the ratios during the conversion with the function module " CONVERT_TO_LOCAL_CURRENCY" are false.
How could I resolve this problem?
Example:
1-First load:
R/3:
Key figure 1       :100
Exchange Rate      :-1,2
Document currency :USD
Local currency        :EUR
Change on          :00.00.0000
ODS13BIL:
Key figure 1       :100
Exchange Rate      :-1,2
Document currency :USD
Local currency        :EUR
Change on          :#
CUBE:
Key figure 1 :100/1,2
Currency      :EUR
2-Seconde load:
R/3:
Key figure 1       :100
Exchange Rate      :-1,2
Document currency :USD
Local currency        :EUR
Change on          :06/01/2006
ODS13BIL:
Key figure 1       :100
Exchange Rate      :-1,2
Document currency :USD
Local currency        :EUR
Change on          :06/01/2006
CUBE:
Key figure 1   :100/1,2
Currency       :EUR
and
Key figure 1   :-100*1,2      <-- False
Currency       :EUR
Thank you for your precious help.

Hello,
Thank you for your answer but that still not works: Give erroneous data is corrected but the data which are not erroneous become erroneous.
I think that if I manage to return the field "Exchange misses" (0EXCHG_RATE) nonmodifiable by the DELTA mode, I cross that will resolve the problem.
With what is used following fields in the definition of the ODS, and it is what impacts it on the existing data: "Non cumulative value" et "Cumulative value"
thanks a lot.

CONVERT_TO_LOCAL_CURRENCY currency conversion errors in Delta mode

Hello,
I have been working with SAP via customer messages for a month now with no resolution. As many of you have experienced, the SAP Level 1 support is pretty useless so I would like to check here to see if I can get some help.
I found a thread where another user has had the exact same problem as I have.
Problem: Exchange rate in Update rules with DELTA mode
However, there was no answer given to him. So, if anyone can help, I appreciate it. Here's the problem:
When a record comes through 2LIS_13_VDITM (for example), it had a document currency of EUR, a local currency of PLN and a statistical currency of USD. The first time the record comes through, it comes through just fine. The exchange rate from EUR to PLN is 3.533. The statistical currency value is calculated by taking the document currency value and multiplying it by the exchange rate from EUR to PLN to get the local currency. Then, this local currency is converted to USD by multiplying itself by the PLN to USD exchange rate of 1.519.
These are the exchange rates that are coming through as key figures on the transaction data. The problem is when a delta occurs. The data goes into the ODS and then once the update rules to the cube get it, the signs are backwards on the exchange rates. This makes sense so that the exchange rate key figures will cancel themselves out, but the SAP code says to calculate the local currency, it must first take the document currency and divide by the exchange rate. It should still be multiplying because the exchange rate from EUR to PLN is still 3.533. The negative on the key figure that is being zeroed out tells the code to divide though.
You cannot simply set the reversal indicator because the values that do come through ok would then be erraneous as the previous poster who had the same issue encountered. This is really causing some bad data for us. This is SAP delivered code. Any help would be appreciated.
Thanks,
Brent

hi,
chk out various application currency conversion links
Need Urgent Help on Currency Conversion Routine
Currency conversion using transformation rule
http://help.sap.com/saphelp_nw04/helpdata/en/bc/058f4073b2f30ee10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/16/088f4073b2f30ee10000000a155106/frameset.htm
Ramesh

Load data with Delta

Hello Expert,
I loaded data from SAP R/3 into PSA using Delta mode and found that a new record which was just created was not loaded into SAP BI. What could be possible?
Step of loading
1. Initial without data into PSA
2. Full load with criteria Fiscal Period (e.g. 001.2009 - 016.2009) into PSA
3. Load data from PSA into DSO with update mode = Delta
4. Create a new transaction from SAP R/3
5. Load data from SAP R/3 into SAP BI-PSA with update mode = Delta
Expected Result: A new record should be loaded into PSA.
Actual Result: There was no record loaded.
After initial loading without data, is it necessary to full load with all fiscal period. And then load with Delta mode?
I have never seen this kind of problem before.
Is anyone familiar with this kind of problem? How did you resolve it?
Any suggestion would be appreciated.
Thank you very much
W.J.

Hi,
Is your Datasource is Logistics? if so how the job has been scheduled in LO cockpit (hourly / daily)
Did you check the record in Delta Queue(RSA7) ??
After initial loading without data, is it necessary to full load with all fiscal period. And then load with Delta mode?
I have never seen this kind of problem before.
If you have specific selections you have to do it by repair full load .. and it doesn't impact delta loads

Custom Extractor using FM for Delta Upload

Hi,
I created a Custom Extractor using FM for Full Upload. The requirement now is that it should be able to handle Delta also.
I used the standard FM RSAX_BIW_GET_DATA_SIMPLE to create my Z FM.
Please suggest me the changes I have to make in this to be able to upload Delta also.
Thanks
Nageswara

Hi Mahesh,
You can selectively load from BI side (through Infopackage) and for that you should have those selection field defined as ranges in your FM.
As per my genius friend Sidharth Gupta:
FM RSAX_BIW_GET_DATA_SIMPLE is a funct. Mod having a simple interface in which I_UPDMODE is not used. Actually FM RSAX_BIW_GET_DATA_SIMPLE is used for a full update and uses an F2 extraction method. However through ABAP we can try to make it delta capable like below.
*Declare
DATA I_UPDMODE.
Now to capture delta on AUDAT
       I_UPDMODE = u2018 u2018.
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'AUDAT'.
            MOVE-CORRESPONDING L_S_SELECT TO L_R_AUDAT.
             I_UPDMODE = u2018 D u2019.
            APPEND L_R_AUDAT.
          ENDLOOP.
This code works however is not flexible as you do not use a CASE stmt on I_UPDMODE.
CASE stmt gives more flexibility which is used in FM RSAX_BIW_GET_DATA.
FM RSAX_BIW_GET_DATA is a funct. Mod having a complete interface in which I_UPDMODE is passed to funct mod during its call.FM RSAX_BIW_GET_DATA can be used for all update types and uses an F1 extraction method. However after writing the funct mod the default extraction method is F2 in table ROOSOURCE which needs to b changed to F1 for ur mod to work. This change from F2 to F1 can be done via test abap code.
Part two of that Article is yet to be published so wait for sometime or follow above mentioned approach.
Hope it helps.
Regards,
Ashish

Generic extractor based on specific function module with delta update

Hi everybody,
I'm trying to create a specific extractor using a specific function module and a specific structure of record.
In my F.M i merge record from standard table MKPF and MSEg and return the result trhu the structure.
In initialisation mode, there's no problem . But now i'm must be able to use the DELTA mode but i don't know how to do it.
Can somebody help me?
Here is the code of my function module , i know it's not a standard one because i'm not using cursor but i got everything i need. The delta mode must be on creattion time of record in mkpf .
FUNCTION z_bw_extract_mvt_sortant.
""Interface locale :
*" IMPORTING
*"     VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*"     VALUE(I_ISOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_DSOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*"     VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
*"     VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*" TABLES
*"      E_T_DATA STRUCTURE ZBW_MVTSORTANT OPTIONAL
*"      I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*"      I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*" EXCEPTIONS
*"      NO_MORE_DATA
*récupération des données.
CASE i_initflag.
    WHEN space.
      transfert_record it_mvtsor e_t_data i_maxsize.
     DESCRIBE TABLE it_mvtsor LINES sy-tfill.
     IF sy-tfill GT i_maxsize.
       APPEND LINES OF it_mvtsor FROM 1 TO i_maxsize TO e_t_data.
       DELETE it_mvtsor FROM 1 TO i_maxsize.
     ELSEIF sy-tfill GT 0.
       APPEND LINES OF it_mvtsor FROM 1 TO sy-tfill TO e_t_data.
       FREE it_mvtsor.
     ELSE.
       RAISE no_more_data.
     ENDIF.
    WHEN OTHERS.
raffraichissement des variables de travails.
      FREE : r_werks , r_bwart , it_mkpf , it_mseg , it_mvtsor .
      CLEAR : r_werks , r_bwart , it_mkpf , it_mseg , it_mvtsor .
récupération des paramètres.
      PERFORM set_selection_criteria TABLES i_t_select.
      PERFORM init_code_mouvement.
      SELECT * FROM mkpf
      APPENDING CORRESPONDING FIELDS OF TABLE it_mkpf.
WHERE cpudt = sy-datum.
      CHECK NOT it_mkpf IS INITIAL.
      SELECT * FROM mseg
        APPENDING CORRESPONDING FIELDS OF TABLE it_mseg
        FOR ALL ENTRIES IN it_mkpf
        WHERE mblnr = it_mkpf-mblnr
          AND mjahr = it_mkpf-mjahr
          AND werks IN r_werks
          AND bwart IN r_bwart.
      LOOP AT it_mkpf ASSIGNING .
        ENDLOOP.
      ENDLOOP.
ENDCASE.
ENDFUNCTION.
Thanks in advance.

Hi,
first of all: The use of delta in a generic Datasource by FM is not supported by SAP standard. You need to change the extraction method in table ROOSOURCE from F2 to F1. There is no standard transaction to do this, you have to do a hard table update. Be careful not to change any standard datasource by error, otherwise you can get serious problems.
The interface for the FM will change with the new extraction method. You will need a new parameter I_UPDMODE of type SBIWA_S_INTERFACE-UPDMODE to distinguish between Init, Delta and Full Load.
For an example coding please refer to FM RSVD_BW_GET_DELTA_DATA.
Hope that helps
Stephan
Message was edited by: Stephan Müller

Generic Extractor using FM with Delta Logic

Hi,
i want to create a generic extractor with Delta Logic based on a FM.
The extractor works fine for full loads (extractor method "F" or "C"), but delivers no record for the extractor method "D" (Delta). I placed a hard coded break-point in the FM, so that the processing should stop while testing it with TC "rsa3". Using the extractor method "D" the debugger doesn't stop. So it seems, that this FM will not be processed for method "D". What could be wrong?
I tried different ways to create the generic extractor:
First i copied the template "RSAX_BIW_GET_DATA_SIMPLE" and tried to get the information for delta-run by "LOOP AT i_t_select INTO l_s_select WHERE fieldnm = 'DATE_FIELD'." But as the processing for method "D" does not consider the FM, there is no chance to get delta data.
On second try i used the template "RSAX_BIW_GET_DATA" and changed "EXMETHOD" from "F1" to "F2" in table ROOSOURCE for the Data Source. In this case i get information about the Update mode (Parameter i_updmode). But the processing leaves the FM for extractor method "D" out too.
Does anybody know, why the FM is not processed for extractor method "D"?
Is there another way to get delta capable extractors based on FMs?
Thanks for help in advance!

Hello
See this blog which uses the same FM with explanation
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
See this forum too
Generic Delta Function Module
Other docs
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
http://help.sap.com/saphelp_nw04/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm
Thanks
Chandran

BW Authorizations - Query variable with processing mode as "customer exit"

Hi,
Iam new to BW authorizations and have not yet worked on customer exit before. I was going through the documentation at various sites but I could not get the end to end description on how the query process( when using a variable for an InfoObject) works in case of customer exit.
Let's assume that I am using a query variable with processing mode as "customer exit" and at the exit I write some code to extract user's authorizations from a z table. if this is the case, then when an end user runs a query,how will the the system know what value needs to be filled in the variable for the requesting user. Are the user details also sent to the code along with the query variable? If so how. If I mis-understood the process then forgive me and let me know the correct process.

Hi!
welcome to SDN!
customer exit variables need programing by user. so if you create a customer exit variable, you got to right a program which extracts values into this variable. we can do what ever we want in program, SAP will not deal anything ´with customer exits.
with regards
ashwin
PS n: Assigning point to the helpful answers is the way of saying thanks in SDN. you can assign points by clicking on the appropriate radio button displayed next to the answers for your question. yellow for 2, green for 6 points(2)and blue for 10 points and to close the question and marked as problem solved. closing the threads which has a solution will help the members to deal with open issues with out wasting time on problems which has a solution and also to the people who encounter the same porblem in future. This is just to give you information as you are a new user.

Enabling FI-SL extractor with delta capability

I am working on enabling FI-SL (3FI_SL_*) extractor with delta capability.
Implemented OSS note 328197 successfully and also related OSS notes.
This works on totals table. Source system is 4.6C
Tested BW01, BW03 and everything seems to be fine, and shows as if extractor is enabled for delta loads.
I have done initialization. it works fine and got records.
But when I do delta - it shows ZERO records.
In RSA7 also I see Zero records.
If you have any experience , will you please share with me.
It's a very urgent one.
Venu

Create some records in the source system so that the base tables for this extractor will add some records.
Then check rsa7 whether it shows any records for next delta.
As Hari said..there might not be fresh records created or records changed,if you do delta load immediately after an init load.
cheers,
Vishvesh

Issues with a customized extractor running 'Full' loads.

Hi Gurus,
Is it possible to check at what date/time a particular data record has been posted in the VBPA table [Sales Document Partner Function Table]?
My issue is that we have a customized extractor that pulls data from both the VBAP & VBPA tables based on VBELN [Doc No] & POSNR [Item]. We are using an 'Inner Join' on these two tables, so if either the Doc No or Item is not present in the VBPA table at the time of extraction, the data record will be skipped and we are facing several such missing documents in BW.
The loads are 'Full' based on 'ERDAT' & 'AEDAT' on the VBAP table for the last 3 days i.e. if a Sales Document is either Created or Changed in the last 3 days, it will be picked up by the extractor. So my reasoning for the missing data records in BW is that the VBPA table entries for that particular Order had been updated at a later date and hence data was missed out during extraction [because of the 'Inner Join' based on Doc No & Item].
But since VBPA does not have a created on or changed on field, I am unable to find out when exactly a data record has been updated in the VBPA table.
Any suggestions that you can provide will be highly appreciated!
Thanks

Hi,
I feel your table join logic is not correct. Please discuss with your functional team once and try to revise the logic. Otherwise you may keep missing some records all the time. Test the extractor alot in RSA3 before replicating in BW.
Regards,
Suman

Function Module Extractor with Delta Functionality

Hi Friends,
I have to extract the entire data of CDPOS table in R/3 , as its a cluster table I am unable to build a view, I am planning to go for FM extraction, Could someone help me as how to build it with Delta Functionality.
I think I need to develop the Datasource, with Extract Structure,( Do I need to create a Structure in SE11) Please help me out .
Thanks,
Krish

Hi,
you can either use an existing structure or else create one on your own. (SE11).
The DeltaHandlig fairly easy.
When having finished the extractor (FunctionModule, Structur and DatasSource), go to the "generic Delta" button and select the relevant field.
The Generic Delta and its DeltaPointer is managed within the DeltaQueue (RSA7) and works more or less like a selection. Don't think too hard about it in your function module except taht you need to select by this field in your FM.
Did that come clear?
hth
Cheers
Sven

Issue with Fiscal Year Period in Custom Extractor

We have a custom extractor that pulls posting period (PERIO) and Fiscal Year (GJHAR)...once we move it to BW we do a concatenate in the transfer rules to get Fiscal Year / Period. Before we did the ERP Upgrade the concatenate worked and then after the Upgrade it stopped working. I have checked RSA3 and the extractor is not pulling the fields any differently then before. I have also tested the same concatenate in our development system and it is working. Does anyone have any idea what might be happening?
Before we were getting data that looked like 2008001 and now thet data is saying 8 1200.
We also have another custom extractor that does the exact same thing and it is working!
We are stumped....can anyone assist?
Thanks!
Caroline

I dont understand why you had to extract period and year?
Can you pl explain. Do you have other fields in the extractor, if so what are they?
Can you paste your code here to look at.
Ravi Thothadri

Generic extractors with delta

hi all,
can any one please provide any thing on generic extractors particular to delta (time-stamp)
VRKR

Hi,
please search the forums. This question has been asked already a lot of times. Additionally you might check my business card --> there is a link to a weblog related to that issue.
Siggi

Data syncup issue - Custom extractor for revenue recognition data from ECC into BW

Hi there,
We have created a custom extractor on top of a Function Module (FM) in ECC that reads data primarily from VBREVE table. Currently, we have close to 10 million records and full load isn't a preferred option so we built in a delta mechanism using "Created On" (ERDAT) and "Posting Date" (BUDAT). The idea is to do an initial full load and then switch over to delta loads on a nightly basis for data where:
"Created On" OR "Posting Date" is within last 6 months.
This will ensure if any updates are made to the existing VBREVE entries, this change will be reflected in the BW DSO, provided the "Created On" or "Posting Date" fall within last 6 months. The issue comes up if in ECC a billing plan is cut down to a smaller term, let's say from 3 years to 2 years, the entries for the 1 year will be deleted from VBREVE table. How can I pick up this change in BW DSO since this data has already been loaded in the past? Addition of entries are okay but I need to address the deletion on entries in VBREVE table so that it reflects this in BW DSO. Any ideas how I can accomplish this? In the example on the screenshots, BW still shows the before image and I need to be able to get it to sync up with ECC as per the after image.
-Rohit

Dear Rohit,
The case is complicated , there can be workaround using the changedon date from VBAK table. if the billing plan is changed in the sales order VBAK will be updated for changedon.
1) If the billing plan deletion is a very specific case, then using the change log tables find out which are the sales order for which there has been billing plan change. Store this sales order details in DSO day wise. call it DSO1
2) Create a self transformation to the DSO ( DSO2) where you are currently loading from the table VBREVE (DSO2 to DSO2 -For loading data from the same DSO) .Transformation should have reverse record mode given as a constant.
3) load the data DSO2 from DSO2 by filling up sales order details from DSO1 in the DTP filter.
( This will reverse the complete entry for the sales order in DSO2 for the sales order for which billing plan has been changed)
4) Now load afresh for these sales order again from source system to DSO2 from the table VBREVE.
You can also use VBAK changedon date to trigger this load.
Hope I have not confused you
Regards
Gajesh

Custom Extractor FM with Delta mode

Similar Messages

Maybe you are looking for