Error In Delta Extraction on 0HR_PT_1

Hi,
The status for delta load for 0HR_PT_1 stays yellow, and the application log in R/3 shows warning messages as
Personnel number 00001503 could not be locked.
It would be great if anyone could help.
Thanks

Sai,
I don't 0HR_PT_1 but I think there is a lock in sm12 for the personnel number because there is an user that modify the personnel number.
alessandro

Similar Messages

  • Error in delta extraction with SAP DataSource 2LIS_11_VAHDR ...

    Hi all
    I used the old data load process(3.5) in 2004s system.
    There are errors in detla extraction with SAP data source
    2LIS_11_VAHDR
    2LIS_11_VAITM
    2LIS_12_VCHDR
    2LIS_12_VCITM
    The delta data(before/after image) aren't right.
    Has anyone experices with this problem?
    thanks in advance

    No Problems yet,explain the error message with error number in details here for some one to help you.
    Hope it Helps
    Chetan
    @CP..

  • Error in Delta extraction of Material using MDM_CLNT_EXTR

    Hi All ,
    I am facing  the following error while doing the delta extraction for material by using MDM_CLNT_EXTR.
    ABAP/4 processor: MESSAGE_TYPE_UNKNOWN 
    I used MATERIAL_EXTRACT stucture, and successfully run the intial load.
    Any help will be appriciated
    BR
    Syam

    Hi Syam,
    Just check whether the target system defined in XI and the extraction object that you are selecting are in sync.
    Such error is possible when there is a conflict in the same.
    You can also refer to the below link.
    Delta Extraction Using MDM_CLNT_EXTR (Urgent)
    Hope it helps.
    Thanks,
    Minaz
    Edited by: Minaz Kathawala on Sep 30, 2008 4:14 PM

  • Processing overdue error during delta extraction from datasource 0CO_OM_CCA

    Hi,
    I'm getting "Processing overdue error" in BW while extracting delta from datasource 0CO_OM_CCA_9. all other extraction jobs from R3 -> BW are successful. Even Delta init on this datasource is successful & problem is only with delta package.
    I appreciate if someone could provide information based on the following error details on this issue.
    here are the extraction steps we followed.
    Full load of fiscal years 2006 & 2007 Into transactional cube.
    load budget data into transactional cube.
    compression of the cube with "0 elimination"
    Delta Initialization with fiscal period selections 1/2008 to 12/9999
    all the above steps were successful.
    and when delta package is scheduled, we are getting following errors.
    BW system log
    BW Monitoring job is turning red with following message.
    Technical : Processing is overdue
    Processing Step : Call to BW
    Sending packages from OLTP to BW lead to errors
    Diagnosis
    No IDocs could be sent to the SAP BW using RFC.
    System response
    There are IDocs in the source system ALE outbox that did not arrive in
    the ALE inbox of the SAP BW.
    Further analysis:
    Check the TRFC log.
    You can get to this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
    Removing errors:
    If the TRFC is incorrect, check whether the source system is completely
    connected to the SAP BW. Check especially the authorizations of the
    background user in the source system.
    R3 Job Log
    Even after BW job turns to red, R3 job continues to run for 2 hours and
    eventually gets cancelled with an ABAP dump & here is the log.
    Job
    started
    Step 001 started (program SBIE0001, variant &0000000110473, user ID
    BWREMOTE) DATASOURCE = 0CO_OM_CCA_9
    Current Values for Selected Profile Parameters
    abap/heap_area_nondia.........2000000000 *
    abap/heap_area_total..........2000000000 *
    abap/heaplimit................20000000 *
    zcsa/installed_languages......EDJIM13 *
    zcsa/system_language..........E *
    ztta/max_memreq_MB...........2047 *
    ztta/roll_area................6500000 *
    ztta/roll_extension...........2000000000 *
    ABAP/4 processor: SYSTEM_CANCELED
    Job cancelled
    Thanks,
    Hari Immadi
    http://immadi.com
    SEM BW Analyst

    Hi Hari,
    We were recently having similar problems with the delta for CCA_9.  And activating index 4 on COEP resolved our issues.
    Yes, by default there is a 2 hour safety interval for the CCA_9 DataSource.  You could run this extractor hourly but at the time of extraction you will only be pulling postings through 2 hours prior to extraction time.  This can be changed for testing purposes but SAP strongly discourages changing this interval in a production environment.  SAP does provide an alternative described in OSS note 553561.  You may check out this note to see if it would work for your scenario.
    Regards,
    Todd

  • Delta extraction for dunning history is not active

    Hi all,
    I am loading data to the FI Cube (Financial A/c -> Contract a/c receivables ) Dunning header .
    This is a Standard infocube.  This cube contains two DSOu2019S  0FC_DS08 , 0FC_DS11.  When I starting the data loading from the DSO ( 0FC_DS08 ), I create the INIT package .  When creating itself it throwing the error  u201C Delta extraction for dunning history is not active u201D
       When I check on SDN SAP , ( Use Tcode sbiw. Select 'Settings for apllication-specific datasources (PI) ->Contract Aacounts Receivable -> Make Central Settings'. Then tick 'Delta Extraction for Dunning Items Active'.) I got this link.  But I could not proceed this link.  Can you explain detailed step by step how to proceed to solve this issue.
    Regards,
    Baskaran.

    Hello Baskaran,
    Did you ever solve this issue?
    We do not have the link in SBIW (ERP 6.0 EHP6).
    Thanks,
    Andreas

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

  • Error in FI - AP Delta extraction

    Hi BW Experts,
    In my R/3, I have a generic datasourece ZFI_AP_PAYMENT.
    It receives data from a View which is created based on couple of cluster tables.
    When I do full load to the correcponding ODS, it is successful.
    I have Initialized delta.
    When I do DELTA extraction, it fails.
    So, when I requested Full load repair, it works fine.
    I am trying to do DELTA extraction again and it Fails.
    Please let me know how can I resolve this problem.
    URGENT

    Hi :
    Could you check the loading log in detail, and see what detail message is raised for failure.
    Could you try to firstly delete all data, then initial loading, after that try delta loading again
    Regards,
    Louis

  • 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

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

  • 0PM_PRM_PLCS_1 error occured during extraction

    Dear gurus ,
    i have make entry im pm_c05 table and extract the data first time ,it works fine .when i again try to load data it give me error .i have checked in rsa3 and while extraction it is giving error " Error occured during extraction " . our bi is is on 7.0 and erp 0n ehp 6.4 .i have implemented the sap note 0001243299 but again gettinng the same error.please help me out

    Hi Faisal:
       I've found a long list of SAP Notes that might be applicable to your environment, even though it is not mandatory to implement all of them to solve the issue you're facing right now, please consider the convenience of installing them on your system to fix some potential problems in advance.
    Note 1344048 - "0PM_PRM_PLCS_1: Delta upload does not work as expected"
    Note 1285238 - "0PM_PRM_PLCS_1: Errors during extraction, poor performance"
    Note 1323965 - "0PM_PRM_PLCS_1: Calculation for services"
    Note 1338093 - "0PM_PRM_PLCS_1: Execution factor not taken into account"
    Note 1339189 - "0PM_PRM_PLCS_1: Error occurs for alternative indicator"
    Note 1340188 - "0PM_PRM_PLCS_1: Revision of the calculation module"
    Note 1312783 - "0PM_PRM_PLCS_1: Implementing additional fields"
    Note 1314158 - "0PM_PRM_PLCS_1: Incorrect result during extraction"
    Note 1356256 - "0PM_PRM_PLCS_1: Poor system performance with strategy plans"
    Note 1416214 - "Overlap of records due to key constraints in 0PM_DS07"
    Note 1446484 - "Planned costs, costing, ECP: Incorrect message KI 217"
    Note 1508442 - "ECP, extractor 0PM_PRM_PLCS_1: error ME024 or ME025"
    Regards,
    Francisco Milán.

  • What are the disadvantages of generic delta extraction

    Hi all,
    what are the disadvantages of generic delta extraction.
    how function module generic extraction works.
    Thanks,
    Madhu.

    hi madhu,
    Pls refer ths,To learn more about Generic Extraction pls read BW350 book.
    Gereric Extraction can be done in 3 ways.
    If you go to transaction RSO2 in R/3 side, provide tech name for data source and click create.
    you will get the 3 options.
    1)From a DB Table
    2)From a DB View
    3)From Functional module/ Infoset Query
    in first option you can directly give a standard or custom build talbe name. in second option you can select the necessary fields from more than one talbe(eiter standard or custom). In third option you will create a function module or Query to extract data. When creating function modules you can use standard function modules as a template e.g. RSAX_BIW_GET_DATA_SIMPLE.
    see weblog : /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    If you want to enable delta for generic extractor you choose the option delta and provide necessary settings.
    Generic extraction is when your extraction is not satisfied by either BC or LIS/LO. It can be using a view / query/table/FM
    Here the changed records can be isentified by :
    1. Based on the date of creation or last change ( Delta based on 0Calday)
    2. Based on the record number ( Numeric Pointer )
    3. Based on time of change ( Timestamp)
    real time examples would be
    1. Master Record creation like customer ID creation
    2. Timesheets in SAP PS
    3. Invoive details / Sales Order Details.
    Pls check this web logs for clear Idea.
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33
    Have a look at these threads too.
    Tables
    Transfer Structure
    The steps for creating extractor using Function Module.
    1. Create new Function group (if you have already not done so) in Se80
    2. Copy Function module "RSAX_BIW_GET_DATA_SIMPLE" with suitable name.
    3. Change the code that populate data.
    Following table may give you the guideline for parameters.
    Parameter Description
    I_REQUNR (import) BW provides this request identifier. It is a system-generated identifier in the form REQU_XXXXXX. BW uses this same identifier in all function module calls that relate to a single load.
    I_DSOURCE (import) The name of the generic extractor
    I_MAXSIZE (import) The maximum number of records that BW expects to be in each data packet
    I_INITFLAG (import) A Boolean flag that indicates if this is the initialization (first) call to the function module
    I_READ_ONLY (import) A test flag not needed in most extraction scenarios
    I_T_SELECT (table) This table holds any selections from the BW InfoPackage. The function module should examine these selections and only return data that matches the selections.
    I_T_FIELD (table) This table holds the fields that BW requests
    E_T_DATA (table) The function module fills this table with data records. These records then return to BW as data packets. This table has the same structure as the extract structure defined in the generic DataSource.
    NO_MORE_DATA (exception) The function module raises this exception when no more data is available
    ERROR_PASSED_TO_MESS_HANDLER (exception) The function module raises this exception if an error occurred during the extraction. It alerts BW to check for error logs.
    Change following code to put the selection fields
    Select ranges
    RANGES: L_R_CARRID FOR SFLIGHT-CARRID,
    L_R_CONNID FOR SFLIGHT-CONNID.
    Change following to populate data
    OPEN CURSOR WITH HOLD S_CURSOR FOR
    SELECT (S_S_IF-T_FIELDS) FROM SFLIGHT
    WHERE CARRID IN L_R_CARRID AND
    CONNID IN L_R_CONNID.
    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.
    Some more links:
    Re: functionmodule
    Re: FM for G. extractor
    with hopes
    Raja Singh

  • Delta extraction is not possible at the moment

    Hello,
    I am trying to run a delta load and am getting the message "Delta extraction is not possible at the moment".  This is actually a repeat because i have tried this load multiple times with no success.
    The Diagnosis in the error message is:
    The delta extraction is not possible at the moment because the status list of the request is locked in the Cube. This can be for a number of reasons:
    1. Another extraction is taking place in the target BI.
    2. The control parameters of the request in the InfoCube are locked by deletion or compressing processes.
    I dont see that any other extraction or a deletion or compression job.  I've tried going through each failed job in the monitor and red lighting them but that hasnt helped.  Any ideas what to check or how to fix the problem?
    Regards,
    TMS

    Hi,
    From what you are describing, there is already some process going on on the infoprovider you are trying to load the data to. Check if a data load is still active/activation is happening, if its a cube then are there aggregates and are they rolling up. You can check the process in SM66 or SM50 and the jobs in SM37.
    The process has locked the infoprovider and no delta or for that matter any process can be done until the earlier one finishes. You can take help from the BASIS team to find out what is locking your infoprovider.
    Cheers,
    Kedar

  • * Delta Extraction for 0ASSET_ATTR_TEXT

    Hi All,
    Can someone help me for the delta extraction for 0ASSET_ATTR_TEXT datasource.
    Steps performed as per SAP Help
    1. Activated the BADI
    2. Ran the initialization without datatransfer infopackage.
    3. Created new records in R/3 side
    4. I can see the newly created records in the Table : BWFIAA_AEDAT_AS
    5. Ran the delta infopackage ( no records are getting updated)
    When i check in RSA3 with the delta update, its giving an error.
    Please guide me if i am missing any steps
    Regards
    Ram

    Hi Ram,
    Check this note,
    Note 816560 - DeltaInit w/o data transfer does not createe time stamp
    https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=816560
    Hope this helps....

  • Delta extraction issue

    Dear all,
    We are doing an delta extraction from 2LIS_01_*.  Delta update is not successfull with the following error messages.
    :error while transfering the data
    :error occured in the source system
    could anyone  help to fix this issue?
    Thanks,
    Krishna

    error message in rsmo
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    when i click on Error message in the status tab the message is
    *Errors occurred while transferring data ( ).
    Errors in source system*

Maybe you are looking for