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

Similar Messages

Generic delta based on timestamp ?

Hello BW Experts,
For a generic datasource involving the sales order data what is the best option for the delta type timestamp / calender day / numeric pointer. I am in the opinion of the timestamp as the records are based on timestamp. let me know if I correct.
Thanks,
BWer

hi,
yes, it's depend on the extract structure (your table/view/fm), F1 info :
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.
hope this helps.

Generic delta extractors without timestamp!

Hi,
For a certain requirement, I have to develop generic extractors which should be delta capable. But unfortunately the source tables donu2019t have a timestamp; hence I canu2019t create delta enabled generic extractors using timestamp. Moreover most of the tables are standard SAP tables, which are used across different modules so it is not possible to introduce timestamp in these tables.
I am working on extractors for Business Partners in SAP Transaction Banking.
I have got couple of options:
1) To use the change pointers by activating CNS service in source system. It is possible to activate the service and set up the segments for standard and custom tables, from where I need to extract the data.
2) To develop the function module and create the generic extractors using delta queue functionality.
Issues: In the first approach, I have created an extractor and it is possible to recognize the changed records. But the issue is I need some kind of flag which tracks the information regarding last successful delta extraction for an extractor based on change pointers and standard SAP table. I am not sure how does standard extractors maintains this status and picks up new/changed records in delta functionality. Not sure how to achieve this.
In second approach I am not sure if it is possible to create generic extractors using delta queue and what are the complexities involved.
If someone has already worked on these areas, any inputs are most welcome.
Thanks and Regards,
Amit

