Delta in Generic datasources.

For the generic datasource. I have to run Delta multiple times per day. In this case I hope that, TIMESTAMP is the suitable option to run delta. Here, to set up TIMESTAMP, I have to select the field name for Delta, based on that field name the delta will work and pick the records into BW side.I have 2 fields DATE and TIME to set up delta. I have given field DATE for delta.
For example.The data in the source system is
      IC            DATE                    TIME
      XX           22/03/2009           09:30:41
I will run delta on 22/03/2009, 10 AM , then the above record will go to BW successfully.
At 11 AM one more record will be added into the source sytem on the same date 22/03/2009. Now the data in the source system is
IC            DATE                    TIME
XX           22/03/2009           09:30:41
YY           22/03/2009           11:00:00
Again, at 11:30, I will run delta to pick the 2nd record. Here my doubt is, will that 2nd record be picked into the BW?. I doubt that, as we have set up delta based on the field DATE, Will the 2nd record will be picked into the BW side or not?. If the 2nd record will not be picked into the BW side.
How can I achieve this. But, I need to run multiple times per day and need all records.
Please let me know if you dont understand.

Hi,
I understand your requirement, as you are using date as delta specific field you would not get another record created on the same day. To solve it you have two options,
1) Field with date and time combination. - e.g 20090317164909.
2) Or can you use time field as delta field.
Any of above can solve your problem.
Hope this helps.
Regards,
Viren
Edited by: Viren Devi on Mar 22, 2009 9:11 PM

Similar Messages

How to catch the delta of generic datasource created on table EBAN?

Hi Guru,
I am facing a problem about the delta of generic datasource i created on table EBAN.
when I convert a PR into PO, this PR was created several month ago, this PR will not be caught into delta package.
how to get this PR again after it was converted into a PO?
many thanks.
brgds/steve

hi,
If you have any fields(calday,timestamp,nemric pointer) in your table , using this fields any one we can enable delta.otherwise one option is there but your table is small valoum of datas.
first data load(full) r3 to bw side cube,then using open hub service download data from cube to any file (excel ,csv) then r3 side create one table using that flat file, then load download file to r3 new table using (LSMW - tcode r3 side).
now compare your genric extroction table and new table using ABAP coding , then you have any new record or changed find update new table first then BW side .
using this type we can enable delta for genric extrocation.
regards,
sundar.

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 in generic datasource

Hi all,
In case of standard datasource, the document posted in R/3 is written to BW delta queue. Generic datasources don't support delta update directly but support generic delta. Can you pleasce clarify what exactly happend in case of generic datasoure.
Thanks in advnce,
Zak.

based on timestamp or values of certain field generic datasource shall manage delta. Check this please - Generic Delta-
http://help.sap.com/saphelp_nw70/helpdata/en/37/4f3ca8b672a34082ab3085d3c22145/content.htm

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 set Generic Delta for Generic Datasource

Hi to all,
please can any one explain me the generic Delta option for Generic datasource
after creating generic datasource, i need to set the generic delta .
can any one explain me all generic delta option in simple language with example.
Field Nm
Time samp
calend. Day
Numeric Pointer
Safety Interval Upper Limit
Safety Interval Lower Limit
New status for changed Records
Additive Delta
i shall be thankful to you for this.
Regards
Pavneet Rana

this question has been answered a million times.
search the forum.
M.

Delta Extraction - Generic Datasource

Hello Guys,
I have an issue related with the delta extraction for a generic DS. I have a DS setup with
a generic delta for a calendar day and safety interval upper limit 1. So i think that for some reason no all values are loaded in the
delta load. Please help me to find the best approuch for this.
Regards,
Iván.

Hi,
Hope below links are helpful for you to find the best approuch
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33?quicklink=index&overridelayout=true
Generic delta safty intervals
Regards,
Vinay

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.

Where to find deltas in generic extraction

hi experts,
could you please explain me tcodes which are used to find the delta data while we go for generic extraction. Also can anyone explain me the full process of extracting the data using
infoset query and function module.
Cheers,
Pragya.

Hi
You can define delta's in generic using " calendr day, numeric pointer, time stamp."
Generic Delta
If a field exists in the extract structure of a DataSource that contains values which increase monotonously over time, you can define delta capability for this DataSource. If such a delta-relevant field exists in the extract structure, such as a timestamp, the system determines the data volume transferred in the delta method by comparing the maximum value transferred with the last load with the amount of data that has since entered the system. Only the data that has newly arrived is transferred.
To get the delta, generic delta management translates the update mode into a selection criterion. The selection of the request is enhanced with an interval for the delta-relevant field. The lower limit of the interval is known from the previous extraction. The upper limit is taken from the current value, such as the timestamp or the time of extraction. You can use security intervals to ensure that all data is taken into consideration in the extractions. After the data request was transferred to the extractor, and the data was extracted, the extractor then informs generic delta management that the pointer can be set to the upper limit of the previously returned interval.
The delta for generic DataSources cannot be used with a BW system release prior to 3.0. In older SAP BW releases, the system does not replicate DataSources for master data and texts that were made delta-enabled using the delta for generic DataSources.
Determining the Generic Delta for a DataSource
       1.      Choose Generic Delta.
       2.      In the subsequent dialog box, specify the delta-determining field and the type for this field.
       3.      Maintain the settings for the generic delta:
                            a.      Specify a security interval.
The purpose of a security interval is to make the system take into consideration records that appear during the extraction process but which remain unextracted (since they have yet to be saved) during the next extraction.
You have the option of adding a security interval to the upper limit/lower limit of the interval.
A security interval should only be specified for the lower limit when the delta method results in a new status for changed records, in other words, when the status is overwritten in BW. In this case, duplicate data records that could arise in such a safety interval have no affect on BW.
                            b.      Choose the delta type for the data to be extracted.
