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

Similar Messages

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

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 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 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 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 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

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 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 with Delta and functionmodule

Hi together,
who can help me ??
Ihave created a generic datasource with function module and
delta.
the extractor runs well while i use full update and also initialization.
If i start the delta extraction, the extractor crashed with short-dump.
the message is SAPSQL_INVALID_FIELDNAME
What can i do, and what is wrong.
regards
thorsten Weiss

Hi Roberto,
here is the code from the function-module:
FUNCTION zbw_mm_get_eket.
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SBIWA_S_INTERFACE-REQUNR
*" VALUE(I_DSOURCE) TYPE SBIWA_S_INTERFACE-ISOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SBIWA_S_INTERFACE-MAXSIZE DEFAULT 1000
*" VALUE(I_INITFLAG) TYPE SBIWA_S_INTERFACE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SBIW_BOOL DEFAULT SBIW_C_FALSE
*" TABLES
*" I_T_SELECT TYPE SBIWA_T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SBIWA_T_FIELDS OPTIONAL
*" E_T_DATA OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER
INCLUDE lrsalk01.
DataSource for table EKET
TABLES: zv_mm_eket.
interne Tabelle für Bearbeitung
DATA: itab_0 TYPE TABLE OF zstr_eket WITH HEADER LINE.
TYPES: BEGIN OF typ_categ,
 j_4kbwef TYPE atnam,
 /afs/bwel TYPE j_4kbwef,
 END OF typ_categ.
DATA: l_s_data_eket TYPE zstr_eket,
 ld_cat_struct TYPE j_4kcsgr,
 lt_cat_fields TYPE TABLE OF j_4kcif001,
 ls_cat_fields TYPE j_4kcif001,
 ls_mara TYPE mara,
 l_tabix LIKE sy-tabix,
 itab_cat TYPE TABLE OF typ_categ ,
 ls_cat TYPE typ_categ,
 h_feldsize1(8) TYPE c,"wegen Typ-konflikt im FB
 h_feldsize2(8) TYPE c."wegen Typ-konflikt im FB
Auxiliary Selection criteria structure
DATA: l_s_select TYPE rsselect.
Maximum number of lines for DB table
STATICS: s_t_select LIKE rsselect OCCURS 0 WITH HEADER LINE,
 s_t_fields LIKE rsfieldsel OCCURS 0 WITH HEADER LINE,
counter
 s_counter_datapakid LIKE sy-tabix,
cursor
 s_cursor TYPE cursor.
Select ranges
RANGES: l_r_ebeln FOR zv_mm_eket-ebeln,
 l_r_ebelp FOR zv_mm_eket-ebelp,
 l_r_bsart FOR zv_mm_eket-bsart.
Initialization mode (first call by SAPI) or data transfer mode
(following calls) ?
IF i_initflag = sbiwa_c_flag_on.
Initialization: check input parameters
 buffer input parameters
 prepare data selection
Check DataSource validity
 CASE i_dsource.
 WHEN 'ZDS_V_MM_EKET'.
 WHEN OTHERS.
 IF 1 = 2. MESSAGE e009(r3). ENDIF.
this is a typical log call. Please write every error message like this
 log_write 'E' "message type
 'R3' "message class
 '009' "message number
 i_dsource "message variable 1
 ' function modul was created for DS ' &
 'ZDS_V_MM_EKET"!'.
 "message variable 2
 RAISE error_passed_to_mess_handler.
 ENDCASE.
 APPEND LINES OF i_t_select TO s_t_select.
Fill parameter buffer for data extraction calls
 S_T_SELECT-REQUNR = I_REQUNR.
 S_T_SELECT-DSOURCE = I_DSOURCE.
 S_T_SELECT-MAXSIZE = I_MAXSIZE.
Fill field list table for an optimized select statement
(in case that there is no 1:1 relation between InfoSource fields
and database table fields this may be far from beeing trivial)
 APPEND LINES OF i_t_fields TO s_t_fields.
ELSE. "Initialization mode or data extraction ?
Data transfer: First Call OPEN CURSOR + FETCH
 Following Calls FETCH only
First data package -> OPEN CURSOR
 IF s_counter_datapakid = 0.
Fill range tables BW will only pass down simple selection criteria
of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
 LOOP AT s_t_select INTO l_s_select WHERE fieldnm = 'EBELN'.
 MOVE-CORRESPONDING l_s_select TO l_r_ebeln.
 APPEND l_r_ebeln.
 ENDLOOP.
 LOOP AT s_t_select INTO l_s_select WHERE fieldnm = 'EBELP'.
 MOVE-CORRESPONDING l_s_select TO l_r_ebelp.
 APPEND l_r_ebelp.
 ENDLOOP.
 LOOP AT s_t_select INTO l_s_select WHERE fieldnm = 'BSART'.
 MOVE-CORRESPONDING l_s_select TO l_r_bsart.
 APPEND l_r_bsart.
 ENDLOOP.
