Extractor with delta

Hi Everybody,
I am using a delta mechanism and would like to check the actual value of the field used for the delta. Where can I find this value?
Thanks in advance
FedeX

Hi Fedex,
Check in RSA7. Check the last column i.e. STAT column. But before this you have to upload the data atleast once.
If useful..assign points.
Regards,
P B

Similar Messages

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

Function Module Extractor with Delta

I'm very new to working with the BW, so I hope I'm explaining my question in a way that makes sense.
I need to make a BW extractor that pulls data from at least one table, possibly more, and which also calculates some data.
I think the only way I can do that is by using an extractor with a function module.
I've been looking at the examples in function group RSAX, and I think I sort of get it, except for one part.
I'm really confused about how the delta works.
I'm looking at the example: RSAX_BIW_GET_DATA_SIMPLE
Does it even use a delta?
I'm trying to understand how the delta gets passed, and how it gets used to filter the data in the function module. I'm not sure if it's something I need to code in myself, or if it's something that BW does by itself, or what.
I'm not sure if I'm making sense, but if anyone could help me, I'd appreciate it.

Thanks guys, you've been super helpful so far, so I'm just going to keep asking questions. I promise to award points at the end
I'm looking at it now, and I think if I change it to read from a table, instead of read from a function module I can use the 'numeric pointer' option for the delta. (Does that just mean a number? For example, payroll runid is a number, so I could use that and only get new payroll runs?)
However, there still are some calculated fields they want. Someone mentioned doing that on the BW side. How would that work?
Sorry for such vague questions, but any help is really appreciated.

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

Generic FM extractor with Delta

Hello all,
I am trying to create a delta function module extractor on a table. I have creation date ANDAT, last change date AEDAT and a deletion flag on the table.
FM has to handle history, new and changes.
How can I generate delta? Can I just use RSO2 to set up delta? How can it be done? Also, can I get the code for a generic FM delta extractor?
Please help.
Thanks,
Anirudh.

Hi Sajeed,
So, I do not have to handle delta in the extractor at all? Just create a function module based extractor with all the fields and actually take care of delta in the infopackage??
The creation date is for newly created records and the change date is for changed records.
My email is [email protected]
Thanks,
Anirudh.

Enhance LIS_ extractor with delta load

Hi all,
I need to enhance 2LIS_02_ITM or 2LIS_02_SCL with account assignment (EKKN). How should I handle the delta from account assignment? It is in 460 environment. I'd like to have similar extractor as 2LIS_02_ACC which exists in 700.
How should I approach? Which way is better?
Options one: Create a generic extractor, delta base on AEDAT in EKKN table. Create custom ODS....
Option two: enhance current 2LIS02_ITM or 2LIS_02_SCL, add cufs. But how to handle the delta?
Thanks
J.

