In Generic Delta By selecting 0CALDAY?

hello all
In generic delta,if v select 0calday as a delta type,after selecting this delta type v need to select a field for this delta type,should v need to select Time field only(like Creation date,Last date of creation or something like) or other than Time field like select Matnr,Ername or something like this?
Pl let me know that?
regards
balji

My pleasure!!
The following document should be very helpful for you.. i lik this paper very much..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
hope it helps..
regards,
Hari

Similar Messages

Generic delta - custom table in r3- help needed

hI ALL
I am using a ztable in r3 as data source . i wish to extract data from this table
to my bw ods as a daily delta . i have created a generic data src zds_ztable on the
basis of this table and in the generic delta section selected ' new and changed records' and 'numeric pointer'
options .
however , on the bw side when i try to create an infopackage under the relevant infosrc , it does not give
me an option for ' initialisation' or 'delta ' , i only have option for FULL loads , I know i can use a date
field and do a pseudo delta using technical FULL load ...but i want to know why cant i do an init and then
a delta the way we do for other data srcs....
pls help

Hi,
You may go to RSA2 for your datasource in R/3 & check do the delta settings are correct ? or you might need to re-generate the datasource and replicate in BW.
Eddo

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 problems

hai guys,
in generic delta having 3 options like numaric pointer ,
time stamp and 0calday
i have confusin when did select perticur option
plz let me know
waiting for reply
murali

Hi,
In case we dont have a business content datasource and the standard table also dont contain any field to register the latest change in time/day/numeric pointer ( for example sd billing plan data ) for that we need to go building a data source following the standard lo queue delta mechanism. To provide dela to datasource the association to a target syetm is required to store the dela queue as well as to extraction also.
Could you please through some infomation for doing the same.
Many thanks to all the Great Gurus.
Regards,
Jugal

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

How does the Generic Delta Works

Hi All,
Please let me know how the different types of Generic Delta works i.e. Numeric Pointer, 0Calday and Timestamp with one simple example for each.
Thanks & Regards,
Sunny

Hi........
There are three options for the type of the field determining the delta in a DataSource:
1. Time stamp - The field is a DEC15 field which always contains the time stamp of the last change to a record in the local time format.
2. Calendar day - The field is a DATS8 field which always contains the day of the last change.
3. Numerical pointer - The field contains another numerical pointer that appears with each new record.
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure.
The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read.
Leaving the value blank increases the risk that the system could not extract records arising during extraction.
Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.
A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction.
For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Extracted Data Delta Type
The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.
A distinction is made between the following:
1. Additive delta
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
2. New status for changed records
Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
Check this link :
http://help.sap.com/saphelp_nw2004s/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm
generic delta
Hope this helps you..........
Regards,
Debjani.............

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

Generic delta with time stamp

Is it possible to work with generic delta with timestamp without time chracterstics , and calday with out date feilds.
PLZ can any one provide reply to my thread.
Edited by: aumdeepa on Aug 5, 2011 11:47 AM

