Generic delta view

i am trying to create a view from the EINE and EINA.when i try to create generic data source using this view i am getting an error "invalid extract structure template" when i double click on this i am getting an error message"Quantity and currency fields refer to a different table" whether i should add that table in the joins? how to create the data source
regards
rajan

You do not have to add the table in the joins. But you have to append the currency or unit field to the extract structure. Then specify this added field as the currency field for the main value field in the extract structure.
This should solve your problem.

Similar Messages

Generic delta extractor on view with ALE

Hello.
Extractor 0RT_WRF1_ATTR has type V and generic delta setting Numeric Pointer. Generic delta field is empty. Delta Process = A (ALE Update Pointer (Master Data)). ALE delta setting includes all fields of extractor structure. But changing one of these fields doesn't push new records into datasource.
Can you please explain, how generic delta works with ALE pointers аnd why no data is delivered?

CC,
Check on deletion data available in table(with any indicator updated) or not available in table.
If not available, you can not get delta through generic datasouce.
Hope it Helps
Srini

Problem in getting Generic Delta records to BW

Hi BW Gurus,
I have got one issues with which I have been struggling a lot for several days . i.e
I am extracting data from R/3 using Generic Extractor (View) from CATSCO and CATSDB. At the time of delta, I tried using Personal No with Time Stamp giving Upper limit as 1800 seconds. I executed Infopackage in BW immediately. But it didn't work out. So plz guide me how I can get Delta Records to BW. Or should I do any necessary factors apart from these in Generic Delta Screen (RSO2).
It is very urgent.
I will be thankful for solving this issue.

Hey I am "Intros" again,,
I am sorry man for giving the wrong T-code mistakenly in my last reply..
To solve the proble...the whole process is same what I told u before..
But... you got to go to T-Code : BD87 , then execute the IDocs manually to bring them in to BW
identify your IDocs which are missing in Monitor screen, then goto BD87 and select those IDocs and click execute... )you can search the IDoc's based on selection conditions)
I hope this will help u...
cheers man..
---Intros

Regarding generic delta.

does any sap bw gurus know the answer to my doubt.
i have created 3 views from mm tables (EBAN,MSEG,MKPF,GLPCA) AND FROM THESE 3 views i have created 3 generic data sorses in r/3 dev server and transported to r/3 quality server and loaded from r/3 qlty server to ods with full update mode in infopackage.
now i want to load delta records for those geeric data sorses, what is the procedure. i have not selected the delta option while creation of data sorses but loaded into ODS with full update.now i want to get delta records, what is the process?
Suppose i have selected generic delta and given some field to get delta records in r/3 dev server, does it effect in r/3 qualty server or do i need to transport same recquest or new recquest for delta from dev to quality server?
this is very very urgent pls. points assigned.

Hi,
ODS may not let you load deltas if there are Full loads already loaded. So either you have to delete them or make them into Full repair using FM RSSM_SET_REPAIR_FULL_FLAG.
This you can decide after talking to users, if they are ok with the data unavailability during the reload, you can delete these data.
Then perform the changes (delta DS) in the DEV and transport it to QUAL.
Then the usual procedure, replicate in BW, perform init load and start deltas.
Hope this helps.
Thanks,
JituK

Problem in extracting Generic Delta Records

Hi BW Experts,
I have an issue. I am using Generic Extractor using View from Tables CATSCO and CATSDB. At the time of Generic Delta, I am using the field PERNR(Personal Number) to use Generic Delta. I am using Time Stamp. For this I have selected Safety Interval Upper Limit 100 seconds.But now I am testing whether we get delta records or not. But I am not getting records to BW. They are changed in R/3. So please guide me whether I should use Calday or Time Stamp . How can I get delta records to BW.For testing , I am executing InfoPackage immediately after changes in R/3 like for two or three minutes. Once I will be sure on getting records to BW, then I can move to Production where we execute process chain at 1:00 a.m
there I can use Calday giving Safety Interval Upper Limit as 1 day. Considering the above factors please guide me .
I will be thankful for solving my issue.

PERNR doesn't contain a date right? so timestamp tells the system PERNR is a date field... That will never work.
What kind of value does PERNR contain, is it an incremental value that adds up at every new entry?
Generic delta needs a field that changes in a way that can be predicted.

EKBE table for Generic Delta