Determine number of database records to be read per FETCH statement
from input parameter I_MAXSIZE. If there is a one to one relation
between DataSource table lines and database entries, this is trivial.
In other cases, it may be impossible and some estimated value has to
be determined.
 OPEN CURSOR WITH HOLD s_cursor FOR
 SELECT (s_t_fields) FROM zv_mm_eket
 WHERE
 ebeln IN l_r_ebeln AND
 ebelp IN l_r_ebelp AND
 bsart IN l_r_bsart.
 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 e_t_data
 PACKAGE SIZE i_maxsize.
 FETCH NEXT CURSOR s_cursor
 APPENDING CORRESPONDING FIELDS
 OF TABLE itab_0
 PACKAGE SIZE i_maxsize.
 LOOP AT itab_0 INTO l_s_data_eket.
 l_tabix = sy-tabix.
Lesen Erstellungsdatum aus EKKO
 SELECT SINGLE aedat FROM ekko INTO l_s_data_eket-sydat
 WHERE ebeln = l_s_data_eket-ebeln.
Lesen Partner aus EKPA
 SELECT SINGLE lifn2 FROM ekpa INTO l_s_data_eket-plief
 WHERE ebeln = l_s_data_eket-ebeln AND
 ebelp = l_s_data_eket-ebelp AND
 ekorg = l_s_data_eket-ekorg AND
 werks = l_s_data_eket-werks .
 IF NOT l_s_data_eket-matnr IS INITIAL .
*A Lesen material für Kategoriestruktur j_4kcsgr(F001 oder R002)
 CLEAR ls_mara.
 CALL FUNCTION 'J_3A1_LESEN_MARA_SINGLE'
 EXPORTING
 i_matnr = l_s_data_eket-matnr
 IMPORTING
 e_mara = ls_mara
 EXCEPTIONS
 param_not_valid = 1
 OTHERS = 2.
 IF sy-subrc NE 0.
 ENDIF.
*E Lesen material für Kategoriestruktur j_4kcsgr(F001 oder R002)
*A Aufsplitten Bestandskategorie
 REFRESH lt_cat_fields.
 CALL FUNCTION 'J_4KG_SPLIT_CAT'
 EXPORTING
 client = sy-mandt
 csgr = ls_mara-j_4kcsgr
 cat_appl = 'S'
 cat_value = l_s_data_eket-j_4kscat
NECESSARY_SPECIFIED = ' '
 TABLES
 cat_fields_tab = lt_cat_fields
 EXCEPTIONS
 no_category_structure_found = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ELSE."sy-subrc <> 0
Verarbeitung der Ergebnisse
 LOOP AT lt_cat_fields INTO ls_cat_fields.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_SCONFIG'.
 l_s_data_eket-zz_bwel_sconfig = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_CONFIG'.
 l_s_data_eket-zz_bwel_config = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_COUNTRY'.
 l_s_data_eket-j_3abwel_country = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_COUNTRYGRP'.
 l_s_data_eket-zz_bwel_coungrp = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_STOCKTYPE'.
 l_s_data_eket-zz_bwel_stktype = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_ORDER'.
 l_s_data_eket-zz_bwel_order = ls_cat_fields-j_4kcatv.
 ENDIF.
 IF ls_cat_fields-j_4kbwef EQ 'BW_CAT_QUALITY'.
 l_s_data_eket-j_3abwel_qual = ls_cat_fields-j_4kcatv.
 ENDIF.
 ENDLOOP."lt_cat_fields
 ENDIF.
*E Aufsplitten Bestandskategorie
*A Aufsplitten MAtrix
 IF NOT l_s_data_eket-j_3asize IS INITIAL.
 CALL FUNCTION 'J_3A_SPLIT_SIZES'
 EXPORTING
 matnr = l_s_data_eket-matnr
 j_3asize = l_s_data_eket-j_3asize
 IMPORTING
 j_3akord1 = l_s_data_eket-j_3abwel_color
 j_3akord2 = h_feldsize1
 j_3akord3 = h_feldsize2
 EXCEPTIONS
 no_grid_determined = 1
 OTHERS = 2.
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ELSE.
 l_s_data_eket-zz_bwel_size1 = h_feldsize1.
 l_s_data_eket-zz_bwel_size2 = h_feldsize2.
 ENDIF.
 ENDIF."not l_s_data_eket-J_3ASIZE is initial
*E Aufsplitten MAtrix
 MODIFY itab_0 FROM l_s_data_eket INDEX l_tabix.
 ENDIF."not l_s_data_eket-matnr is initial
 ENDLOOP. "itab_0
An Ausgabe-Tabelle übergeben
 APPEND LINES OF itab_0 TO e_t_data.
 IF sy-subrc <> 0.
 CLOSE CURSOR s_cursor.
 RAISE no_more_data.
 ENDIF.
 s_counter_datapakid = s_counter_datapakid + 1.
ENDIF. "Initialization mode or data extraction ?
ENDFUNCTION.
regards
thorsten

To enable delta update in generic datasource

Hi All,
I'm creating a generic datasource for master data. I want to enable the delta update option. While creating the datasource the option is disabled and i'm not able to tick the checkbox. Can you please tell me how to enable the delta update option.
Thanks in advance,
Sananda

Hi Sananda,
when creating the DataSource, choose button Generic Delta. In the dialog box that appears, specify the delta-determining field and the type of this field. Maintain your entries and save data. After the DataSource has been generated, the delta update field is selected.
Regards,
Theodoros

Generic DataSource & Delta setup

Similar Messages

Maybe you are looking for