Generic delta with timestamp

Hi All,
i have created a generic datasource using tables vbrp,vbrk.mara,marc,knvv.. to get the sales data for planning.Here i have document created date and time.So i'm concatinating these 2 date and time fields into timestamp which is of format yyyymmddhhmmss.Finally i'm using this timestamp to extract data .
So is it the right way to pull the data using timestamp and what is the timezone i need to specify as the servers are in india only.
or any other way to proceed.
Thanks
Rao.

Hi Siva,
U mean.. is ur MKPF is having the TIme stamp field in that? or this table has got enhanced with the TIme stamp field..?
do let us know these details..
Why dont u try using any other fields like changed on or some other fields which will satisfy ur requirement..?
Is ur Init is done successfully?... and do u see an entry in the table ROOGENDELTM table....
This table will be having an entry for the generic extractors which are with the Delta's..
Thanks
Assign points if this helps

Similar Messages

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 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 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 with function module

Hi Gurus,
Is it possible to create a generic DataSource with delta support using function module following the queue delta mechanism (u can get some function moduel in MCEX function group, and check the outbound delta queue before and after update in transaction smq1.
I can store the delta data using qRFC and collective update mechanism. but I don't know how to create a generic data with delta and how to attach a rfc destination (& logical system) to the data source. The Source system information is stored in the table "ROOSGEN". Is there any configuration setting required to do the same.
Regards,
Jugal

Jugal,
What I understand you to be asking is if it is possible to create a generic delta extractor which uses the delta queue. If this indeed is your question the answer is yes.
First you need to create your data source so it is visible via tx RSA5 and need to make sure that the delta type (ie ABR, AIM)is set appropriately for the datasource.
The issue however is determining from where you will associate your delta hook (when will you write to the queue)? I have in the past utilized BTE's, Business Transaction Events to write information out to the delta queue, you can see a list of available BTE's in your system via tx FINF.
Once you find a place to write your deltas from you call the below FM with the appropriate datasource.
RSC1_TRFC_QUEUE_WRITE.
Once you have done this the standard BW extractor for deltas will pull the information from the delta queue. But from what I understand you just want to know how to associate the data with the delta and that is the FM listed above.
Hope this helps,
Cheers,
Scott
> Hi Gurus,
>
> Is it possible to create a generic DataSource with
> delta support using function module following the
> queue delta mechanism (u can get some function moduel
> in MCEX function group, and check the outbound delta
> queue before and after update in transaction smq1.
> I can store the delta data using qRFC and collective
> update mechanism. but I don't know how to create a
> generic data with delta and how to attach a rfc
> destination (& logical system) to the data source.
> The Source system information is stored in the table
> "ROOSGEN". Is there any configuration setting
> required to do the same.
>
> Regards,
> Jugal

Time interval limit for generic delta on timestamp

I have searched a lot about delta on timestamp in the forums.
But I'm still not clear with the safety upper and lower limits..how is my delta load affected by this value?
What happens if I dont specify any value for the interval limit?

Hi,
This is very simple thing, you must be knowing the concept of data posting in transactional system, e.g. creating a sales order.
When you create an order and press save, system takes data from this screen to the database tables and once this action, which is called "DB COMMIT", gets completed, you get data in your system tables. So this activity may take some time before you can retrive this information.
Let's say it takes 5 mins, so when you'll collect delta records, if some records, which are under process for DB commit, they won't come in delta. Say u collect these records at 12:00 AM and record posted 11:55 PM will take 5 mins to reflect in Database. So we keep safty limit of 5 min.
Upper and lower means starting and ending of time window, from which you want to extract records.
Hope it helps in understanding...
Regards,
Ashish

Generic Delta with Numeric pointer.

Hi Experts,
We are using a generic delta for a Standard Master Data Attribute Data Source. Since it is standard by default it has the Numeric Pointer and the Additive Delta in the settings.
When a delta extraction is done with this option it does not bring any changed records it just brings the newly added records.
We are not able to change to the other Delta options available in that screen.
Could you guys help us with this issue.
Thanks
Sandhya

Hi Harvinder,
The answer you gave was very helpful.Thanks for all your help so far.
Due to some restrictions from our BASIS team, We are not able to Check the 'Change Document' for (AEDAT) Changed on field. There are other fields in the same Data Source which are Delta Enabled and they also have the 'Change Document' Checked. Could we use one of those fields in our Delta. If yes what changes do we have to make. If you can, Can you give a brief step by step how to make the changes.
Also we are not able to change anything in the Generic Delta tab. At times it is giving an error, other times it does not get saved when we go back it is unchaged. May be we are doing something wrong.
Regards,
Sandhya

How to get generic delta using timestamp field

Hi All,
i have created a generic datasource using tables vbrp,vbrk.mara,marc,knvv.. to get the sales data for planning.Here i have document created date and time.So i'm concatinating these 2 date and time fields into timestamp which is of format yyyymmddhhmmss.Finally i'm using this timestamp to extract data .
So is it the right way to pull the data using timestamp and what is the timezone i need to specify as the servers are in india only.
or any other way to proceed.
Thanks
Rao.

Hi Rao,
Delta based on timestamp based on generic datasource only works if any one of the tables contains timestamp field(not time and date fields separately).
I dont think by combining date & time fields will give you correct results.
Regarding time zone: Use SAP system time zone.
Srini

Generic Delta with Two fields

Hi,
Can it be possible to have Delta on two fields in Generic Data Source?
If yes, Please let me know the Procedure.
Thanks,
Ram.

hi,
generic data source is nothing but if u used one data source to upload the data to one ods. at that time u want the same data source for next cube also.that time u crete the generic data source and create transformation ods to cube and also create the dtp ,upload the data.
delta means its filter the same records present in next time.
1.create data source and infopackage.
2.upload the data to datasource(psa).
3.create ods.
4.create transformation.(use that data source).
5.create dtp.
6.execute the data.
7.create cube.
8.right click the ods.
9.create generic data source.
10.right click the ods create transformation(use torget as cube)
11.create dtp.
12. that will have full or delta updates .
13. use delta update.
14.execute the data.
if its helpfull assign points.
thanks.
prakasu

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

Numeric Pointer Option on Generic Delta Screen

Hi, I was just wondering if anyone could help with why the option for 'Numeric Pointer' on the 'Generic Delta' screen in datasources is missing. I only have the option for 'timestamp' and 'calendar day'.
Thanks

Hi,
If you are trining to create a Generic delta with FM, you can't find the option "Numaric pointer".
Please check this link.
[Generic Extraction via Function Module|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=%28J2EE3417500%29ID1674507050DB11515805598662912203End?blog=/pub/wlg/2415]
Regards,
Madhu

Generic Delta Extraction (Bill Plan Data)

Hi BW Gurus,
We need to cerate data source from Bill plan extractor.
Please note that there is no SAP standard extractor for the bill plan data. So that is the reason we are using generic extractor (RSO2). We were using sales order delta extract program to find out the changes in bill plan data and there was routine in that extract which updated the custom table. But, soon they have to get rid of this design, because they observed that all the changes being done to bill plan were not being captured in the sales order delta extract. So, they have to go ahead with a full extract instead of the delta extract for bill plan data. Now we need to create design so we can do a delta extract on the billing plan data.
Please advice me ASAP.
In Advance Many thanks for your help.
Regards
SAP Team

You could use the date field instead , you could have a lower safety interval and then when you do the delta again the records included in the lower safety interval are included. As for delta with timestamp , I have a question what is the timestamp used for delta - is it UTC Timestamp or the date and time concatenated together. UTC Timestamp did not seem to work for me and I did not have the luxury of having a concatenated timestamp.
When I checked the base tables for delta maintenance , I found both timestamps and am confused as to what timestamps to use.
Arun
P.S I have a current delta with changed date and a lower safety interval of 1 day and it is working fine so far.

Generic delta extractor for BW

Hello people!
I'm developing an extractor for BW with Generic delta with the field AEDAT.
In function module for the extractor, how can I identify this delta?
I have to select the table ESSR with this field and I don't know how to identify this field.
Thanks in advance!
See ya!

Define a range field like
ranges : l_r_aedat for <tabname>-aedat.
In your FM
LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'AEDAT'.
MOVE-CORRESPONDING L_S_SELECT TO L_R_AEDAT.
append l_r_aedat.
Then when you do selections :-
Select * from <tabname> where
and aedat in l_r_aedat.

Incorrect TimeStamp in Generic Delta (UTC Issue)

Hi,
I have a problem regarding a generic delta extractor. The pointer stored in rsa7 (ROOSGENDLM table) is not UTC but system time. As standard tables store the timestamp using UTC format the delta extractor is not picking up the correct data.
Do you know a solution for this?

Hi,
Thanks for your reply. However I think that unfortunately this solution is not enough
For example:
I execute a delta. My TimeStamp is registered as UTC +2: 20080612160000. (Here I have the error, it should be in UTC)
Now I modify a record in R3 and it is registered with timestamp UTC: 20080612140000.
If I execute a delta it will take all the records higher than 20080612160000. Therefore my modification will never be uploaded.

Intervals with generic delta extraction

Hello,
Can some1 explain when do we use intervals in generic delta extraction with a good example?
Thanks in advance.
Regards,
KS

Hi,
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.
refer to this link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Hareesh

Generic delta with timestamp

Similar Messages

Maybe you are looking for