Hi Gurus,
Good Day to all. I just like to inquire some details for creating generic datasource with delta enabled. I have created a view table with fields from EKBE table, and created generic datasource that reads the view table I have created from EKBE, now it needs delta process with CPUDT as delta specific field name, seeing the data type of CPUDT, it is DATS with 8 length.
I would like to assure if what will be use as marker of delta, timestamp utc, timestamp local, calendar day and numeric pointer?
And if I use one of the above, what settings that needs to be use for the safety interval upper and lower limit?
Thank you for your inputs and really appreciate it.

Hi,
use the CALDAY as a generic delta pointer.
i would like to recommend as: Safety Interval for Upper Limit as 1 and Safety Interval for lower Limit as ZERO
i think your are using the DSO as a staging layer no worry about duplicates.
Thanks,
Phani.

What are the disadvantages of generic delta extraction

Hi all,
what are the disadvantages of generic delta extraction.
how function module generic extraction works.
Thanks,
Madhu.

hi madhu,
Pls refer ths,To learn more about Generic Extraction pls read BW350 book.
Gereric Extraction can be done in 3 ways.
If you go to transaction RSO2 in R/3 side, provide tech name for data source and click create.
you will get the 3 options.
1)From a DB Table
2)From a DB View
3)From Functional module/ Infoset Query
in first option you can directly give a standard or custom build talbe name. in second option you can select the necessary fields from more than one talbe(eiter standard or custom). In third option you will create a function module or Query to extract data. When creating function modules you can use standard function modules as a template e.g. RSAX_BIW_GET_DATA_SIMPLE.
see weblog : /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
If you want to enable delta for generic extractor you choose the option delta and provide necessary settings.
Generic extraction is when your extraction is not satisfied by either BC or LIS/LO. It can be using a view / query/table/FM
Here the changed records can be isentified by :
1. Based on the date of creation or last change ( Delta based on 0Calday)
2. Based on the record number ( Numeric Pointer )
3. Based on time of change ( Timestamp)
real time examples would be
1. Master Record creation like customer ID creation
2. Timesheets in SAP PS
3. Invoive details / Sales Order Details.
Pls check this web logs for clear Idea.
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Have a look at these threads too.
Tables
Transfer Structure
The steps for creating extractor using Function Module.
1. Create new Function group (if you have already not done so) in Se80
2. Copy Function module "RSAX_BIW_GET_DATA_SIMPLE" with suitable name.
3. Change the code that populate data.
Following table may give you the guideline for parameters.
Parameter Description
I_REQUNR (import) BW provides this request identifier. It is a system-generated identifier in the form REQU_XXXXXX. BW uses this same identifier in all function module calls that relate to a single load.
I_DSOURCE (import) The name of the generic extractor
I_MAXSIZE (import) The maximum number of records that BW expects to be in each data packet
I_INITFLAG (import) A Boolean flag that indicates if this is the initialization (first) call to the function module
I_READ_ONLY (import) A test flag not needed in most extraction scenarios
I_T_SELECT (table) This table holds any selections from the BW InfoPackage. The function module should examine these selections and only return data that matches the selections.
I_T_FIELD (table) This table holds the fields that BW requests
E_T_DATA (table) The function module fills this table with data records. These records then return to BW as data packets. This table has the same structure as the extract structure defined in the generic DataSource.
NO_MORE_DATA (exception) The function module raises this exception when no more data is available
ERROR_PASSED_TO_MESS_HANDLER (exception) The function module raises this exception if an error occurred during the extraction. It alerts BW to check for error logs.
Change following code to put the selection fields
Select ranges
RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
L_R_CONNID FOR SFLIGHT-CONNID.
Change following to populate data
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
WHERE CARRID IN L_R_CARRID AND
CONNID IN L_R_CONNID.
ENDIF. "First data package ?
Fetch records into interface table.
named E_T_'Name of extract structure'.
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS
OF TABLE E_T_DATA
PACKAGE SIZE S_S_IF-MAXSIZE.
Some more links:
Re: functionmodule
Re: FM for G. extractor
with hopes
Raja Singh

Generic delta; When R/3 record deleted.

Hi all
Please tell me What will happen to the BW record when the record in R/3 add-on table is deleted and the data is retrieved by generic delta.
(1)At the beginning.
R/3                         BW
20051124000001   100$   -> 20051124000001   100$
(2)Then, R/3 record deleted.Does the record on BW will be deleted or remain in same?
R/3 record deleted      -> BW record also deleted
                        or
R/3 record deleted      -> 20051124000001   100$
                            remain in same
Now, I cannot access to BW; I couldn't test by myself. So, I wish someone help me.
Ken'ichi