Hi J CHEN
In my opinion first check with MM -Purchasing consultant whether the delta in account assignment is linked to purchasing document changes or not ? (check whether delta is supported or not ...you can do this testing in SAP R/3 Side) and if answer is YES then you should go for Option 2 which is relatively simpler.
hope this helps
Regards
Pradip
(Friends: Don't forget to assign points !!)

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

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

Sharing an extractor with another BW system possible?

Dear all,
We currently run BW3.1. Now we would like to install NW2004s next to it.
Is it possible to use the same extractor with delta loads when you have only 1 source system with 2 BW systems?
Do both BW systems contain all information after delta loads?
Thanks in advance,
Ralph

Hi,
Yes, its possible. You can have just one source system, feeding multiple BW systems. But in your case, I'll be careful as you are trying to upload data to 2 different versions of the BW system. You have to check and test for the PI versions on the R3 side. Your current set of PI versions on R3 will have to be upgraded if you are planning to connect the system with the netweaver 04s version. Once you upgrade, you also need to make sure that the data loads work fine with your older BW version as well.
Cheers,
Kedar

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

Issue with Delta Load in BI 7.0... Need resolution

Hi
I am having difficulty in Delta load which uses a Generic Extractor. The generic extractor is based on a view of two Tables. I use the system date to perform the delta load. If the system date increaes by a day, the load is expected to pick up the extra records. One of the tables used in the view for master data does not have the system date in it.
the data does not even come up to PSA. It keeps saying there are no records.... Is it because I loaded the data for yesterday and manually adding today's data...?
Not sure what is the cuase of delta failing....
Appreciate any suggestions to take care of the issue.
Thanks.... SMaa

Hi
The Generic DataSource supports following delta types:
1. Calender day
2. Numeric Pointer
3. Time stamp
Calday u2013 it is based on a calday, we can run delta only once per day that to at the end of the clock to minimize the missing of delta records.
Numeric pointer u2013 This type of delta is suitable only when we are extracting data from a table which supports only creation of new records / change of existing records.
It supports
Additive Delta: With delta type additive delta, the record to be loaded only returns the respective changes to key figures for key figures that can be aggregated. The extracted data is added in BI (Targets: DSO and InfoCube)
New status for changed records: With delta type new status for changed records, each of the records to be
loaded returns the new status for all key figures and characteristics. The values in BI are overwritten (Targets: DSO and Master Data)
Time stamp u2013 Using timestamp we can run delta multiple times per day but we need to use the safety lower limit and safety upper limit with minimum of 5 minutes.
As you specified, the DS is based on VIEW (of two tables, with one containing date and other does not).
Kindly check the above lines and verify, if the view (primary key) could be used to determine the Delta for your DS.
Also let us the if any standard SAP tables used in creating VIEW and if so, what is the size of the DS load every day?
Thanks.
Nazeer

3FI_SL_C1_TT - Procedure of extracting data with delta

Dear experts,
I try to load FI-SL data with delta.
We use extractor 3FI_SL_C1_TT and have implemented the start routine from note 577644 to create 0balance within the transformation.
Delta is only available for actuals so we select data only for valuetype 10 as recommended.
I read that I have to do a full update of the closed periods.
To load the carryforward from 2014 I have to select 000.2015 and load it with a full load.
Till now every thing is clear.
But what are the next steps?
What do I have to select within the infopackage for the init load of the open periods (current year)?
After executing the init load: how do I have to define the delta load?
Thanks for your help.
Best regards
Mirjam

Hi Leszek,
we use cube for each year.
So when the periods of the previous year (2014) is not closed, too, I have to work with them
the same as with cube for current year and do at first an init for the whole year and after that a Delta for whole year.
For current year cube I try do init/Delta with 001.2015 - 016.9999. But what do I do with the carryforward -
I can´t do only once a full, case with every new data record for 2014 it will Change.
What is the best practise with carryforward in this case?
Regards,
Mirjam

RESB Extraction with Delta

Hi All,
I have a requirement to extract data from RESB(Reservation) table. There is no create Date or Date field in the table.
My Question is:
1. How to extract data from RESB table with Delta option.
2. Is there any standard data source to extract data from RESB table.
Your earliest response will be highly appreciated.
Thanks,
Bsreddy

Hi,
well I'm not sure if there is a standard extractor but anyway, you can goto table aufk. There you have a creation as well as a change date. This might help.
regards
Siggi
PS: Additionally you might look here: http://help.sap.com/saphelp_nw04/helpdata/en/28/500b3c56488e6be10000000a114084/frameset.htm

Standard datasource do not work with Delta DTP

Hi,
0MAT_PLANT datasource is connected to an infoobject and a datastore
object. The DTP into the infoobject manage the delta but the delta dtp is not supported for the Datastore transformation.
The following message occure:
"Update mode 'Construct Opening Status' is usually not permitted for updating a DataStore object. With the update modes 'Initialization of the Delta Process', and 'Delta Update', whether an update to a DataStore object update is permitted depends on the delta process,."
When i create a specific extractor i do not face the problem.
Is it possible to use delta DTP to populate datastore with datasource using E delta process?
thanks for your help,

Hi Viermont,
Did you check the OSS Note: 973475 - No delta extraction for materials in ODS object
Symptom
During the delta extraction of data for the following DataSources, the system issues error message RSM1 113 ('Cannot update DataSource &1 to a DataStore object').
0MATERIAL_ATTR
0ARTICLE_ATTR
0MAT_PLANT_ATTR
0ART_PLANT_ATTR
0MAT_SALES_ATTR
0ART_SALES_ATTR
0MAT_ST_LOC_ATTR
0ART_ST_LOC_ATTR
In update mode, you want to update the DataSources with delta procedure E to an ODS object as the data target.
Other terms
RSM1 113, RSM1113, RSM1(113), ODS, delta procedure E, roosource
Reason and Prerequisites
The ODS object update is not permitted with delta procedure E for the 'Initialization of the delta method' and 'Delta update' update modes .
Solution
Carry out the following steps for the 0MAT_PLANT_ATTR or 0ART_PLANT_ATTR DataSources (for customers using the industry solution retail).
Carry out the same steps for the other DataSources, but use the following program in step 1:
0MATERIAL_ATTR or 0ARTICLE_ATTR --> Z0MATERIAL_ATTR_UPDATE
0MAT_SALES_ATTR or 0ART_SALES_ATTR --> Z0MAT_SALES_ATTR_UPDATE
0MAT_ST_LOC_ATTR or 0ART_ST_LOC_ATTR --> Z0MAT_ST_LOC_ATTR_UPDATE
1. Implement the attached Z0MAT_PLANT_ATTR_UPDATE program and execute it in your OLTP system.
2. Use transaction RSA5 to activate the 0MAT_PLANT_ATTR or 0ART_PLANT_ATTR DataSource in your OLTP system. Open the following nodes:
SAP-R/3 -> LO -> LO-IO
Select the 0MAT_PLANT_ATTR or 0ART_PLANT_ATTR DataSource and choose 'Activate DataSources'.
3. You can use transaction RSA2 to check the 0MAT_PLANT_ATTR or 0ART_PLANT_ATTR DataSource. The delta procedure should be NEWE.
4. Replicate the DataSource in the BW system.
To do this, call the Administrator Workbench in the BW system and display the DataSources for the relevant source system. Find the DataSource in the DataSource overview and replicate it.
Bye
Dinesh

CRM extractor 0CRM_SERV_PROCESS_H delta for ZZ-fields not working

Dear all,
We are experiencing trouble with a extractor 0CRM_SERV_PROCESS.
We have extended the extract structure of this extractor with an append structure containing some custom date and text fields.
When doing a full load or a delta init, all fields arrive properly in SAP BW. In RSA3 in CRM, everything appears to be correct.
When performing a delta update however, the custom fields appear as null in SAP BW while the standard fields are updated normally (null as in empty or 00000).
After browsing thru this forum and some sap notes (661340, 692195, 871930, 887724, 892022) I still haven't found a solution.
Does anyone have an idea of how to solve this?
Thanks in advance
Jan W

HI,
What is the logic you ahve used to populate the values for new appended fields ?
Is it BADi, User Exits or mapping module enhancement ? Value population to custom field code should be checked throughly.

Extractor with delta

Similar Messages

Maybe you are looking for