Generic Datasource Delta Settings Change

Hi Experts,
Currently the delta field in generic datasource is set to timestamp (LOCAL) and Upper limit is blank.
I need to change the delta settings to timestamp(UTC) or set the upper limit to 1000 seconds.
Can anyone tell me how to change this in production. Do i need to change this in dev and transport this to production.
If i do the changes to generic datasource, do i have to initialise the delta again?
Pls provide me the step by step solution.
Regards,
Anand

Ananda, What about the delta initialization? After transporting the datasource from R/3 dev to R/3 production, I have to replicate the datasource right.
In that case what will happen to my delta?.
One more thing incase i need to change only the upper limit value. Even for this, do i have to change it in dev and transport to production?
Regards,
Anand

Similar Messages

GENERIC EXTRACTION DELTA SETTINGS

HI Everyone,
                    I need to know how we set up Generic Delta in the following scenarios.
1) When we have a Generic Extractor based on a View and this View has multiple table(For Example 2 Tables to start with).
Then how wil you have the Generic Delta based on which field from which table? FOr example Table 1 has Header Data and Table2 has Item Data.Our Functional Consultant says Header can change or Item data can change.So we need to pick up the record based on the change in each of the tables. For Example , there is a field called CHANGED DATE(AENDT) which is present in both the tables. Now , in the view if I add AENDT from Table1, then Table1's chnages will only be updated i guess. What if the change occurs in TABLE2 (ITEM).
I dont know how to go about this. The solution is I created two Generic Extractors with two views (The only difference between the views is AENDT field coming from TABLE1 in the first extractor and AENDT field coming from TABEL2 in the second Extractor).But I think this is not the best way and there must be an alternative for this
2) The other issue is If I have a Function Module which Brings data from Multiple Tables, then how to select the field on which Delta is set.Do we need to write some Logic. After writing the logic, can we directly set the Generic Delta in RSO2 or is there any other way to do it.
Regards,
Samir

Hi Samir,
We too had a simliar requirement. In your case you can create a FM generic datasource on top of the view. The view in your case will get the intersection of the Header and Item level data. the main challenge was to get the delta records as we can have both Orders created and changed , and in Delta can be maintained on only one field.
To overcome this issue in the FM coding, Steps:
create Generic datasource, with Delta on changed on date (AENDT)
So during extraction you get the date on which the last Load was succesfully completed using the (AENDT).
So in the selection part use the statement similar to this:
      select * from vbap into table it_order where
                             ( erdat in l_r_erdat or aedat in l_r_zaedat ) and
                             ( erdat in l_r_aedat or aedat in l_r_aedat )
Sample generic datasource for your reference:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/403b299b-94e5-2c10-a3b4-e2cecb8ee869?quicklink=index&overridelayout=true
Hope this helps.
Regards,
Umesh.

Generic Datasource Delta upload Issue

Hi all,
I have created a Generic Datasource for Solution Manager ODS 0crm_process_srv_h which contains the userstatus, transaction number, transaction desc and GUID of CRM Order Object (ods key field),only these fields.
I have taken transaction number as delta field and it is as timestamp. But delta upload is not happening. If I give GUID or Status also delta upload is not happening . Please suggest which is the best way to give to delta upload.
Thanks and Regards,
SGK.

Hi,
in your case you need to create a function module as a extractor. Create a extract structure as well and add a timestamp field (lets call it zdeltahelp) to be used as the delta relevant field of the datasource. After successful init the last extraction timestamp will be passed to the fm and you can start selecting all resb entries for orders created and/or changed from that time on as well as the ones deleted (but therefore you need to read the change documents as well). For more information about generic extraction using fm search the forum or check out my business card. There you will find a link to a weblog about that issue.
regards
Siggi

Generic datasource technical settings: Data class : Transaction or Master?