Hi Ken'ichi,
Refer these posts on RECORDMODE:
Re: ods- 0 Record mode
Re: 0RECORDMODE Question
A generic datasource can be based on:
1. View/Table
2. Function module extractor
3. Infoset query.
You would find many links on the same topic in these forums. Kindly use the search option.
Bye
Dinesh

What type of generic delta to use and what field?

Dear BW Gurus,
I am creating a generic datasource based on a view BSAK and BSIK (Accounts Payable tables). I am not able to determine what type of generic delta (numeric pointer, calender day or timestamp) should i use and what field in the table should it that be based on? All or any help is greatly appreciated.
Thanks
Raj

CALDAY on field BLDAT (in both tables) seem an obvious candidate.
Added - You will need help from functional people (or you can try it in ABAP forum) to determine which date field is updated with the system date when these tables are updated with SAP txns (some hint can be had by looking at the data)- the fields of interest would be -
BUDAT
BLDAT
CPUDT
It is almost certain that CALDAY is the only option you have for delta type, and one of these three fields will have to be chosen.
Message was edited by: Ajay Das

RDA enable option in Generic Delta

Hi,
Where do you see RDA enable option in Generic Delta in both the cases R/3 4.7 and ECC6.0? I didn't find the enabling option. Could anyone tell me any settings need to be done before it enables. Whether RDA enables for Generic Delta? If yes what method SAP recommended to use among table/view, FM, or InfoSet Query?
Thanks & Regards,

Hi Lathika
to enable RDA option go with WEB Service data sources in the data source-Extraction tab you can see the option Realtime where you can find RDA suppoted
but wen creting the infopackage you need to assign the daemon to that and assign your DTP which loads further targets from that data source also to the same daemon and mention request losing settings in the info package
for example if you mention the request closing time is 1 hour that particular request will be opened for 1 hour the deltas that are posted in that 1 hour will fall in this request
after the request automatically will set to closed
Thank you

Generic Deltas vs. LO Deltas

Dear All,
I am learner of SAP BI/BW I have one query mentioned below
1) I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
2) When did you go for Function module and let me know the real time scenario which you faced.
Regards,
Divyesh

Hi..
1) I would like to know the difference between Generic Deltas vs. LO Deltas u2013 when we used to prefer both the Deltas.
Generaic datasource is something which you create when the standard ones doesn't fulfill your requirement.....
To make it delta enable you should select some delta specific field.......which will work as a timestamp.......which will record the changes based on which the new or changed records (delta records) will get fetched......
You have to do the init......and then you can execute the delta.......
Here you are directly fetching data from some Application table, view, Infoset........
Or if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
Now...LO deltas are different........here Set up table is mandatory..........because it cannot access data directly from the Application table......
First, you have to fill the set up table..........then run the init.........once the init is done..........after that changes will automatically get recorded in the Delta queue........but here also once catch is there........
Different Update modes are there...........if it is a Queued delta or Unserialized V3 update ..........then the changes and new records will get stored in the Extraction Queue(LBWQ) and Update table (SM13) respectively............then you have to schedule the Collective run in LBWQ to pull the records in RSA7..............only in case of Direct delta changes will directly get recorded in RSA7........
2) When did you go for Function module and let me know the real time scenario which you faced.
if the logic is complex..........means you have fetch data from multiple table you can go for a Function Module......
For an example..........for FI logic is quite complicated.........business specific.......if you just create a view it will not fulfill the requirement.........you will have some business specific logic..........
So in this case you have to go for a FM......
Regards,
Debjani....

Generic delta not working with '0calday' change pointer

I have created a generic datasource based on a database view and extracted data with afull load infopackage into BI. Then, I configured the generic delta with a date field and 0calday type. Set the safety interval of 1 day as a lower limit. Saved the datasource in R/3 and Replicated and activated the datasource in BI. Done some changes to a record in R/3.
After that, I created an Init delta infopackage (with data) and extracted the data with the same number of records as extracted in the full load. Note that all these were done on the same day.
If I have done something wrong by doing it on a same day, I should get 0 records.
Why did I get the same data with a delta init package? I wonder the generic delta is configured correctly or not? Please tell me where I have gone wrong. Thanks..

Hi Shiva,
While running the delta init, you have option of without data transfer and, with data transfer.
I am sure, you used with data transfer and thats why got all those records same as full load.
U can use different options like.
1. DO the init without data transfer and then do the full load, and then run delta everyday for delta records
2. Do the init with data transfer then no need to do the full load and the subsequent delta will take care day onwards,
I guess your are good to do the delta load by tomorrow.
Thank-You.
Regards,
Vinod