Hi Amit,
I haven't worked on SAP Transaction Banking but I hope you can get most of Business Partner data in standard extractors. Try to look for some.
If you have to go for Generic extractor. there are 2 options:
1. Use BTE
[How To Create GDS which uses Delta Queue|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b68b99-022e-2a10-999d-c4dc9ec24a59]
2.Use FM based GDS
[How to Create Generic Delta|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[Generic Delta Using Funtion Module |Re: Generic Delta Using Funtion Module]
You can also look for some numeric pointer from RSO2.
Hope it will help you...
Regards,
Ashish

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

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 extraction using function module

Hi.
I have a generic datasource , extraction being performed by a function module. The extraction works fine in full update mode. The extract structure has a timestamp field.
I have enabled generic delta using this field(i.e., marked this field in RSO2). I understand that with this setting, I should be able to get delta data when I do a delta request. But it does not seem to happen.
I checked the ROOSPRMSC table for the last(local) timestamp stored there. Now when I do the delta upload I expect to see only those records which are younger than the stored timestamp of last upload.
But I still get the entire set of records.
Questions are :
1. Do I need to explicitly code for fetching the delta in the extractor ?
2. If not, what could be the reason why generic delta is not working ?
Thanks and regards,
Anuradha

Hi GFV,
I read-up all the forum entries on this topic but could not find anything specifically dealing with my problem. I have browsed through the how-to paper on generic delta as well.
I am quite sure that we don't need any special coding in the extrator for generating delta generically. Even the how-to paper does not mention that.
I have used the FM RSAX_BIW_GET_DATA_SIMPLE as a template
for my extractor(as suggested by F1 help in RSO2). This FM does not even have the i_updmode flag in its interface.
Thus this function module always does full extraction and I expect the system to take care of delta using the timestamp field.
Are these assumptions incorrect ?
Regards,
Anuradha

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

Generic Delta for table MVKE

I need to extract material sales data from table MVKE.
I want to use generic delta datasource but I'm not sure based on which field I need to load delta.
Any suggestions?
Is it possible to use generic delta for MVKE?

Hi,
Yes you can go for generic delta, but you need to decide how your delta should be, whether you want only changed records or after before images or only new records,...
After deciding if you want only new records then you can go for CREATED On field
For changed records ou can go for CHANGED ON field
if you want after before images then choose the correct fields,
after choosing the delta you have to check for when you want to run your delta, daily once or more than ones, if you want yo run more than once go for time stamp.
Regards,
Pavan.

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

Reg. Generic delta using fun module

Hello Experts,
I am creating function module for generic delta (both Full, Delta) using RSAX_BIW_GET DATASIMPLE. My generic field is AEDAT.
When I check this function module, there is no logic to maintain Delta load excapt Full. Where as this Delta functionality is available in another function module RSAX_BIW_GET_DATA. Now my question is:
Can we use RSAX_BIW_GET DATASIMPLE for Delta load also?
If yes, How to maintain delta based on AEDAT field?
Do we need to maintain this Delta specific field AEDAT in Extract structure?
Can anybody please clarify my doubts.....
Thanks in advance,
Zak.

Hi,
Please check the blog:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Also check :
Re: Delta update - rso2
-Vikram

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.

ALE Delta vs Generic Delta

Hi Gurus,
Can we set only ALE delta for master data attr/text extractors. Can we not set generic delta for master data extractors. If yes can you provide some master data extractors which use generic delta?
Regards,
Rajesh.

Hi, if we are loading master data from R/3 to BI system we will select change pointers in BD61 . ROOSGEN table contains the message types based on that message types change pointer will work. In TBDA2 table we can activate and deactivate the message types; in active column X means message type is active.before activating that field will be in blank once we will activate the it will converted it to X.
for generic refer this document :Delta Transfer to BI (SAP Library - Business Intelligence)

Generic delta creation with Extractor Starter Kit - BW Datasource option

Hi Rajesh, Rohit,
As per the wiki, http://wiki.sdn.sap.com/wiki/display/CPM/FAQ-DataExtractionforSpendPerformance+Management, the question:-
Do these starter kits have any support for delta (periodic data updates) after the initial load is completed?
A. Yes. Deltas are available (for all source objects that support delta mechanism) in both of the extraction options. You don't need to reload the full set of data, when you perform the periodic data updates.
I understand you can use the date range but this in my view is still a full load. We understand that you can create your own generic datasource based on the generated function module generated by generating the object, for e.g PO.
We have tried to do this for the object PO, thus the following:-
rso2 > create a new transaction datasource > base on generated datasource (Z_SADSERPPO) and use it's fm and extract strucutre :- Z_SAERPPO_DS fm , ZEXTR_ERPPO extr structure
When we goto to create a generic delta based on DATE_RANGE we get the error message ::-
Z_PDPOTEST: TABLES-paramter E_T_DATA for extractor Z_SAERPPO_DS is missing
Can you create a blog around this as we understand other customers have managed to create these deltas?
Best regards,
Pom

Hi Claudia,
That's fine, please continue to use the Z_SA_DEPD to generate the datasource. If you then do a rsa2 on this datasource, you can see the underlying function module and the extract structure for this which is also fine.
The bizarre thing is that through rso2 for this generated extractor, you cannot see the fm associated for this, hence why the generic delta is not working.
What we thought of doing and in line with the sap recommendation was to create a new transaction datasource from tcode rso2 and base it on the above function module and extract structure, but when we goto choose the date_range as the generic delta, it doesn't work and gives the error.
Am still waiting an answer.
Will keep you posted.
Thanks,
Pom

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

Problem in delta management for custom fields added in standard Table

Hi developers,
we have a problem, when a sales order is modified in a field custom, added in tables (VBAP-VBAK), the delta BW doesn't recognize the modifications. The data type of these fields haven't the flag (Change document) setted in
view Definition.
If this flag is setted, Can the delta BW recognize the modifications of the custom fields?
Best regards
Domenico

You cannot get delta by just appending fields to extract structure & writing the user exit coding as this user exit code is run by the extractor after the X- and Y- tables are compared to create the before & after images.
You have to do this procedure by enhancing LIS comm structures like MCVBAP (for example).
Please refer to OSS note 576886 for complete details.
Kumar Gudiseva.

Generic Delta based off TimeStamp field is extracting full load

Similar Messages

Maybe you are looking for