Dear Experts,
I am not sure what is the difference in datasource technical settings (in R/3) : Data Class = Appl1 (transaction data) vs Data Class = Appl0 (master data).
The reason for asking is i have a z-table used as the table of a generic datasource and this table contains master data.
The Data Class is set as Transaction data.
It works. So, what is the difference if its set to Master data as the Data Class? Is there performance difference during data extraction?
Please advise.
regards
Pascal

Hi,
Data classes are assigned during table creation and are maintained in technical settings,
Data class: By choosing data class some space will be allocated to the table in the database when it is created.
Each data class corresponds to a physical area in which all the tables assigned to this data class are stored.
There are 3 main data classes:
a) APPL0- Which is the master data. Data which will be rarely changed.
An example of master data can be like name, employee number and telephone number.
b) APPL1-Which is transaction data. Data that is frequently changed.
An example of transaction data is the goods in go down which will change as per the purchases.
c) APPL2-Which is organizational data. Customizing data that is defined when the system is installed and rarely changed.
Example may be table with country codes.
By assigning the data class to the table we can retrieve the data very easily.
There are also 2 more data classes USR and USR1, which are provided for the customer.
These are for the user developments. The tables assigned to these data classes are stored in a table space for user developments.
Regards,
Durgesh.

Generic datasource delta enabling against S973 & S966

hellow gurus
m workin on BW 3.5
i have to create Generic datasource for Warrqanty FOC against Sales
for that i need to create a datasource using S966 and S973 View
could u plzz tel me
on which field should i make Delta enable in generic Datasource and
what shuld i selc in DATA-Specific Field -
and which radio button
Time Stamp
or Cal Day or Numeric Pointer
and
Saftety interval upper and lower limit for the same.
points will be awarded as my gesture and thanks for ur efforts
regards

Hi,
The following is the criteria that needs to be looked upon during Delta enabling in Generic Datasource.
Delta Specific Field :
Time Stamp - If you are extracting data for critical modules like FICO, go for Time stamp.
Calendar Day - If data is extracted from modules that does not have huge postings in a day, like Sales or Delivery Billing, go for Calendar day.
Numeric Pointer - For sequentially generated records like GLPCA, go for Numeric Pointer.
Safety Interval (Upper & Lower Limits) :
(1) If delta field is Date (Record Create Date or change date), then use Upper Limit of 1 day.This will load Delta in BW as of yesterday. Leave Lower limit blank.
(2) If delta field is Time Stamp, then use Upper Limit of equal to 1800 Seconds (30 minutes). This will load Delta in BW as of 30 minutes old. Leave Lower limit blank.
(3) If delta field is a Numeric Pointer i.e. generated record # like in GLPCA table, then use Lower Limit. Use count 10-100. Leave upper limit blank. If value 10 is used then last 10 records will be loaded again.
If a record is created when load was running, those records may get lost. To prevent this situation, lower limit can be used to backup the starting sequence number.
This may result in some records being processed more than once; therefore, be sure this DataSources is only feeding an ODS Object.
Regards,
Balaji V

Generic DataSource & Delta setup

Hello Folks,
I am trying to get my Generic DataSources and Delta concepts straight and got more confused after reading a white paper titled "how to ...create generic delta". I am on SAP R/3 4.6c and BW 3.0b.
This white paper talks about creating generic datasource and delta using RSO2 in BW. It explains how to specify delta-specific field and then select a delta type (AIE or ADD) which sets the "delta update" flag after generating.
My question is
1)should we create a generic datasource and delta from BW as suggested by this white paper and not in SAP R/3 directly using RSO2 and RSA3? what are the pros and cons.
I tried creating a generic datasource in SAP R/3 using RSO2 since these transactions are available in SAP R/3. I noticed the "delta update" checkbox was always(or for the cases I tried) blank and protected. Also noticed a menu item under "Datasource" called "setup delta" to be grayed out as well. So looks like, a delta can be set up in SAP R/3 but does not let me do it.
My question is
1) why can't I set up a delta?