Generic Delta with numeric pointer (Without safety interval and no field)

Hi
We have problems with Generic Delta extraction. Our previous Dev has created the data source with numeric pointer as the data source without any safety interval and without any field for numeric pointer selection even we have the date field (creation and change dates in view)....
He created the generic delta with numeric pointer and Additive delta selection on top of view (EKKO,EKPO and EKKN). So we are missing lot of records. Now I need to fix this asap, I have done generic delta with timestamp and cal day with change/creation date.
Now in order to fix our delta loads should I use the cal day as the delta pointer with change or creation date already available or is it ok to use numeric pointer with additive delta and safety lower limit as 10 or 20 with upper limit blank?
Also Should I use any field in the field nm section or is it ok to leave it blank ? Please advice...
Note: I checked the missing delta records in ECC and the change timing is in the afternoon and our load time is only night...We also have several other data sources with same settings (numeric with no safety and no field) but it is not giving any issues.
Thanks
Edited by: ganesh uttitti on Jan 26, 2011 10:33 PM

Hi Ganesh ,
I'm a little confuse,Why are you not use LO Delata for it?

Generic delta creation with Extractor Starter Kit - BW Datasource option

Hi Rajesh, Rohit,
As per the wiki, http://wiki.sdn.sap.com/wiki/display/CPM/FAQ-DataExtractionforSpendPerformance+Management, the question:-
Do these starter kits have any support for delta (periodic data updates) after the initial load is completed?
A. Yes. Deltas are available (for all source objects that support delta mechanism) in both of the extraction options. You don't need to reload the full set of data, when you perform the periodic data updates.
I understand you can use the date range but this in my view is still a full load. We understand that you can create your own generic datasource based on the generated function module generated by generating the object, for e.g PO.
We have tried to do this for the object PO, thus the following:-
rso2 > create a new transaction datasource > base on generated datasource (Z_SADSERPPO) and use it's fm and extract strucutre :- Z_SAERPPO_DS fm , ZEXTR_ERPPO extr structure
When we goto to create a generic delta based on DATE_RANGE we get the error message ::-
Z_PDPOTEST: TABLES-paramter E_T_DATA for extractor Z_SAERPPO_DS is missing
Can you create a blog around this as we understand other customers have managed to create these deltas?
Best regards,
Pom

Hi Claudia,
That's fine, please continue to use the Z_SA_DEPD to generate the datasource. If you then do a rsa2 on this datasource, you can see the underlying function module and the extract structure for this which is also fine.
The bizarre thing is that through rso2 for this generated extractor, you cannot see the fm associated for this, hence why the generic delta is not working.
What we thought of doing and in line with the sap recommendation was to create a new transaction datasource from tcode rso2 and base it on the above function module and extract structure, but when we goto choose the date_range as the generic delta, it doesn't work and gives the error.
Am still waiting an answer.
Will keep you posted.
Thanks,
Pom

WHAT IS GENERIC DELTA

Please explain me what is generic delta and how to create generic datasource for transaction data?

Hi,
Generic extraction
Usage:
1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
3. FI-SL requires generic extractors.
How:
You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
Steps
Log on sap R/3.
Step 1. create a table or view for generic extraction in se11.
Step 2. Goto t-code RSO2
Step 3. Here u have to decide whether to extract transaction data or master data attributes or texts.
Step 4. suppose if u have opted for transaction data,then give name in the column ex:ztd_m(data source name)
Step 5. select create button,this will take u to another screen.
Step 6. Here u have to decide from which application component u r extacting data.Ex: SD,MM,..
Step 7. in this screen u have to fill short disciption,medium,long( these r mandatory).
Step 8. then U have to Table name or view name which u have created in se11.
Step 9. I f u want to maintain generic delta then u can select generic delta in top left hand side corner.
Step 10. in next screen u have to give some field which is primary key.
step 11. here u to specify whether time stamp or cal day or numeric pointer depending on u r requirement.
step 12. then u have to specify whether new status for changed records or additive delta.
If u choose additive delta ,then u have to load data to infocube or ods object.
If u choose new status for changed records, then u to load data to ods object only.
Step 13. then save it.
Step 14. then logon to sap bw ,then replicate the data source then as usuall.
Refer:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-db
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b0
http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
Thanks,
JituK

Generic delta view

Similar Messages

Maybe you are looking for