Generic Delta Extarctor has a field inactive

we have created a generic data source in which we have a delta for this field ERSDA and we also need selection in the infopackage for this field but the selection option in the data Source is inactive
it is inactive becuase we are having delta for that field
Can any one tell me how to make it active.
Thanks
Nagesh.

Hi nagesh,
if you have used a feild for delta pointer in datasource, we cannot have the same used for selection.
This is because, we are doing a selective identification of delta records and the same one cant be used agian to do a selective loading.
regards,
naveen

Similar Messages

Generic Delta based off TimeStamp field is extracting full load

I have a generic delta in place which is extracting a full load every time instead of only extracting the changes.
I have created a generic delta based off a timestamp using a "Last Changed by" field of type Dec15, format YYYYMMDDHHMMSS.
This datasource is populated via a FM which is only used to update two fields, all other fields (including last changed by field) are taken straight from the source table. Entries to the last changed by field are entered like this:
20080310021530, then show up like this: 20,080,310,021,530.
All relevent entries are showing in the tables ROOSOURCE, ROOSGENDLM, and ROOSPRMSC. There is also an entry in RSA7, status Green, Total = 1, and Status is showing the correct Delta relevent field as well as the correct timestamp of the last extraction.
The entry in ROOSGENDLM contains:
Current Pointer Repeat Pointer
20080320091503 20080320091653
Yet every time I extract a "delta" from BI, it pulls a full load.
Does anyone have an idea of how I can get the generic delta to work properly? I'm using 7.0 transformation/DTP. This field in BI uses a routine to convert the timestamp to a date field. Any help is greatly appreciated.
Thanks!

I think I found the issue. This timestamp is UTC timestamp, and until we implement SP13 (which is being onboarded in a week), this type of timestamp is not delta-relevent. Only timestamps on the local application server are delta-relevent pre-SP13, which can cause issues if the time is updated in a different timesone (to the east) of the application server.
The following note corrects this issue:
1073871
Edited by: Cote Adams on Mar 20, 2008 4:59 PM

Problem with functioning Generic Delta

Hi Expert !
I Have Created a Generic Delta and has Scheduled the Delta Load By Means of Process Chain In BI Side.
Although it is showing Green(OK) status for the respected Request at PSA(saying No Data Exists FOR PSA) and ODS Lavel but no data is loaded at ODS.
although the data for the same crieria is available in R/3 side.
please share your idea what is reason behind........
Regards
Prakash

Hii I have created Generic Delta On Function Module, also i had checked in RSA3 and it is showing data. Also I have checked the Function Module and the field on which i had created Delta, the Delta Parameters is coming.
I am not able to find what actually the problem is........
Please share your idea if you have any.
Regards
Prakash

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

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.

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?

Two fields for generic delta

I have to create one data source which will contain two fields for generic delta...extraction of data will be through FM.SAP provides a standard functionality to create a generic delta. This can only be build on one selected field.
The logic of the functional module is based on two fields: ICRDT (creation date) and IUPDT (change date). The module should look for both day because when a new records is created the change date does not get populated in R3.
Can anyone pls help me out?

Hello Siggi,
i have to create an delta enabled extractor for a database table.
The database table (=EAUS) contains the fields "ERDAT" and "AEDAT".
I'm a Newbie in ABAP und so i read some blogs, articles and how to do papers here.
But my tests haven't work:
1. I created a structure in SE11 for extraction. The structure contains all the of the database tabel (=EAUS)
2. Then I created a data element "ZDATE" in SE11. I integrated ZDATE in the structure.
3. Then I copied function group "RSAX" and function module "RSAX_BIW_GET_DATA_SIMPLE" in our namespace.
4. I used the copied function module as a template and adapted the coding in the function module. The coding is from the paper "Functional Module Based Delta Enabled Generic Datasource"
But i doesn't work. My deltaenabled generic datasource doesn't get the deltas. In RSA3 with update mode "D" no data records were selected. (I create new records in the database EAUS before I checked the extraction). The update mode "F" and "C" works.
Can you help me and send me the coding of your function module?
Many thanks!
Jan

Appended field is missing in field list of generic delta

hi all,
i appended the generic extract structure in RSA6 and uncheck the hide box.
now im unable to see the zz field in the field list in rso2 to set up generic delta, any ideas...
Thanks,
GK

Hi,
First check the asset Scr.layout rule for asset class by using path -
Spro>Financial Accounting>Asset Accounting>Organizational Structures>Asset Classes-->Define Asset Classes
Select your asset class and check - asset Scr.layout rule .
Then go to -
Spro>Financial Accounting>Asset Accounting>Master Data>Screen Layout-->Define Screen Layout for Asset Master Data
Click on - Define Screen Layout for Asset Master Data
Select your Screen layout which you got earlier. In Logical Field group select 'Inv. account assignment'. and double click on field group rule.Then make required changes in 'Investment Order' as required - Required, optional, display.
Then check asset master data in AS02.

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

Generic Delta with Timestamp Field

Dear SDN Team,
We changed one of our HR datasource from FULL to DELTA with Timestamp(TMSTMP)-Time Stamp(UTC).
Which Delta we need to take Timestamp(Local) or Timestamp(UTC)
Our Generic Datasource is based on Function Module.This data source contains HR Hours Data i.e Direct Hours & Indirect Hours.
With interval settings has
Safety Interval Upper Limit - 'Blank' .
Safety Interval Lower Limit - 1800
New status for Changed Records (Selected)
It is a HR Generic Data Source.
We are creating the records in PA30,PA40 and going to take the records from PA0000,PA0001
Delta type for this DS is "AIE" as our delta type process for our DS.
I am trying to load the INIT to Cube,but its not allowing to load,saying with 'AIE' delta type its not possible to load to cube.
I changed the delta type to 'ADD' then the safety interval limits changed to
Safety Interval Upper Limit - 1800 .
Safety Interval Lower Limit - Blank.
Additive Delta (selected)
Is it possible to load the Generic Delta Time stamp to Cube?
Please let us know what are the settings & delta type needs to be there to load the Generic Delta Timestamp to Cube.
Your suggestions are really appreciated.
Thanks and Kind Regards,
Lakshman Kumar G

Hi,
We used TMSTMP filed with Data element TZNTSTMPS with data type DEC Length 15 in Function Module & Extract Structure.
Default filed name is TIMESTAMP_UTC,Domain is TZNTSTMPS.
Generic Delta -
Filed name - TMSTMP
Timestamp (UTC) selected
With interval limits
Safety Interval Upper Limit 1800
Safety Interval Lower Limit
New Status or Changed Records selected.
Thanks and Kind Regards,
lakshman

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

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.

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

How to Create a Generic Delta Datasource

Hi All,
I have created a extractor thru RSO2 using a table.
The table consist of a time field which i set it to the timestamp field. After initlializing the delta upload successfully, when i run delta upload, no data has been uploaded even having made changes to some of the records.
Why is it so? Kindly advise.
Does the timestamp field have to be a datetime field or it can be any field of any data type?
Thanks in advance.

Hello Bill,
I have checked RSA7 and my datasource has the status of green. I have set the upper level to 900secs. After the init load, i waited for more than 900secs before i do another load but it still comes out as 0 records. Is there anything else i need to do?
I'd like to clarify one thing, is the timestamp field's data type suppose to be a decimal of length 15 field? Mine is currently a DEC15 field which is also a packed field. When i used F1 at the generic delta screen, it told me that the timestamp field should be a dec15 field. Is it correct?
Thanks, Bill!
Message was edited by: Shunhui Chua

Generic Delta Extarctor has a field inactive

Similar Messages

Maybe you are looking for