Hi Jay,
First, you do not create a Datasource from BW. A Datasource is created in R/3. You replicate them to BW afterwards so that you can create/map them to Transfer Rules.
Datasource creation is in R/3 only. You can of course create BW as a source of data for other systems but thats something else.
Creating a GENERIC DELTA is based only on TIMESTAMP, NUMERIC POINTER and CALENDAR DAY. Delta Check box is really grayed out for GENERIC DATASOURCES because once you specify that your generic data source is DELTA capable by using any of the three options above as DELTA, then the Delta Check Box is automatically checked.
What Setup Delta are you referring that you cannot do?
--Jkyle

Generic DataSource - Function Module Changed

I endup changing a FM that is feeding the Generic DataSrc.
The BW side is a ODS with data loaded from multiple requests using the Generic DS.
What are my implications after the change; Do I need to have a full load or Init or ...
Thanks.

Hi Gopi,
it depends on what you are looking for. If the new addition fields are not needed for the history, then the current one should n't cause any issue.
But if you are looking for the history of the new fields, then you should consider having the full load.
Secondly, as you have changed the EXTRACT on R/3, it could give you an error like version on BW is old or something like that. For this, Replicate the DS and hence execute this program "RS_TRANSTRU_ACTIVATE_ALL" to activate the trans structure.
Regards
GPK.

Generic DataSource using FM - Delta doubt

Hi All,
I have few doubts on Generic DataSource Delta.
I am working on one HR requirement. where I need to pull the Mandatory courses information.
to get this done, we have created one Generic DataSource using Function Module.
FM has huge and complex logic, at present it is taking long time when I run in RSA3, if I continue with this to BI, daily running FULL load to BI is not suggestible, because it takes much time to load.
I have planned to set the Delta, just want to know what would be the best option to set the delta option for this requirement? and how? I have 2 dates (Course Start and End dates), Employee, Course Id, Course Type, Position, Job, etc in my DS structure.
Please suggest someone so that I can do FULL load once in BI and continue with Delta without missing any delta records going forward.
Regards,
Kiran

Hi,
In mystrucure used dates are not relating to aedat and erdat, they are CHAR type. here the requirement is little different.
Regards,
Kiran

Delta settings in Generic data source

Hi experts,
I have created a generic datasource based on infoset query i,e the table KONV (Cluster table).
I maintained the delta settings in rso2 as follows:
Delta specific field : KNUMV Doc condition number.
Calendar day.
Safety interval upper limit: 1 Calendar days.
New status for changed records.
Are the above settings correct ?
Regards,
Nishuv.

Hi ,
befor creating the data source U need to create the infoset in r/3 (the sap query). SQ02 is the tcode for creating the infosetquery.
hope it will help u sahu.
Jay

Delta issue on a Generic Datasource

Hi
   I had a Generic Datasource on a Z table.
   The Z table had a Date field on which Delta is based.The Postings are performed manually.
How to solve the delta issue in the below scenario.
Ex; A user made a manual posting with a date 09AUG2010 today and delta is extracted to BW.
    But tommorow a used made another posting with a date 14JULY2010....
Currently that record is not being extracted....how can i resolve this
Thanks

Hi,
Once the data source is created you will extract the data till that date and as the delta is set it will fetch the newly updated records .But i dont think one can post with the back dates in R/3 side.
If i'm not wrong if you are asking regarding record got missed out them wht need to be done?
Then do the repair full request and pull the missed delta records and it wont effect the delta settings.
Regards
KP

Generic Datasource on table IMRG in R/3- delta on timestamp is it ok ?

Hi
I am creating Generic datasource based on table IMRG in R/3, This has stoppages related data. which we need in BI report. There is a field for Time-stamp in the table, i have checked values in table IMRG, but in R/3 it shows no data for the time-stamp.
Now i want to create delta basis for this generic datasource based on table, so shall i create delta based on time-stamp or date field.
If I create delta based on time-stamp will it create problem in delta extraction subsequently? Please share your experience in such a cases.

