CRM Delta Extraction Problem

Hi,
I have my standard DS and I am able to see the data in RSA3 but when I do a delta load it is returning 0 from 0 records.
How do I enable delta for this DS (This is a CRM DS)
Thanks & Regards.

Hi Ganesh,
There might be different issues related to this like authorization etc.., Always make sure that data source is activated in BWA5.
Check these links:
CRM data to BW .. some issues
No data when extracting using 0CRM_SRV_PROCESS_H
Hope this helps.......
Rgs,
Ravikanth.

Similar Messages

  • Master Data Delta Extraction Problem

    Hi,
    I have this problem. When loading delta data from 0BPARTNER_ATTR infosource, BW informs me "Short dump in the Warehouse". When I go looking for it, there is none. Once I got to the infopackage->scheduler, the system reports "Request the repeat?", and I go "Continue", but the data load never begins. Does anybody knows what it's wrong?.
    I'v been doing some work-arround: start a new init load, but this is good for two or thre days (delta loads), and then the delta stops working.
    any ideas where to look for the problem?
    thanks for the help.
    Mauiricio

    Hi Mauricio,
    maybe it depends by the number of records in delta quque. If you have a daily lot of changes in a Master Data the system is no more able to extract the data in tables for change pointers. Also maybe that you have to cancel entries on the tables of changed data.
    Check the quantity of delta records for every day, and then check also if it is possible to update this master data frequently.
    Ciao.
    Riccardo.

  • 0FI_AP_4 - Delta Extraction Problem - Please help

    Hi,
         I activated the business content ODS 0FIAP_O03 and the relevant infosource for Accounts Payable and also did the init. In R/3 I created an Invoice using FB60 transaction and Posted the payment using F-53 transaction. I can see the document in BSAK table which the 0FI_AP_4 extractor is using but when I see the delta queue in RSA7 there are 0 records for the extractor 0FI_AP_4 which means the new changes are not pushed to the delta queue. Please help.
    Thanks.

    Hi Thiagu,
    Try running a delta load 0FI_AP_4 using the tcode RSA3 in your R/3 system? Are you seeing your document there?
    I would also check RAS7 in R/3, and to make sure the delta init has taken properly. You can also check for your document there.
    HTH

  • Problems with Delta Extraction for 0CRM_OPPT_H (no data found)

    Hi,
    I've some problems with the Delta Extraction of the Infosource 0crm_oppt_h (CRM Opportunities Header). After initialization I get no delta data from the CRM system.
    What I already did:
    Activated 0crm_oppt_h Data Source (checked functionality with rsa3)
    Started Info Package (Init) on BW side (worked fine)
    Checked the status of the Data Source on the CRM system using BWA7 ("initial upload" is unmarked; "delta active" is marked and what makes me worry is that the column "Queue exists" in <i>unmarked</i>...)
    If I change anything (like Phase, Expected Sales Vol.) in the opportunity, the Delta Extraction get no changes.
    Could You help me out, please?
    Best regards,
    Markus Svec

    hi Markus,
    try to check oss note 788172
    Release Status Released for Customer
    Released on 23.03.2005
    Priority Correction with high priority
    Category Program error
    Symptom
    No data exists in delta extraction from the CRM server to the BW system for business transactions, if parallel processing is applied as per note 639072. But Data is extracted if parallel processing is switched off.ie. when BWA_NUMBER_OFF_PROCESSES is set to 1,there is data during delta. This applies to the following DataSources:
    0BBP_TD_CONTR_1
    0CRM_COMPLAINTS_I
    0CRM_LEAD_ATTR
    0CRM_LEAD_H
    0CRM_LEAD_I
    0CRM_OPPT_ATTR
    0CRM_OPPT_H
    0CRM_OPP T_I
    0CRM_QUOTATION_I
    0CRM_QUOTA_ORDER_I
    0CRM_SALES_ACT_1
    0CRM_SALES_CONTR_I
    0CRM_SALES_ORDER_I
    0CRM_SRV_CODES
    0 CRM_SRV_CONFIRM_H
    0CRM_SRV_CONFIRM_I
    0CRM_SRV_CONTRACT_H
    0CRM_SRV_PROCESS_H
    0CRM_SRV_PROCESS_I
    Other terms
    DataSources, BWA, initial extraction, delta init, parallel processing, no data in delta.
    Reason and Prerequisites
    There is an update on the generated delta table which causes data corruption in running delta initializations as the changed delta sets will be deleted with every further update on documents. An open cursor statement is there without fetch data in SMOX3_GET_DATA.
    Solution
    The problem is solved with the attached corrections.After applying the corrections a new initialization of the affected datasources is necessary.

  • Problem while delta extraction

    Dear Experts,
    I am facing a poblem while delta extraction for AR ODS. When I check the status of delta extraction it shows green and records transferred as well but when i check into BW side I find some records missing. When I faced this problem for first time I did the init load again after which all records came into BW side but subsequently again when some changes were made in R/3 side and delta was uploaded, again the same records were found missing.
    If anyone has any idea why this is happening please guide me as to how to go about it. Also I have given no filter conditions in data selection.
    Thanks in advance. Will assign points happily for any kind of assistance.
    regards
    akshat

    Hi,
    the standard delta extraction is not sensitive to program in the R/3 side that write directly into tables. For my experience, this is the only reason when the delta does not work.
    So, check with the R/3 people, if they are input account document by write directly into BSIS or BSAS.
    Rgs
    Antonino

  • A problem with 1CL_OLIS002 and 1CL_OMAT001 extractors - delta extraction

    Hi
    I have a problem with 1CL_OLIS002 and 1CL_OMAT001 extractors - delta extraction.
    Interrelated extractors: 2LIS_11_VAITM and ZMATBATCH_Attr work well.
    For 1CL's extractors I see current data in RSA3 but I don't see LUWs in RSA7.
    Extractors send 0 records to BW.
    There is no entry in "BIREQU* " job logs like this:
    "Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with xxx records".
    which I find in job logs when all worked well.
    We had some problems with R3. I had to restart job "LIS-BW-VB-APPLICATION_13*".
    May be it has influence on these extractors?
    Any suggestions about how to resolve the problem?
    Regards
    PWnuk

    Hi
    Can you please share the solution of this problem with me,I am also facing same issue of Delta not working but full load is working in 1CL_OBI_001?
    Edited by: Aseem84 on Jan 12, 2011 10:23 AM

  • CRM- BI extraction

    hi experts,
    am working on Netweaver 2004s, CRM5 & BI7.0.
    every day we used to do CRM - BI extraction.
    now we are facing a problem.
    when i click "manage" on datasource, it is asking for user id & password.
    once i gave that, am able to proceed. again, after executing the infopackage, in the monitor, it is showing, zero records.
    in sm59, it is showing production BI & CRM connections test ok.
    kindly suggest me what to do? its very urgent & important.
    jeeva

    Hi Jeeva,
    If you are viewing the source system's datasource from BW system then it'll ask for the User ID and Password, and in the monitor if you have 0 records check the dat in RSA3 in source system. Also some of the extractors of CRM doesn't support delta mechanism.It will extract in the init. load but from delta load it'll not load due to authorization issue. EX:-  0CRM_SRV_PROCESS_H
    No data when extracting using 0CRM_SRV_PROCESS_H
    Rgs,
    I.R.K

  • Business Partner Items (0FC_BP_ITEMS) delta extraction help

    Has anybody used 0FC_BP_ITEMS extractor? The documentation says that it supports delta, but it needs to be enabled.
    I did enable delta extraction in IMG as SAP help site suggested. However, the documentation also says that before running delta, I need to update/initialize it in tcode FPOP. I go to that tcode, but I can hardly understand what to do in that tcode and there is no help or documentation I can find on how to initialize that delta extraction for 0FC_BP_ITEMS in OLTP system.
    anybody came across any help document on FPOP tcode?
    Thanks

    Have you found a solution to the problems you were facing? is there any documentation you have regarding the BP Items extractor.

  • Error while doing DELTA Extraction

    Hi BW Experts,
    In my R/3, I have a generic data source ZBUT_VW.
    It receives data from a View which is created based on couple tables.
    When I do full load to the corresponding ODS, it is successful.
    But after that I delete the ODS and created CUBE with DELTA
    I have Initialized delta.
    When I do DELTA extraction, it fails.
    The error
    “The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
    and/or
    the maximum wait time for this request has not yet run out
    and/or
    the batch job in the source system has not yet ended.”
    I delete the initialization load and trying to do DELTA extraction again and it Fails With the same error
    Please let me know how can I resolve this problem.
    URGENT
    gaurav

    I dont think it is possible to have to additive delta with creation date.
    Try a full load to cube to check if the extractor is working.

  • Error while doing DELTA Extraction (generic data source)

    Hi BW Experts,
    In my R/3, I have a generic data source ZBUT_VW.
    It receives data from a View which is created based on couple tables.
    When I do full load to the corresponding ODS, it is successful.
    But after that I delete the ODS and created CUBE with DELTA
    I have Initialized delta.
    When I do DELTA extraction, it fails.
    The error “The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
    and/or
    the maximum wait time for this request has not yet run out
    and/or
    the batch job in the source system has not yet ended.”
    I delete the initialization load and trying to do DELTA extraction again and it Fails.
    With the same error
    Please let me know how can I resolve this problem.
    URGENT
    gaurav

    I dont think it is possible to have to additive delta with creation date.
    Try a full load to cube to check if the extractor is working.

  • Delta extraction for FI (AR & AP) data sources

    I tried extracting the data from 2 standard SAP data sources under FI module for Accounts Receivable.
    0FI_AR_10(Customer payment history via delta extraction)
    0FI_AR_5 (customer payment history)
    The data to be extracted into 0FIAR_C05(payment history) info cube.I assigned the 2 data sources to an info source and pumped the data into the cube via an ODS.Now the problem is with delta extraction.No records are picked in the delta extraction.So I checked in extractor checker RSA3 with delta update mode.I got the following error.
    "Could not determine BW release of logical system"
    Could some one resolve the issue?Thanks in advance.
    Thanks & Regards
    Vinay

    Hi ,
    Please go through 493422 note  once . see if suits to your requirement  follow it  accordingly .
    Thanks ,
    Anil

  • How to debug mapping function module during delta extraction?

    Hi experts,
    Somehow our delta is not working properly, and i would like to debug our mapping function module. How can i debug it during a delta extraction?
    Some info:
    Our source system is CRM and our extractor is extracting one order document (contracts in this case). I know that when we modify a contract, a bdoc is generated and then passed throught the mapping function then the extracted data to the delta queue. I just need to debug when the bdoc is being mapped to see what's wrong with the extracted data.
    Thanks in advance,
    Van

    Hi,
    Since you are using a Function Module for the Extraction. Edit the Function Module and give "BREAK-POINT" before the loop command. Check and activate the Function Module.
    Now Extract the datasource using RSA3. Now you can debug it. After checking remove the "BREAK-POINT" from the function module. Also Check and activate the same.
    Regards
    Jayaram M

  • Use of Update Table in Delta Extraction ....

    Hi all ,
           I have a small doubt regarding why there is an update table introduced between statistical table and delta queue in delta extraction process ... why not directly extract data from the statastical table and put it in to the delta queue .....
    Kindly help me regarding this ...
    Regards ,
    Santosh ....

    Hi Santosh,
    I think it is related to resource, batch and memory, problem. Infact you can use only delta queue if you select direct update, but you use this kind of update only for huge amount of data produced in a short period of time.
    The two queue let you divide transaction moment to batch collection moment.
    Hope this help.
    Ciao.
    Riccardo.

  • CRM-BW Extraction

    Hi,
    I read many threads, but cudnt find any final answer. Can you please let me know how to extract CRM (6.0) to BW/BI systems!
    What are the useful tcodes and how to enhance the Data Sources!
    Thnx.

    There is no interval settings required, like there are for FI. Here's the technical description of the CRM extraction process for both Full and Delta extraction.
    1) SAP BW calls the BW Adapter using the Service API.
    2) BW Adapter reads the data from the source table for the DataSource.
    3) Selected data is converted into the extract structure as a BDoc.
    4) The BDoc type determine the BAdI that is called by the BW Adapte.
    5) Data Package is transferred to SAP BW using the Service API.
    Some considerations for Delta are:
    1) Net changes in CRM are communicated via BDoc.
    2) The flow controller for BDocs calls the BW Adapter.
    3) BW Adapter checks if net change is in BDoc that's BW relevantci.
    4) Non-relevant net changes are not sent to SAP BW.
    5) Relevant net changes are transferred to SAP BW.
    6) CRM standard DataSources use AIMD delta method.

  • Generic Delta extraction by Function module issue

    Hello Experts,
    Please help !!!
    I have problem for delta extraction by Function module.  For the full load, I wrote function module based on RSAX_BIW_GET_DATA_SIMPLE. It works fine.
    But I would like to have the delta load enabled. Therefore, I modified the datasource, add a delta specific field u2018ztimestampu2019, which type is calendar day.
    Then I create a function module based on template u2018RSAX_BIW_GET_DATAu2019, as this support the upload mode. But when I test this datasource in RSA3, no matter itu2019s full load or initial delta load, it always send me an error, u201CErrors occurred during the extractionu201D.
    I had some debug, and found that there is no value  for i_isource when my function module is called. Therefore it raised the exception.
    But I do not have the chance to debug my code for the delta logic, can somebody help to check?
    I also check the entries in ROOSOURCE,
    For my datasource ZTRNREC_FM_DELTA, The DELTA value is u2018AIEu2019, and extraction method is u2018F2u2019, should I change them to DELTA= u2018Du2019 and extraction method to u2018F1u2019? Where to change?
    FUNCTION ZRSAX_TRAININGREC_DELTA.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(I_REQUNR) TYPE  SBIWA_S_INTERFACE-REQUNR
    *"     VALUE(I_ISOURCE) TYPE  SBIWA_S_INTERFACE-ISOURCE OPTIONAL
    *"     VALUE(I_MAXSIZE) TYPE  SBIWA_S_INTERFACE-MAXSIZE OPTIONAL
    *"     VALUE(I_INITFLAG) TYPE  SBIWA_S_INTERFACE-INITFLAG OPTIONAL
    *"     VALUE(I_UPDMODE) TYPE  SBIWA_S_INTERFACE-UPDMODE OPTIONAL
    *"     VALUE(I_DATAPAKID) TYPE  SBIWA_S_INTERFACE-DATAPAKID OPTIONAL
    *"     VALUE(I_PRIVATE_MODE) OPTIONAL
    *"     VALUE(I_CALLMODE) LIKE  ROARCHD200-CALLMODE OPTIONAL
    *"     VALUE(I_REMOTE_CALL) TYPE  SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
    *"  TABLES
    *"      I_T_SELECT TYPE  SBIWA_T_SELECT OPTIONAL
    *"      I_T_FIELDS TYPE  SBIWA_T_FIELDS OPTIONAL
    *"      E_T_DATA STRUCTURE  ZTRN_REC_TIME OPTIONAL
    *"      E_T_SOURCE_STRUCTURE_NAME OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    The input parameter I_DATAPAKID is not supported yet !
    Example: InfoSource containing TADIR objects
    Auxiliary Selection criteria structure
      DATA: l_s_select TYPE sbiwa_s_select.
    Maximum number of lines for DB table
      STATICS: l_maxsize TYPE sbiwa_s_interface-maxsize,
              S_S_IF TYPE SRSC_S_IF_SIMPLE,
              S_COUNTER_DATAPAKID LIKE SY-TABIX.
    Parameter I_PRIVATE_MODE:
    Some applications might want to use this function module for other
    purposes as well (e.g. data supply for OLTP reporting tools). If the
    processing logic has to be different in this case, use the optional
    parameter I_PRIVATE_MODE (not supplied by BIW !) to distinguish
    between BIW calls (I_PRIVATE_MODE = SPACE) and other calls
    (I_PRIVATE_MODE = X).
    If the message handling has to be different as well, define Your own
    messaging macro which interprets parameter I_PRIVATE_MODE. When
    called by BIW, it should use the LOG_WRITE macro, otherwise do what
    You want.
    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
    The input parameter I_DATAPAKID is not supported yet !
    Invalid second initialization call -> error exit
        IF NOT g_flag_interface_initialized IS INITIAL.
          IF 1 = 2. MESSAGE e008(r3). ENDIF.
          log_write 'E'                    "message type
                    'R3'                   "message class
                    '008'                  "message number
                    ' '                    "message variable 1
                    ' '.                   "message variable 2
          RAISE error_passed_to_mess_handler.
        ENDIF.
    Check InfoSource validity
        CASE i_isource.
          WHEN 'ZTRNREC_FM_DELTA'.
          WHEN OTHERS.
            IF 1 = 2. MESSAGE e009(r3). ENDIF.
            log_write 'E'                  "message type
                      'R3'                 "message class
                      '009'                "message number
                      i_isource            "message variable 1
                      ' '.                 "message variable 2
            RAISE error_passed_to_mess_handler.
        ENDCASE.
    Check for supported update mode
        CASE i_updmode.
          WHEN 'F'.
          WHEN 'D'.
          WHEN 'R'.
          WHEN OTHERS.
            IF 1 = 2. MESSAGE e011(r3). ENDIF.
            log_write 'E'                  "message type
                      'R3'                 "message class
                      '011'                "message number
                      i_updmode            "message variable 1
                      ' '.                 "message variable 2
            RAISE error_passed_to_mess_handler.
        ENDCASE.
    Check for obligatory selection criteria
        APPEND LINES OF i_t_select TO g_t_select.
    Fill parameter buffer for data extraction calls
        g_s_interface-requnr    = i_requnr.
        g_s_interface-isource   = i_isource.
        g_s_interface-maxsize   = i_maxsize.
        g_s_interface-initflag  = i_initflag.
        g_s_interface-updmode   = i_updmode.
        g_s_interface-datapakid = i_datapakid.
        g_flag_interface_initialized = sbiwa_c_flag_on.
    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 g_t_segfields.
      ELSE.                 "Initialization mode or data extraction ?
    Data transfer: First Call      OPEN CURSOR + FETCH
                   Following Calls FETCH only
      LOOP AT G_T_SELECT INTO L_S_SELECT
            WHERE FIELDNM = 'ZTIMESTAMP'.
      ENDLOOP.
          IF G_COUNTER_DATAPAKID = 0.
            IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
            OPEN CURSOR WITH HOLD G_CURSOR FOR
                SELECT (g_t_fields)
                FROM ZTRN_REC_TIME.
            ELSE.
              OPEN CURSOR WITH HOLD G_CURSOR FOR
                SELECT (g_t_fields)
                FROM ZTRN_REC_TIME
                WHERE ZTIMESTAMP >= L_S_SELECT-LOW
                  AND ZTIMESTAMP  <= L_S_SELECT-HIGH.
            ENDIF.
          ENDIF.
      FETCH NEXT CURSOR G_CURSOR
                   APPENDING CORRESPONDING FIELDS
                   OF TABLE E_T_DATA
                   PACKAGE SIZE S_S_IF-MAXSIZE.
        IF SY-SUBRC <> 0.
          CLOSE CURSOR G_CURSOR.
          RAISE NO_MORE_DATA.
        ENDIF.
        S_COUNTER_DATAPAKID = S_COUNTER_DATAPAKID + 1.
      ENDIF.
    ENDFUNCTION.
    I found some similar issue in this forum by link
    Generic Extractor Delta Function Module code, but still I could not get clear answer.
    Can you please help me:
    1)     why there is no value for i_source , how to fix it?
    2)     For the delta logic for ztimestemp, is it correct?
    3)     Need I modify the entries in ROOSOURCE ?
    Thanks a lot !!!

    Hello Andre,
            Thanks a lot for your help. I did some change , but still does not work. Could you please help check.
    Now the source code are the following, It's based on the RSAX_BIW_GET_DATA_SIMPLE, as you confirm that this also supply the update mode (full, initial delta, delta).
    FUNCTION RSAX_BIW_GET_DATA_TRAININGREC1.
    ""Local Interface:
    *"  IMPORTING
    *"     VALUE(I_REQUNR) TYPE  SRSC_S_IF_SIMPLE-REQUNR
    *"     VALUE(I_DSOURCE) TYPE  SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
    *"     VALUE(I_MAXSIZE) TYPE  SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
    *"     VALUE(I_INITFLAG) TYPE  SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
    *"     VALUE(I_READ_ONLY) TYPE  SRSC_S_IF_SIMPLE-READONLY OPTIONAL
    *"     VALUE(I_REMOTE_CALL) TYPE  SBIWA_FLAG DEFAULT SBIWA_C_FLAG_OFF
    *"  TABLES
    *"      I_T_SELECT TYPE  SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
    *"      I_T_FIELDS TYPE  SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
    *"      E_T_DATA STRUCTURE  ZTRN_REC_TIME OPTIONAL
    *"  EXCEPTIONS
    *"      NO_MORE_DATA
    *"      ERROR_PASSED_TO_MESS_HANDLER
    Auxiliary Selection criteria structure
      DATA: L_S_SELECT TYPE SRSC_S_SELECT.
    Maximum number of lines for DB table
      STATICS: S_S_IF TYPE SRSC_S_IF_SIMPLE,
    counter
              S_COUNTER_DATAPAKID LIKE SY-TABIX,
    cursor
              S_CURSOR TYPE CURSOR.
    Select ranges
    RANGES:
            L_R_ZTIMESTAMP FOR ZTRN_REC_TIME-ZTIMESTAMP.
    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 'ZTRNREC_FM'.
          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
                      ' '.                 "message variable 2
            RAISE ERROR_PASSED_TO_MESS_HANDLER.
        ENDCASE.
        APPEND LINES OF I_T_SELECT TO S_S_IF-T_SELECT.
    Fill parameter buffer for data extraction calls
        S_S_IF-REQUNR    = I_REQUNR.
        S_S_IF-DSOURCE = I_DSOURCE.
        S_S_IF-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_S_IF-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.
          LOOP AT S_S_IF-T_SELECT INTO L_S_SELECT WHERE FIELDNM = 'ZTIMESTAMP'.
          MOVE-CORRESPONDING L_S_SELECT TO L_R_ZTIMESTAMP.
          APPEND L_R_ZTIMESTAMP.
          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.
         IF L_S_SELECT-LOW = '' AND L_S_SELECT-HIGH = ''.
            OPEN CURSOR WITH HOLD S_CURSOR FOR
            SELECT (S_S_IF-T_FIELDS)
            FROM ZTRN_REC_TIME.
            ELSE.
            OPEN CURSOR WITH HOLD G_CURSOR FOR
            SELECT (S_S_IF-T_FIELDS)
            FROM ZTRN_REC_TIME
            WHERE ZTIMESTAMP >= L_S_SELECT-LOW
            AND ZTIMESTAMP <= L_S_SELECT-HIGH.
         ENDIF.
        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 S_S_IF-MAXSIZE.
        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.
    I think it already includes the important statements you suggested.
    I test this FM in RSA3, for the Full load mode, it works fine. Also if I checked the debug mode in execution , it will stop in the code and let me debug.
    But when I choose other mode, like 'initializion of the delta transfer'  or simulation of initial delta, I always get error 'error occurs  during the extraction' .. even I choose debug mode, but it could not enter the code for debug..
    Till now I did not see any parameter or value for the upload mode..
    Another questions is that, in RSO2, I define Ztimestamp as my delta field.. But , can I add other field as selection condition in the datasource definition, and has its range table in this function module ?
    Should I change the entries in ROOSOURCE for this datasource ??
    Please let me know your feedback, do you have some concret example for generic delta extraction ?
    Thanks a lot !

Maybe you are looking for