Delta  loading in Generic extraction

Hi Everybody,
            Can anybody explain the procedure of delta loading in generic extraction.
With Regards
Raju

Raju,
Just goto RSO2->Enter your datasource name->Click Generic Delta
Select one in Delta Specfied field.
Either Time stamp or Calender day or numeric Pointer.
If you select Numeric Pointer then enter the filed name on which you want to creat delta in Field name.
Or just browse in Field name , it will display you all valid fields for delta.
Check new status for changed records.
Now save.You know the next steps.
If you need any thing else.Buzz me.
Thanks
Ram
"BW is Everywhere"
Then make necessary setting in setting.
Safety interval upperlimit-1
Safety interval lowetlimit-1

Similar Messages

  • Delta loading of generic data source.

    Hi,
    please tell me the procedure for How to load Delta data For generic data source?

    Hi
    You can use the following procedue
    Enabling Delta Load
    Use
    You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
    Prerequisites
    You have launched the Maintain Generic DataSources tool of SAP BW.
    Procedure
    1. Configuring Generic DataSources
         1.      In the DataSource pane, choose  next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
         2.      In the Change DataSource maintenance screen:
               a.      Set Applic. Component to BW.
                b.      Choose Save.
        3.      In the Create Object Directory Entry dialog box:
                a.      Choose Local Object to see the DataSource information.
                 b.      Choose Save to return to the Change DataSource maintenance screen.
      4.      Choose Generic Delta. In the Generic Delta dialog box:
                a.      Browse Field Nm. to select the delta-relevant field.
               b.      Mark the Time stamp radio button.
                c.      Mark New Status for Changed Records.
    5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
    ○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
    ○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
    6.      In the DataSource: Customer version Edit screen, save all data.
    2. Activating DataSources
           1.      Launch the SAP BW Administrator Workbench and go to Modeling.
          2.      Open the list of InfoSources and select the DataSource assignment you want.
          3.      With the secondary mouse button, choose Replicate DataSources.
          4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
          5.      In the InfoSource Change screen, choose with the quick info text Activate.
    Initializing Delta Load
    Prerequisites
    You have configured the DataSource for the delta loading process. For more information, see Enabling Delta Load.
    Procedure
    1. Starting Delta Initialization
         1.      Launch the SAP BW Administrator Workbench and go to Modeling.
         2.      From the Modeling pane, click InfoSource to populate the InfoSource pane and select the InfoPackage you created for the InfoSource in, for example, Example of Data Extraction.
          3.      From the Update tab page, activate the Initialize Delta Process indicator.
          4.      To define parameters to be used for the delta load process, go to the Data Selection tab page and define relevant parameters.
          5.      In the Schedule tab page, choose Start to begin delta initialization.
    If you defined parameters to be used in delta load (step 4 above), use PSA in the modeling component of Administrator Workbench  to view the request results.
         6.      To check when delta initialization is finished, go to the Maintain InfoPackage screen of the Monitor u2013 Administrator Workbench and press F6.
    2. Monitoring Delta Initialization
         1.      Launch the BW Delta Queue Maintenance and select the DataSource in question.
         2.      Use the secondary mouse button to see the current pointer value in Generic Delta Current Status.
         3.      You can delete the delta initialization (if you want, and subsequently create a new delta initialization) in Scheduler (Maintain InfoPackage) by choosing the delta request from Initialization Options For Source System and choosing Remove.
    In this screen, you can also check the status of the delta initialization request.
    To see the content and results of the delta initialization request, go to PSA in the modeling component of Administrator Workbench  to view the request results. 
    3. Running Delta Load
    You can run the delta load process only after delta initialization has been completed.
         1.      Open the InfoPackage and in the Update tab page activate the Delta Update indicator.
          2.      Go to the Schedule tab page and choose Start.
    *Enabling Delta Load *
    Use
    You must first configure and modify the DataSource to be used for delta loading in CAF and SAP BW integration and define delta-relevant attribute fields.
    Prerequisites
    You have launched the Maintain Generic DataSources tool of SAP BW.
    Procedure
    1. Configuring Generic DataSources
          1.      In the DataSource pane, choose  next to the Transaction data field to select the DataSource to use for CAF and SAP BW integration and choose Change.
         2.      In the Change DataSource maintenance screen:
            a.      Set Applic. Component to BW.
            b.      Choose Save.
        3.      In the Create Object Directory Entry dialog box:
               a.      Choose Local Object to see the DataSource information.
                b.      Choose Save to return to the Change DataSource maintenance screen.
       4.      Choose Generic Delta. In the Generic Delta dialog box:
           a.      Browse Field Nm. to select the delta-relevant field.
           b.      Mark the Time stamp radio button.
           c.      Mark New Status for Changed Records.
      5.      In the Selection of field determining delta dialog box, select the following delta-relevant fields:
    ○       For the entity service DataSource, select the field corresponding to LASTCHANGEDAT.
    ○       For the application service DataSource, select the field corresponding to delta-relevant field specified by BW extractor method developer.
       6.      In the DataSource: Customer version Edit screen, save all data.
    2. Activating DataSources
       1.      Launch the SAP BW Administrator Workbench and go to Modeling.
       2.      Open the list of InfoSources and select the DataSource assignment you want.
      3.      With the secondary mouse button, choose Replicate DataSources.
        4.      Select the same object from step 3 and choose Change Transfer Rules with the secondary mouse button.
      5.      In the InfoSource Change screen, choose with the quick info text Activate.
    Hope this helps
    Regards
    Shilpa

  • Delta loading through Generic extractor - function module not found

    Hi,
    I'm working on a BW3.5 system and we have some generic delta FM extractors. One of these is called ZBW_CONF_DELTA and the FM is also called ZBW_CONF_DELTA. It is a delta-enabled extractor. Whenever an extraction is done in the init delta mode, the data gets picked up from SAP.
    However, whenever we load subsequent deltas, the extractor brings zero records. When I look in the SM37 logs in R/3, it says "Function module /BIC/QIZBW_CONF_DELTA0001 does not exist"
    I'm not sure where the "/BIC/QIZBW_CONF_DELTA0001" function module name came from, because I haven't given it like that (if I did, the init load would also have failed).
    Due to this problem, I'm unable to perform any delta loads. Is there anything I could be doing to fix this?
    Regards

    Hi,
    First check how extractor works in R/3 side using RSA3
    Make a full load.
    Now check the generic delta field of your generic extractor, lets say changed on date.
    Do the SAP transaction ( take help from some Functional COnsultant ) to update that delta field. Note that record.
    Now if u do the delta load with same extractor, you are suppose to get that record.
    If not then there is some problem with FM or extracor.
    Let me know what happens.
    Thank-You.
    Regards,
    Vinod

  • Full to delta load in generic extration

    Hi All,
    I am loading the data form R/3 to BW with full load by using the generic data sources.
    Now I need to change the full load to delta. But I get the data 2 views and one FM.
    Some what I have got the solution, that is going RSO2 there generic delta will be available
    If I click I will get the one wind there 3 deltas form there I took time stamp. Then I need
    Select the field name.
    1) Now only my problem started in that field name there is no creation
    Date and last changed data, based on this we need to get the data from R/3 to BW.
    2) In that 3 datasorce I used the one DS function module in this also that field name is not
    available .
    3) In safety interval what I need to give.
    Please help on above 3 issues.
    Thanks
    kumar.

    Hi,
    plz check with this most proberly it works.
    Go to RSO2 >> Now select the right option(Transaction data,Master data attributes or texts) >> Now in the next screen enter the Application Component >> enter the descriptions >> Now select how you want to populate data in your data source .....following options are there :
    View/table >> Choose the extraction from view button if you want to want to extract the data from a transpatrent table or database view,and enter the name of the table or view...the extraction structure of the generated datasource is then identical to that of view or table.......
    SAP Query/Infoset>> Choose the extraction from query button if you want to use SAP query infoset as datasource..then select the required infoset from the infoset catalog...you can go to the screen for maintaining an existing infoset by double click on its name...
    Function Module
    To make your datasource delta enable >> Click on Generic Delta on the top >> Here first give the field name .This field from the extract structure of a DataSource meets one of the following criteria:
    1. The field has type: time stamp. New records to be loaded into the BW using a delta upload have a higher entry in this field that those which have already been loaded.
    2. The field has type: calendar day. The same criteria applies to new records as in the time stamp field.
    3. The field has another type. This case is only supported for SAP Content DataSources. In this case, the maximum value to be read must be displayed using a DataSource-specific exit when beginning data extraction.
    Now choose one of the three options :
    Time Stamp
    Calender day
    Numeric pointer...
    Safety Interval Upper Limit >>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.
    DataSource Is Real-Time Enabled
    The "Real-time enabled" indicator determines whether a delta-enabled DataSource can supply data for a real-time demon.
    If the DataSource finds the delta generically using a delta-relevant field, observe the following with regard to the safety intervals:
    The safety interval at the lower limit may cause redundant data to arrive in BW. This data is not suitable for InfoCubes and ODS objects with key figures that are updated in appended order. With real-time updates, the redundancy of the data is increased by the short time spans between the individual runs of a real-time demon. With a lower safety interval of 2 minutes and a demon frequency of one per minute, all data may potentially arrive in the PSA three times. This can lead to database and runtime problems.
    The safety interval at the upper limit makes the data less up to date. How up to date the data is with real-time is always the sum of the upper safety interval and the time span between two runs of the demon.
    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.

  • The delta load for generic machine in CRM doesnt run.

    When the machine was dismantled from a location and installed on a different Functional location. The changes didnt download to CRM. Even the request load fails for the same. The machine is a generic Machine.
    In R/3, the queue is in STOP status and gives the error Generic stop set on activation.
    User had changed the Functional Location for a Generic machine in R/3. The changes didnt upload to CRM. Even the request load failed to upload the changes.
    The Idoc is failed on R/3 , it gives the error message - Generic Stop Set.
    Thanks in advance

    Hello Mohammed,
    I have also met with this issue in the past, and I have resolved it by steps described in this link: http://scn.sap.com/docs/DOC-56972
    Hope it helps.
    Best regards,
    Jerry

  • Difference between Generic extraction and Generic Delta

    Hi Experts,
    Pleasee give of some information below  query:
    1) Difference between Generic extraction and Generic Delta.
    2) How to achieve Generic delta.
    3) When we go for Generic delta instead of generic extraction.
    Advance ThankU. Points vl be assigned.
    Thanks,
    Ragu.R

    Hi,
    Generic delta is the delta load done using Generic DS.
    Generic extraction
    Usage:
    1. When the standard extractors are not supporting the extraction what you need. If SAP does not have a standard extractor for your need to get data from R3, you would have to go for generic extractor.
    2. If you create a custom object say by combining certain base tables in R3 say custom tables ZTAB1 and ZTAB2. These two tables are not SAP provided tables and there will not be any standard extractors. So cases like this you will have to go for generic extractors.
    How:
    You have to use RSO2 transaction and you can also set delta based on, one of the three characteristics such as timestamp, calday or pointer (a sequence no).
    once you create it and activate it. The extractor will be available in ROOSOURCE - (table in R3 where all the data sources are available).
    Refer:
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    http://help.sap.com/saphelp_nw04/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/content.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Generic Extraction via Function Module
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    thanks,
    JituK

  • Deltas in generic extraction

    how can we set delta updates in generic extraction?can any one help in this

    Hi Praveen,
    Please do check the link for step by step for generic extraction
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    check the following
    http://help.sap.com/bp_biv235/BI_EN/html/bw.htm
    business content
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/biw/g-i/how%20to%20co-pa%20extraction%203.0x
    https://websmp203.sap-ag.de/co
    http://help.sap.com/saphelp_nw04/helpdata/en/37/5fb13cd0500255e10000000a114084/frameset.htm
    (navigate with expand left nodes)
    Check these links:
    /people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
    /people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
    /people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
    /people/sap.user72/blog/2005/02/14/logistic-cockpit--when-you-need-more--first-option-enhance-it
    /people/sap.user72/blog/2005/04/19/logistic-cockpit-a-new-deal-overshadowed-by-the-old-fashioned-lis
    <b>For Generic:</b>
    >Go to Tcode : RSO2,
    >There give the name of data source which you want to create like transaction data source or master data attribue or Text data source.
    >enter
    >again in the next screen you need to give application like SD or MM etc
    >in the same screen need to select table/view or infosetquery or function module. these are different ways of creating data sources.
    >Give the name for the same like if u r creating data source on table give the name of table.
    >click on Generic delta which will there in application tool bar and fill the required columns in that screen like type of delta and all
    >continue and save
    >it will give all the fieds
    >enable the check boxes based on your requirement like selection or hide or field only..
    >save
    Hope This Helps.
    Regards,
    Ravikanth

  • Delta load from r3 to bw ?

    i have one question on the mechanism of data transfer from r3 to bi 7.0. the followings is my concerns:
    scenario:
    The total numer of data is 1000 rows and these rows are seperated into 10 data package , each package contains 100 rows.
    Now bw is trying to recieve these 10 packages from r3 in sequence.
    When 5 data packages have been transfer to bi psa. the network is broken and the tranfer is canceled at the 6th data package.
    What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
    How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS.
    How to find out how many records have been transfered from r3 to bw while the transfer has ended in
    the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube.
    Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle ?
    What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer.
    And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
    Last doubt, what is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request ?
    What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
    How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
    Please I am having all these doubts and I want you SAP experts to answer them please so that I can clear my doubts in production support . I really appreciate if someone explain me the scenarios here. It will be a really great help if someonce clears these doubts.

    Hi......
    What i want to know is when the network is reconnected ,Does the transfer start from the 6th data package?
    If your connection is broken in between......inspite your load is through PSA...........you have to delete the request from the target(after making the QM status red)............then you have to reload it again............But before repeating the load check the connection is ok or not in SM59........
    How to find out whether its a delta load or a full load if a transfer is scheduled from r3 to bw ? For both CUBE & ODS
    This you can check in IP scheduler in the Update tab...........whether it is delta or full load.......
    or you can also check in IP monitor(You can go here through RSMO..........IP monitor screen will open directly here............or you can also go through RSA1>> Find your IP >> Double click on it >> Click on the monitor icon in the top >> From the you will go to the IP monitor>> the under the Header Tab you can see whether it is a delta or Full update...........
    Or you can check the datasource also..........
    If it is a generic datasource go to RSO2..........and check...........If it is a standard datasource check it in RSA5...........
    How to find out how many records have been transfered from r3 to bw while the transfer has ended in the middle ? I mean how to check how many records have been successfully transfered from r3 to cube/ods .Please tell me for ods as well as cube
    Your load cannot be ebded in the middle.........it can failed.............if it fails then you have to delete the request from the target..........and then repeat the load.......
    Is the continuation of transfer process is same for both ODS & INFOCUBE, if it ends in the middle
    Yes.........
    What is the procedure for full load & Delta load in case of CUBE & ODS ? I mean how to reschedule the transfer
    If a full or delta load fails after extraction got completed due lock issue or SID issue.....etc..........and if you load is through PSA.............then just delete the request from the target without making the QM status red.......and reconstruct the request.........no need to repeat the whole load again........
    But if you r load is not through PSA..........then make the QM status red........delete the request from the target........and repeat the load...........
    And if the whole scenario is is in the support, SO I will be handling these issues on the live production server. Am I right ? So in this case my user id should have access to all the production r3 and production bw to do these change status to red and delete the request and reload the request etc., So I should be logging on to the production server and do all the manipulation, Am I right ?
    Yes.......
    What is repair request and so if the transfer stops in the middle we change the status to red and reload the request again , Is it called repair request or reload request?
    Suppose you delta load has failed ............and you have deleted the request from the target without making the QM status red............In this case your data will be lost and your delta mechanism will get corrupted............In this situation.............
    1) Delete the init flag........
    2) You have to do Full repair..........(After filling the set up table)
    3) Init without data transfer to set back the init flag
    4) Then Delta upload.............
    In case of an ODS............you cannot load Full update and delta upload parrallely..............Your ODS activation will fail...........suppose you want full upload in the ODS..............then you have to go for Full repair............
    What is the difference between repeat delta & repair request & repair delta ? When do we choose these options, In which scenarios ?
    I think Full repair concept is now clear............
    Suppose your delta load fails...........After that you delete the request after making the QM status red............Then system will ask for a repeat delta when you will try to repeat the load...........which means it will pick the same delta records of the failed load..........
    How do we schedule a daily load job from r3 to bw without the use of process chains ? I mean daily it should fetch the records from r3 to bw from the SD datasources at 10.00 PM ,how do we do that ?
    This you can do via infopackage or infopackage group...........schedule it at the specific time.....
    Check these links :
    http://help.sap.com/saphelp_nw04/helpdata/en/20/ad673844a7114be10000009b38f842/frameset.htm
    Re: Schedule Infopackage for last day of a fiscal period
    Hope this helps you.........
    Regards,
    Debjani...........

  • I can not make delta load for some component of public sector management

    Hello All:
    I´am using these three data source 0PU_IS_PS_31, 0PU_IS_PS_32 and 0PU_IS_PS_42 and I realize that I can not make delta loads. When I make the full load everything is correct even when I made the delta, the problem is that the Delta load is not extracting any new data or changed data.
    Do you have any idea to fix this issue?
    Thanks
    Message was edited by: Víctor Olivera

    Hello Victor,
    As u have already tried the delta load,I assume that u have already done the init load too.As system will not allow u to do delta load without doing an init load first.
    The first datasource u talked about..31..it needs new records created in table FMIOI table.
    What happens is..if u run a delta load immediately after an init load,there might not be new or changed records created in the system..therefore there arent any records in the delta queue.
    Could u try creating some commitment document transaction data,so that records get added in FMIOI table.Then see if the delta queue for this datasource shows any records.
    Links to BC pages for these datasources are below..
    http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c425e8afe11d496d80000e835339d/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/1a/8c42618afe11d496d80000e835339d/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/46a53ec5f0c0428fa8b9cfcdcd9fcd/frameset.htm
    Note that for 42 datasource..page says that delta update is not supported(though it does talk about updating delta queue).
    For 32 datasource source tables are FMIFIIT and FMIFIHD.
    For 42 datasource table is FMBDP.
    cheers,
    Vishvesh

  • Delta loading to BW and archiving

    Hi Expert
    We have ERP2004 and BW.   For loading data from ERP2004, we use both full and delta upload.  We are currently planning to implement archiving in ERP2004.
    Especially MM PO (purchasing order) documents is the target for archiving.  I have question here.
    If we archiving tables which are loaded to BW with delta upload,  is data in BW also deleted?
    We do full loading to BW for PO document table, but related tables like STXH, STXL, ADR2, ADRCT, we do delta upload. I am afraid that data inconsistency will occur.
    Thank for your advice in advance.

    In my opinion, if you are using standard data sources for loading in delta mode, it will delete archived documents from BW tables also unless you write a specific routine for field ROCANCEL and value R (used for deleted records).
    In case of full load, data will not be deleted from BW system unless you are doing a delete and full.
    If you are doing a delta load using generic data sources, it will not bring any deletion to BW system unless you have specifically written some code to find the deleted records and send those to BW.
    I hope it helps.
    Regards,
    Gaurav

  • Generic Extraction Delta Loads

    Hi Experts,
    I am facing problem is I want to extract the data in Generic Extraction in View, Suppose my requirement is I want to delta loads every 1 hour per day, how can i do, Generic Extraction possible are not delta records.
    Note:- LO Extraction is possible like we have update mode we can scheduled hours in everyday, But Generice Extraction possible are not.
    Please provide me solutions ASAP.
    Thanks in Advance......
    Regards,
    Bharathi.

    There are various delta method
    1.calday.
    2.time stamp.
    3.Numeric pointer.
    For youe requirement Time stamp will work.
    Please check weather you have any field related to time.
    Thanks,
    Saveen kumar

  • 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

  • Generic extraction loading and performances issues

    hi,
          any one can give the details about the generic extraction loading as well as performance issues.
    advance thanks
    regards
    praveen

    Hi,
    when there is no suitable business content datasource we go for creating generic data source.
    by using generic data source we can extract data present in single or multiple tables.
    If the data is present in the single table we go for generic data source extracting from table.
    If the data that is to be extracted is present in multiple tables and the relation between the tables is one to one and if there is a common field in both the tables we create a view on these tables and create a generic data source extracting from view.
    if you want to extract data from different tables and there is no common field we create a info set on these tables and create a generic datasource extracting from query.
    if you want to extarc the data from different tables and the relation is one to many  or many to many we create a generic data source from function module.
    If we extarct from function module ,at run time it has to execute the code and brings the data to BW.so it degrades the loading performance.
    regards,

  • Deltas for generic extraction.

    Hi,
    if i want use time stamp & calday  for my generic extraction , i can use uppercase and lower case, wher can i give timings suppose want run deltas for 10am-10.30am.
    regards
    anitha

    Hi,
    Security 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 security interval for the upper limit is 120 seconds. The selection interval for the delta request is: 12:00:00 to 12:28:00. When the extraction is finished, the pointer is set to 12:28:00. Security interval lower limit The delta-relevant field is a timestamp. After images are transferred. In BI the record is overwritten with the post-change status, for example, for master data. Any duplicate data records do not affect BI. The last read timestamp is 12:28:00. Delta extraction begins at 13:00. The security interval for the lower limit is 180 seconds. The selection interval for the delta request is: 12:25:00 to 13:00:00. When the extraction is finished, the pointer is set to 13:00:00.

  • Delta for Generic Extraction

    Hi all,
    Can anyone tell about delta for generic extraction i.e 3 options in detail and when do we use it.
    thanks in advance,
    chandra sekhar

    When you want to customize existing datasources at R/3 sides then you can do that with customer exits.
    Suppose if you want to add a column to the existing datasource then you will use append structures (Transaction SBIW-> Edit Data sources - Enhance Datasource) then to fill the column you will write the code in these Exits.
    There are 4 types of Exits available.Function Group (XRSA)
    EXIT_SAPLRSAP_001 Customer Function Call for Supplying Transaction Data
    EXIT_SAPLRSAP_002 Customer Function Call for Supplying Master Data (Attributes)
    EXIT_SAPLRSAP_003 Customer Function Call for Supplying Text
    EXIT_SAPLRSAP_004 Customer Function Call for Supplying Hierarchies
    As you are aware there 4 types since the datasources in R/3 are predefined to fill the data of BW viz, attributes,Text,Hierarchy and Transaction.
    Check the below forum discussion for more information..
    DataSource Enhancement
    Regs
    Gopi
    Assign point if it helps ...

Maybe you are looking for