Doubt Reg Generic Delta "Safety Interval" Setting

Hi Experts,
I have a doubt regarding Setting "Safety Interval Upper Limit" and Lower limit in RSO2 for generic delta.
What does this setting imply?
If I do setting for calender day say both 1 then wht will be difference between delta before setting amd after setting?
Plz explain in terms other tham help provided...
Points will be awarded to say thanks..
Thanks in advance,
Sorabh

Hi Sorabh,
Here some SAP informations:
Safety Interval Upper Limit of Delta Selection
This field is used by DataSources that determine their delta generically using a repetitively-increasing field in the extract structure. The field contains the discrepancy between the current maximum when the delta or delta init extraction took place and the data that has actually been read. Leaving the value blank increases the risk that the system could not extract records arising during extraction. Example: A time stamp is used to determine the delta. The time stamp that was last read is 12:00:00. The next delta extraction begins at 12:30:00. In this case, the selection interval is 12:00:00 to 12:30:00. At the end of extraction, the pointer is set to 12:30:00.  A record - for example, a document- is created at 12:25 but not saved until 12:35. It is not contained in the extracted data but, because of its time stamp, is not extracted the next time either.
For this reason, the safety margin between read and transferred data must always be larger than the maximum length of time that it takes to create a record for this DataSource (with a time stamp delta), or it must display an interval that is sufficiently large (for determining delta using a serial number).
Safety Interval Lower Limit
This field contains the value taken from the highest value of the previous delta extraction to determine the lowest value of the time stamp for the next delta extraction. For example: A time stamp is used to determine a delta. The extracted data is master data: The system only transfers after-images that overwrite the status in the BW. Therefore, a record can be extracted into the BW for such data without any problems.
Taking this into account, the current time stamp can always be used as the upper limit when extracting: The lower limit of the next extraction is not seamlessly joined to the upper limit of the last extraction. Instead, its value is the same as this upper limit minus a safety margin. This safety margin needs to be big enough to contain all values in the extraction which already had a time stamp when the last extraction was carried out but which were not read. Not surprisingly, records can be transferred twice. However, for the reasons above, this is unavoidable.
Extracted Data Delta Type
The system uses the delta type to determine how extracted data is to be interpreted in BW, and into which data targets it can be posted.
A distinction is made between the following:
1. Additive delta
The key figures for extracted data are added up in BW. DataSources with this delta type can supply data to ODS objects and InfoCubes.
2. New status for changed records
Each record to be loaded delivers the new status for the key figures and characteristics. DataSources with this delta type can write to ODS objects or master data tables.
Check also examples in "How to... Create Generic Delta" under www.service.sap.com/bi.
Ciao.
Riccardo.