If it failed in BW (request is red) and you do a delta - system will ask to mark it a 'repeat' because the last one failed. When you choose 'repeat', it is going to let the extractor know that it is a repeat delta.
In this case, it will extract data from 25th to current date (both last and current delta).
Repeat delta will work the same, just that the lower and upper limits will be applied to the selection of the delta field.
Lower limit -> adjust back the lower selection value by this value
upper limit ->Adjust back the upper selection value by this much.
upper limit 1, lower limit 1 (by the way lower limit isn't usually applicable in real situations)
Ran delta on 20th first time
Select all data upto 19th (adjusted due to upper limit)
Ran again on 23rd
Select from 19th (ie 20 - 1 due to lower limit 1) upto 22nd (ie 23 - 1 due to upper limit)
Ran on 27th
Select from 21st (22 - 1 due to lower limit 1) upto 26th (27 - 1 due to upper limit) and so on.
Repeat delta will follow this logic but will also bring the selection that was executed in the last delta run.
Hope it clears.

Generic delta

Hi experts
i have problem in loading generic delta , Generic delta have three parameters
1.Time Stamp
2.Numeric pointer
3.Calender day
and also upperlimit and lower limit
can any one explain me about this parameters and how it works in generic delta
Thanks in in advance

hi,
Yes we have these 3 delta types.
timestamp is used when the requiement of data load is depends on time ie hourly based.
0calday is is used when the requiement of data load is depends on date ie daily based.
Numeric pointer is uesed if u want to load delta based on some fields like sales order,material order.
Lower limit and upper limit used for not to miss the records.
regards,
kundan

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

Doubt Reg Generic Delta "Safety Interval" Setting

Hi Experts,
I have a doubt regarding Setting "Safety Interval Upper Limit" and Lower limit in RSO2 for generic delta.
What does this setting imply?
If I do setting for calender day say both 1 then wht will be difference between delta before setting amd after setting?
Plz explain in terms other tham help provided...
Points will be awarded to say thanks..
Thanks in advance,
Sorabh

Hi Sorabh,
Here some SAP informations:
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure. The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read. Leaving the value blank increases the risk that the system could not extract records arising during extraction. Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00. A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction. For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Extracted Data Delta Type
The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.
A distinction is made between the following:
1. Additive delta
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
2. New status for changed records
Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
Check also examples in "How to... Create Generic Delta" under www.service.sap.com/bi.
Ciao.
Riccardo.

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.

Urgent: Problems in Generic Deltas by Function Module

Hi BW Experts,
My requirement is to extract text from CRM to BW using Zfunction module, copy of RSAX_BIW_GET_SIMPLE_DATA
which works fine for full loads but the problem arises only when i go for generic deltas. My code in FM for Deltas is:
LOOP AT s_s_if-t_select INTO l_s_select.
CASE l_s_select-fieldnm.
WHEN 'ZDATE'.
s_date_from = l_s_select-low.
s_date_to = l_s_select-high.
WHEN OTHERS.
ENDCASE.
ENDLOOP.
IF s_date_from IS INITIAL.
s_date_from = '20060401'.
ENDIF.
IF s_date_to IS INITIAL.
s_date_to = '99991231'.
ENDIF.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT * FROM STXH
WHERE TDOBJECT = 'CRM_ORDERH'
AND TDID = 'A002'
AND TDSPRAS = sy-langu
and TDLDATE between s_date_from and s_date_to
or tdfdate between s_date_from and s_date_to.
ENDIF.
FETCH NEXT CURSOR S_CURSOR
APPENDING CORRESPONDING FIELDS
OF TABLE wa_stxh
PACKAGE SIZE S_S_IF-MAXSIZE.
TDFDATE is creation date and TDLDATE is changed on
My extract structure contains Zdate(TDLDATE), Ztext1,2,3, Key field and langu in RSO2 I have selected calday in generic delta and Zdate as field Nm and upper limit as 1 and lower limit as space in settings and new status for changed records button.
Did I missed something because when i check in RSA7 i didnot see any changed records under totals column and i tried to load without it into BW than i didnot received single record evenafter changes.Would anyone suggest me the good solution for it I appreciate it in advance. I have seen lot of posts in SDN but I didnot find this type of secenario anywhere.
Thanks in advance
Regards
Kishore

Kishore,
go through the thread... which i provided for Generic DS using function for CRM Texts.
Re: Urgent: Extraction through function module
Any questions please let me know. If you have any questions update the thread with your mail id.
Replace the code with ...
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ZDATE'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_TDLDATE.
APPEND L_R_TDLDATE.
ENDLOOP.
OPEN CURSOR WITH HOLD S_CURSOR FOR
SELECT * FROM STXH
WHERE TDOBJECT = <Text Object>
AND TDID = <Text ID >
AND TDSPRAS = sy-langu
AND (TDLDATE IN L_R_TDLDATE
or TDFDATE IN L_R_TDLDATE).
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 wa_stxh
PACKAGE SIZE S_S_IF-MAXSIZE.
L_R_TDLDATE will be calculted by the system. Internally, system will save the Last Delta date(you need to enable this field for Generic delta).
all the best.
Regards,
Nagesh Ganisetti.

Regards Generic Delta

Hi Guys,
I have a small doubt regarding Generic Delta Extraction. In Generic Delta i choose Calday on Posting Date. And am getting data on Daily basis. Here My doubt is can I use this posting date in field selection in Info package. If not?Please give me clarification regarding the same.
Thanks,
Tg.

Hi Tg,
If I have understood correctly, Posting date has been chosen as the delta field in datasource.
I don't think you can use the fiield in infopackage selection because the field is used to extract delta for that generic datasource and the system doesn't allow us to put a filter on the filed which is responsible for delta .
If system wud have allowed us to put a selection on that field then correct delta will not be loaded in BI.
System can not allow us to play with deltas and hence the field is not avaialble for selection .
Hope it helps,
Manish Sharma

Generic delta has problem with delts pointer time stamp

Hi All,
We have generic delta data source with Delte pointer as Time stamp. We have not used any safety limits. We are loading the data to DSO and using Additive delta. But the problem is when delta flag is set, there might be a case where some records still being inserted to table with lower time stamp. These records are not being fetched in next delta.
We are planning to keep a safety upper limit of 5 min so that those records can not be missed. But we have a doubt as it is a Additive delta duplicate records will be loaded. If we make the delta to 'new status to changed records', it is going to work?? Any other things we have to check when we make this changes??
Thanks
Haaris

Hi
If you had selected additive delta then you can load data to DSo with addition mode only. No overwrite possible.
If you want to select new or changed status then you can load to DSO with overwrite mode only.
Additive or changed delta depends on your requirement because if you want to add data to the DSO then you can go ahead with additive otherwise you have to use DSO with overwrite mode only.
You can either give safety upper limit or lower limit but if you give safety lower limit then you can only load data to DSO with overwrite mode because there could be some duplicate records.
Hope it clarifies.
Regards
Sadeesh

In Generic Delta By selecting 0CALDAY?

Similar Messages

Maybe you are looking for