There is a field for Time-stamp in the table, i have checked values in table IMRG, but in R/3 it shows no data for the time-stamp.
Delta specific field should be something which defines changes in your table, not something which is blank always.Based on the change in this delta specific field only delta will be pulled.Having it blank will never pull you delta.
Hope this helps.

How to deal with delete record in generic delta of generic datasource

Hi,
Anyone can give me suggestion about the delete record in generic delta of generic data. I need extract data with a generic datasource and hope deleted record in datasource also can be "delete" in next delta extraction. I do a test with generic delta. It seem that the delete record can not be updated in ODS. but updated record can be updated in next delta extraction.
How dose BW generic delta deal with the deleted record with generic delta mechanisim? Or how can I use generic delta mechanisim to realize that BW "delete" the deleted record of source system in ODS with delta extraction?
Thanks in advance!
Billy

Delete is not supported in delta mechanism of generic delta extractor. You will need to add a workaround for that.
- Capture the deleted records somewhere (maybe enhance the txn deleting the record so the key is written to a Z table). Take these records to BW and manipulate the recordmode to affect deletion of corresponding record from ODS.
- If your generic delta is based on FM, and if the 'delete' is captured in change document tables, add the logic to check change document tables whether any records are deleted, and if yes, send those to BW with appropriate recordmode to achieve deletion.

Delta enable generic datasource

hellow sir ..
im workin on SAP BW 3.5
i'm creating the generic datasource ,, so my confusion is how to make it Delta enabled because The check box for DElta is Greyed...
so wat;s the diference between delta box checked and unchecked..
how to make that grey area checked..
thanks and regards

u r talkin about Generic Delta Tab.. where 3 option s are there,.. - YES
so wat options i shud go for.. so that it enables Delta upload at BW side. - This will not enable delta loading at BI side it will extract delta records from R/3 only, for activation BW delta you have to create a delta infopackage that will extract the delta records from R/3 to BI.
and there are 2 more options in Radio button
- Filed name : Here u specified based on which field ur delta records wil be picked up, like change date field (field name : ERDAT) then specify the name of field, as its a date field so choose the Radio button CAled day. If it had been a time stamp filed u have choosen then Timestamp radio butoon.
1) New status for change Records
2)Additive Delta..
For above read F1 help (that is very clearly explains this)
and what is the DElta check box which is there in Selection and Hide field Tab,, which comes after Saving the First Screen of RS02 ( DATASOURCE : Customer Version Edit ) - This box will become checked when u maitain any delta field in Generic delta tab. It indicates wether the datasource is delta enabled or not
Hope this is clear now.

How to Add delta functionality to generic datasource

Hello all,
My requirement is to make a Generic Transactional Data source Extractor to Delta enabled.
The datasource doesnt contain either of the following delta enabling functionality
-> Date
->time stamp
->Numeric pointer.
Could anyone suggest idea how to add these in Generic Datasource so that it can be delta enabled
regards
Bala

Hi Bala,
Coding should be done checking th trasaction and the tables.
but i can provide outline .
add a field last changed on and write a code saying last changed on is equal to sy-datum.
i am not sure of the scenario where to write this code and after which line.you can take a decision.
check the link below
https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c062a3a8-f44c-2c10-ccb8-9b88fbdcb008&overridelayout=true
Regards
Joga

I am using generic datasource first time init sucessful, next time deltas

Hai ALL,
I am using Generic Datasource first time i run init next time i want to run the delta, delta is sucessful but 0 records. i am taken date field and new status fileds(DSO) for DSO. R/3 side table values chaging but not replicate to BI. Can any suggest how to run the delta for Generic Datasource.
Thanks & Regards,
Suresh

Hi
Have you set delta pointers in your Generic datasource? if yes then what it is ? try to see if its logically related with your changes in records or you need to use any other type of delta pointer.

Generic Datasource Delta Settings Change

Similar Messages

Maybe you are looking for