Similar Messages

  • Doubt about generic delta using function module.

    Hi,
    I have the following scenario.
    I have to create a generic data source having delta using funcation module.
    The full load works fine, but the delta load not.
    I don't know, if always the field that was specified as a delta, must be part of the cursor in this case AFRU~LAEDA
    This is my cursor:
    OPEN CURSOR WITH HOLD S_CURSOR FOR
               SELECT AFIHAUFNR AFIHADDAT AFIHIPHAS AFIHILART AFIH~AKKNZ
                             AFIHPLKNZ AFIHILOAN AFIHIWERK AS ZPLANPLANT AFIHEQUNR
                             ILOA~TPLNR
                             AFKOGSTRP AFKOGLTRP AFKOGSTRS AFKOGLTRS AFKOGSTRI AFKOGETRI AFKO~FTRMI
                             AUFKAEDAT AUFKERDAT AUFKWERKS AUFKKOSTL AUFKKOKRS AUFKSOWRK AUFK~OBJNR
                             AUFKAUART AUFKVAPLZ
                             CRHD~ARBPL
                            TKA01~WAERS AS ZCOSTP_ML_UM
                  FROM AFIH
                       INNER JOIN AFKO ON AFIHAUFNR = AFKOAUFNR
                       LEFT OUTER JOIN ILOA ON ILOAILOAN = AFIHILOAN
                       INNER JOIN AUFK ON AFIHAUFNR = AUFKAUFNR
                       INNER JOIN TKA01 ON AUFKKOKRS = TKA01KOKRS
                       LEFT OUTER JOIN CRHD ON CRHDOBJID = AFIHGEWRK
                  WHERE AFIH~AUFNR in L_R_AUFNR
                        AND AFIH~EQUNR in L_R_EQUNR
                        GROUP BY AFIHAUFNR AFIHADDAT AFIHIPHAS AFIHILART AFIHAKKNZ AFIHPLKNZ AFIH~ILOAN 
                                           AFIHIWERK AFIHEQUNR
                                          ILOA~TPLNR
                                          AFKOGSTRP AFKOGLTRP AFKOGSTRS AFKOGLTRS AFKOGSTRI AFKOGETRI AFKO~FTRMI
                                          AUFKAEDAT AUFKERDAT AUFKWERKS AUFKKOSTL AUFKKOKRS AUFKSOWRK 
                                         AUFKOBJNR AUFKAUART AUFK~VAPLZ
                                         CRHD~ARBPL
                                         TKA01~WAERS.
    For each aufnr I must go to the afru table and totalize the real work (IWNW)  and real duration (IDAUR) when AFRUSTZHL > 0 and totalize too when AFRUSTZHL = 0 but with sign to negative.
    This is my external query, i need that the field AFRU~LAEDA must be taken as delta field:
              SELECT AFRUERSDA AFRULAEDA AFRUSTZHL SUM( AFRUISMNW ) AS ZTRA_REAL AFRUISMNE AS ISMNE SUM( AFRUIDAUR ) AS ZDURAC_REAL AFRU~IDAUE AS IDAUE
                     INTO CORRESPONDING FIELDS OF TABLE WT_AFRU_OM
              FROM AFRU
                   WHERE AUFNR = WT_ZCUROM-AUFNR
                         AND AFRU~STZHL = 0
                   GROUP BY AFRUERSDA AFRULAEDA AFRUSTZHL AFRUAUFNR AFRUISMNE AFRUIDAUE AFRUISMNW AFRUIDAUR
                   order by AFRUERSDA AFRULAEDA AFRUSTZHL AFRUIDAUE AFRU~ISMNE.
              IF sy-subrc = 0.
                CLEAR WT_AFRU_OM2.
                REFRESH WT_AFRU_OM2.
                SELECT AFRUERSDA AFRULAEDA AFRUSTZHL SUM( AFRUISMNW ) AS ZTRA_REAL AFRUISMNE AS ISMNE SUM( AFRUIDAUR ) AS ZDURAC_REAL AFRU~IDAUE AS IDAUE
                       INTO CORRESPONDING FIELDS OF TABLE WT_AFRU_OM2
                FROM AFRU
                     WHERE AUFNR = WT_ZCUROM-AUFNR
                           AND AFRU~STZHL > 0
                     GROUP BY AFRUERSDA AFRULAEDA AFRUSTZHL AFRUAUFNR AFRUISMNE AFRUIDAUE AFRUISMNW AFRUIDAUR
                     order by AFRUERSDA AFRULAEDA AFRUSTZHL AFRUIDAUE AFRU~ISMNE.
                IF sy-subrc = 0.
                  LOOP AT WT_AFRU_OM2.
                    WT_AFRU_OM2-ZTRA_REAL = WT_AFRU_OM2-ZTRA_REAL * -1.
                    WT_AFRU_OM2-ZDURAC_REAL = WT_AFRU_OM2-ZDURAC_REAL * -1.
                    APPEND WT_AFRU_OM2 TO WT_AFRU_OM.
                  ENDLOOP.
                ENDIF.
                LOOP AT WT_AFRU_OM.
                  "fjro incluir el clear y el move
                  CLEAR WT_DATOS_OM.
                  MOVE-CORRESPONDING W_DATOS_BASE to WT_DATOS_OM.
                  MOVE-CORRESPONDING WT_AFRU_OM TO WT_DATOS_OM.
                  APPEND WT_DATOS_OM.
                  APPEND WT_DATOS_OM TO WT_ESTFIN_OM.
                ENDLOOP.
              ENDIF.
    It's possible set the delta field in a external query of the cursor.
    Best Regards
    Ramon Sanchez
    Edited by: RAMON SANCHEZ on Aug 20, 2010 2:46 PM

    Hi Sri,
    here some coding, I hope this helps!
    first, get the delta-field
          LOOP AT s_s_if-t_select INTO l_s_select.
            CASE l_s_select-fieldnm.
              WHEN 'ZDATE'.
                MOVE-CORRESPONDING l_s_select TO r_date.
                IF r_date-high IS INITIAL OR r_date-high = space.
                  r_date-high = '9991231'.
                ENDIF.
                APPEND r_date.
            ENDCASE.
          ENDLOOP.
    Cursor öffnen
          OPEN CURSOR WITH HOLD s_cursor FOR
          SELECT * FROM
          WHERE  ....
          AND    erdat in r_date
          AND    aedat IN r_date.
          FETCH NEXT CURSOR s_cursor INTO CORRESPONDING FIELDS OF table e_t_data package size s_s_if-maxsize.
    regards
    Siggi
    PS: Note that this coding only works for a very straight forward extraction.
    Message was edited by: Siegfried Szameitat

  • 0FI_GL_12 delta safety interval

    Hi
    I am using 0FI_GL_12.
    Requirement is to run the delta every 2 hours.
    I want to know if there is any time limit contraint between 2 delta loads.
    can be there any issue if I start loading delta every 2 hours for this datasource.
    Thanks
    Navneet

    Hi Revanth
    0FI_GL_12 is replacement of 0FI_GL_10
    your SAP should be ECC 6.0
    There are certain modifications you need to do in R/3 side then only you can see 0FI_GL_12 in business content datasources.
    Changes are mentioned in SAP notes.
    Also you need to write start routine for calculation of key figure 0BALANCE as this datasource does not contain 0BALANCE values
    and they are always calculated in BI in start routine which is also provided in SAP Note:
    Please refer to the following SAP notes and the link :
    1153944 -> R/3 settings
    1233941 -> start routine for 0BALANCE
    1392817-> 0FI_GL_12 delta concept and compariosn with 0FI_GL_10
    link: [0FI_GL_12 FI new datasource;

  • Doubt on generic

    hi bw gurus,
    i am having one doubt in generic deltas.  if you are using calendar day for generic deltas suppose if i extracted data today and there are deltas posted after 3 pm. if i want to extract delta records after 3 pm.  is the calendar day option will work fine for that. or what is the scenario explain.
    explain about the safety intervals how it works will calendar day.
    what is BCS. can any one provide me the material for BCS.
    good links and good answers will be given points.

    Hi,
    Docs on BCS...
    http://help.sap.com/saphelp_nw04/helpdata/en/aa/29673a9011fc7be10000000a11402f/frameset.htm
    /people/thomas.jung3/blog/2004/09/08/sending-e-mail-from-abap--version-610-and-higher--bcs-interface
    http://help.sap.com/saphelp_nw04/helpdata/en/a3/295c3c76054953e10000000a11405a/frameset.htm
    BCS
    SEM-BCS
    BW-BCS
    SEM-BCS WITH BW
    Hope this helps...
    Thanks,
    Raj

  • Regards Generic Delta

    Hi Guys,
    I have a small doubt regarding Generic Delta Extraction. In Generic Delta i choose Calday on Posting Date. And  am getting data on Daily basis. Here My doubt is can I use this posting date in field selection in Info package. If not?Please give me clarification regarding the same.
    Thanks,
    Tg.

    Hi Tg,
    If I have understood correctly, Posting date has been chosen as the delta field in datasource.
    I don't think you can use the fiield in infopackage selection because the field is used to extract delta for that generic datasource  and the system doesn't allow us to put a filter on the filed which is responsible for delta .
    If system  wud have allowed us to put a selection on that field then correct delta will not be loaded in BI.
    System can not allow us to play with deltas and hence the field is not avaialble for selection .
    Hope it helps,
    Manish Sharma

  • Regd Safety Interval Lower Limit for Generic Delta

    Hi All,
    Safety Interval Upper Limit =1  for a Generic Delta would get Delta based on yesterday's BW data.
    What would Safety Interval Lower Limit would do for a Generic Delta .
    Your inputs please
    Sree

    Hi,
    just a short example:
    you run a init today --> 20070525  (internal date format).
    for the next delta tomorrow the system takes the last extraction date - 1 day so 20070524 for data selection and will store 20070526 as last extraction date and so on.
    This is to make sure that you will get all additional records extracted which were changed or created on each extraction date, but after last extraction. OK, you will get some records twice, but therefore you normally post the data to a ods via overwrite mode and this will take care about the 'real' delta while doing the further posting to the cube.
    Hope this helps
    kind regards
    Siggi

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

  • What is safty delta and safety interval

    Hello,
            PLease tell me What is mean by Safety Delta and Safety Interval?

    Hi,
    Safety interval should be set so that no document is missed – even if it was not stored in the DB table when the extraction took place.
    Example for Determining Selection Intervals with a Generic Delta:
    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
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Assign points if this is needful.
    Rgs,
    I.R.K

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

  • Reg Generic FM Delta

    Hi Friends,
                     For generic extraction I created the function module and its working fine. My requiremnet is how to set up delta for this function module ?
    Actually in this FM  I had 3 keyfields. But in RSO2 generic delta only one field is possible and i think I can not use for FM time stamp and calender day and .
    In this case how i set the delta for my FM for these 3 fields ?
    Can you please suggest any one and ur answers are highly appreciable and
    points will be award.
    Thanks & Regards,
    Govind.

    You could do the following:
    Create an extra table with the keys. When you pass data to the BW store the key in this table and make sure that you don't pass any key twice.
    But I would recommend to do a full upload and do the delta with a DataStore-Object (ODS). You need to select all data anyway so you won't save a lot of performance if you do it in the source system.
    Best regards
       Dirk

  • Safety Intervals for Generic Delta

    Hello Gurus,
    I want to know about safety upper limit and lower limit for generic delta.
    I have gone through the previous threads related to this topic and i am not able to understand completely.
    can anybody explains me this in detail with example in terms with Calday, Timestamp & Numeric pointer.
    Thanks in advance.

    There is very good example was exist on wiki.
    please search and help yourself.
    Use Google search by using search term " wiki generic delta".
    You will get what you need.

  • 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

  • Generic delta has problem with delts pointer time stamp

    Hi All,
    We have generic delta data source with Delte pointer as Time stamp. We have not used any safety limits. We are loading the data to DSO and using Additive delta. But the problem is when delta flag is set, there might be a case where some records still being inserted to table with lower time stamp. These records are not being fetched in next delta.
    We are planning to keep a safety upper limit of 5 min so that those records can not be missed. But we have a doubt as it is a Additive delta duplicate records will be loaded. If we make the delta to 'new status to changed records', it is going to work?? Any other things we have to check when we make this changes??
    Thanks
    Haaris

    Hi
    If you had selected additive delta then you can load data to DSo with addition mode only. No overwrite possible.
    If you want to select new or changed status then you can load to DSO with overwrite mode only.
    Additive or changed delta depends on your requirement because if you want to add data to the DSO then you can go ahead with additive otherwise you have to use DSO with overwrite mode only.
    You can either give safety upper limit or lower limit but if you give safety lower limit then you can only load data to DSO with overwrite mode because there could be some duplicate records.
    Hope it clarifies.
    Regards
    Sadeesh

  • Generic Delta issue..

    hi experts,
    i have created Datasource based on view which is based on EKPO and EKBE tables.
    i have date fields BUDAT, CPUDT  and CPUTM.
    I have selected CPUDT as Delta Field.
    select Calendar Day and Safety Interval Upper Limit as 1.
    I have initialized yesterday, though the records are created and i can see the new records with today's date, in RSA7 i cannot see any records.
    what is the issue in it, do i need to change delta field as CPUTM as it is time.
    if yes then how can i set the Delta to capture the Delta Records?
    regards
    venuscm

    Hi,
    All three fields are from EKBE table, so kindly check whether there is any change in source system table EKBE, for these fileds for the new records created.
    New record created will be updated in table EKPO and EKKO only.
    Also make sure that delta field should be one of the extracted field in your generic extractor.
    wish u all the best
    Regards,
    Vinod

  • 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

Maybe you are looking for