The delta type is used to determine how extracted data is interpreted in BW and which data targets in which it can be posted.
With the delta type additive delta, the record to be loaded for summarizable key figures only returns the change to the key figure. The extracted data is added in BW. DataSources with this delta type can supply both ODS objects and InfoCubes with data.
With the delta type New Status for Changed Records, every record to be loaded returns the new status for all key figures and characteristics. The values are overwritten in BW. DataSources with this delta type can write the data into ODS objects and master data tables.
       4.      Save your entries.
Delta transfer is now possible for this DataSource.
After generating the DataSource, you can see this from the marking for the field Delta Update on the DataSource: Customer Version screen.
In systems from release 4.0B, you can display the current value of the delta-relevant field in the delta queue.
Example for Determining the Selection Interval for a Generic Delta
Safety Interval Upper Limit
The delta-relevant field is a timestamp.
The timestamp that was read last is 12:00:00. Delta extraction begins at 12:30:00. The safety interval for the upper limit is 120 seconds. The safety interval for the delta request is: 12:00:00 to 12:28:00. Upon completion of the extraction, the pointer is set to 12:28:00.
Safety Interval Lower Limit
The delta-relevant field is a timestamp. After images are transferred. In other words, the record is overwritten with the status after the change in BW, for example for master data. Any duplicate records that appear have no effect upon the BW system.
The last changed timestamp is 12:28:00. Delta extraction begins at 13:00. The safety interval for the lower limit is 180secs. The safety interval for the delta request is: 12:25:00 to 13:00:00. Upon completion of the extraction, the pointer is set to 13:00:00.
source: help.sap.com
Hope it helps
kalyan

Delta enabled generic data source not updating delta

HI,
   Created one Delta enabled generic datasource with the help of ztable .Fill the content of table by manual entries.
   While executin init,records are extracted from R/3 system. After made a change in table entries , it is not captured in RSA3.
   Data source is avaialble in RSA7 after execueting init.
   Delta type== TIME STAMP
   fIELD NAME=zTIME
SAFETY LIMIT=30 SEC
ITS FROM 'NEW STATUS FOR CHANGE RECORDS'
Please help me on this issue..
Regards,
MohammeD

how did you create your data source? - based on view, table for Function Module?
If it is based on a View or table, ideally delta should have worked. If it is not working, please chedk the data type of the field. Make sure that delta field (i.e. ZTIME) is getting updated evertyime you change any record in ztable. While extracting data in RSA3 in delta (D) mode, make sure you also give the target system ID. Also try runnign the delta infopackage in BW if it fetches data.
If nothing works, try creating your data source again.
If it is based on Fuction Module, you will have to include the delta functionality in your code.
Regards,
Gaurav

Delta in Genric datasource

Hi Experts,
How to test delta for generic datasource.
will the delta goto lbwq for generic datasource or straight away rsa7?
Regards,
Anand

Hi,
For generic data source, delta will be seen in RSA7 not LBWQ.
Generic datasource to have a delta capability, your table or view should have either time or date field.
Thanks
Srikanth

Generic DataSource cannot be updated in an InfoCube!

Hi Expert
We have a Z infocube that is loaded directly by a Generic Datasource. We setup a infopack for initialize delta precess and other for Delta Update. With a DTP Full we load the initial data, but when we try to setup a DTP for Delta information the system respond that Generic datasource cannot be updated in an infocube directly because uses delta process AIE (RSM1112).
We have a transformation rule and many routine from the generic datasource to Z infocube, so for us is very difficult to setup a ODS. So anybody know is there another option that allow us to setup a DTP Delta for generic datasource to update directly to Z infocube, for us is going to be very helpfull any idea.
On the other hand, on DES with made a DTP Delta and the system doesn´t say anything, but on PRD the DTP Delta can´t be active.
Thanks a lot

Hi David:
AIE only supports loading to ODS/DSO, for more details refer to the blog provided by Swapna Gollakota.
"How does a datasource communicates "DELTA" with BW?"
/people/swapna.gollakota/blog/2007/12/27/how-does-a-datasource-communicates-delta-with-bw
Regards,
Francisco Milán.
P.S. Take a look at this thread for a similar discussion.
"DataSource 0FI_AP_4 cannot be updated in an InfoCube! "
Edited by: Francisco Milan on Jun 18, 2010 5:20 PM

Generic Datasource--plz confirm

Hi gurus,
i have created a generic datasource but unfortunately i don't have any number, date field which i can use as delta field...so as per the document on SDN which says that by using Business Transaction Events we can get the delta capability
but i am not able to find any BTE for production orders which i can use for delta...so can somebody help on this like how ...enable the delta capability as well as plz help to find BTE so that i can use it.
thanks and regards
Neel
Message was edited by: Neel Kamal
Message was edited by: Neel Kamal
Message was edited by: Neel Kamal

Hi Neel
Pseudo delta is not generic delta. What I had advised is you can create pseudo delta if you are not able to find date field for generic delta mechanism.
1.Add both date fields to generic datasource alongwith all other fields.
2.You have to assign this datasource to infosource in BW and map the transfer rules.
3. Create 2 infopackages for this -one for CREATED ON - will load new records created yesterday & other for CHANGED ON - will load changed records yesterday.
4. schedule both these infopackages to load daily.
Also want to re-iterate the fact that this approach is not recommended over creating a delta enabled generic datasource. But in abscence of date field for generic delta mechanism.
Hope this helps
Regards
Pradip

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.

Delta in Generic datasources.

Similar Messages

Maybe you are looking for