Problems appending to a Generic Extractor

I have a Generic Extractor which is built on a customer defined table.  I have tried to append a ZZ field to the Extract structure but the Append button is greyed out.
I therefore directly added the ZZ field into the structure and wrote the logic in the user exit to populate.
When I go to RSA6 the field is not visible.  Why is this and how can I resolve? Thanks

Hi-
Is it possible to delete DS? If so....do that first!
goto RSO2 Create it again
RSA6/Select DS/Enhance Extraction Structure/Add fields/Activate
CMOD/Program/Include....
Then come back to RSA6, try it
I hope this can be out the issue!
Thanks,
Chandra.

Similar Messages

  • 0WBS element (external format) as append field in generic extractor?

    Hi Guru's,
    we use an generic extractor for our CO-PA data, as a join of different tables. Now I get the issue with this internal format of PSP element. It is of NUMC 8 and my basic data PSP element is CHAR 24. As they are not matching I want to add the POSID as an append field. But how to do this?
    In table PRPS I found the Include PRPS_INC an thought about using this in my extract structure? Is this possible? How do I need to go on and to simply have my additional field - with content! - in my extract structure?
    First I used an append and put in my include. As there are no fields extracted to BI I think this is wrong!? How can I delete my append?
    Thanks

    Hi Siggi,
    I have not created an special Append on the VEKP. I created an generic extractor on the VEKP. All fields of VEKP are available and I can hide or choose selection-field for all of these fields. No problem.
    i created an append on the extract structure via RSA6 - enhancement. I know that after generating the generic extractor with RSO2 all settings done in former times in  RSA6 are lost. But, my problem is: <b>I can not see any of the fields I put into the append. They are not there.</b> Not in ROOSFIELD and following not in RSA6. And that's the problem.
    Thanks for your support.
    OJ

  • Problem in creating a Generic Extractor on a custom 'Z' table

    This is regarding an earlier question I posted in sdn today. I am trying to create a generic extractor on a custom 'Z' table and iam getting the following message.
    Invalid extract structure template YBW_Z3PVR of DataSource YCNA_3PVAR_RPT
    Message no. R8359
    Diagnosis
    You tried to generate an extract structure with the template structure Z3PVR. This operation failed, because the template structure quantity fields or currency fields, for example, field MENGE refer to a different table.
    Procedure
    Use the template structure to create a view or DDIC structure that does not contain the inadmissable fields.
    Please advise. how do i solve this?

    Hi there,
    Is your Z* table working? It must be add check field for quantity field and currency field.
    Hope this helps.

  • Generic extractor and an append structure

    Hi all,
    this system is driving me crazy. So, that's something worked in former times..
    I created an generic extractor on VEKP. I have not restricted to any selection criteria or hide any field. The system generated the extractor and everything is fine. THEN I created an append on the generic extractor and put different fields inside the append. I want (and this works) to fill this different field via user exit for extraction. All field in the append are having the prefix ZZ, all field are characteristic and there is no inconsistency in the append. I activated the append.
    AND NOW - none of the fields of the append is available in RSA6 to hide or none hide or do anything. They are not available. By checking with SE11 on the generated structure - all field including the append are there.
    We are on ECC 5.0 with PI 2004.1 for 5.0 SP 10.
    Can anyone help. As i told you, this worked in former times (with SAP 4.6C with PI 2004.1 or lower).
    Regards
    OJ

    Hi Siggi,
    I have not created an special Append on the VEKP. I created an generic extractor on the VEKP. All fields of VEKP are available and I can hide or choose selection-field for all of these fields. No problem.
    i created an append on the extract structure via RSA6 - enhancement. I know that after generating the generic extractor with RSO2 all settings done in former times in  RSA6 are lost. But, my problem is: <b>I can not see any of the fields I put into the append. They are not there.</b> Not in ROOSFIELD and following not in RSA6. And that's the problem.
    Thanks for your support.
    OJ

  • Generic extractor question/problem

    Hello,
    I want to create a generic extractor on custom table which should delta enabled . This custom table has ERDAT( creation date) and ERZET u2013 Entry time but the client is asking me to use both fields for delta functionality . I am not sure how to do this . Please help .
    Regards,

    As you said client want you to use both the date n time stamp field to extract delta you can follow the below steps.
    - Create the generic data source as per you requirement in order to pic the delta
    - Open you extract structre and append the field TZNTSTMP, this is the field which holds the time stamp.
    - to setup deltas click on generic delta --> select time stamp(UTC)
    Regards
    KP

  • Generic Extractor Appends Missing

    Hello,
    I am trying to append an already existing generic extractor.  I have appended the extract structure with the new fields and it is activated.  However i cannot see my new fields in RSO2 or RSA6 or the ROOSFIELD table!  How do i get the new fields to show up?
    Regards,
    TMS

    Hi...You must enter to RSA2 in order to modify the datasource structure and uncheck the "hidden" check box for this new fields....after that you will see the fields...
    Regards

  • Generic extractor Delta problem

    hello,
    i have created a Generic extractor based on the AUFM table and the delta field is MBLNR (Material document no) that is a numeric pointer used for delta. My problem is that when i pull the delta not all records are being pulled. Why is that so? Can anyone give suggestions.
    thanks
    Laura.

    Well, using Function module is one approach. I can provide you another approach.
    You can create a View based on the following tables
    AUFM and MKPF,
    use the join condition
    AUFM-MANDT= MKPF-MANDT.
    AUFM-MBLNR = MKPF-MBLNR
    AUFM-MJAHR = MKPF-MJAHR
    In AUFM select all the fields that you want and MKPF select the "Accounting Document entry date" field which you can take it as delta field and select calday as your delta option.
    Once view is created, you can generate the datasource.
    Please check this option.
    I think it should work...
    Thanks
    Vj

  • Generic Extractor on Table VBAP

    Hi Gurus,
    I want to develop a Generic Extractor on table VBAP, but unfortunately its not giving me the extract structure when I save in RSO2, the screen wherein we select our fields are not displayed. Is there anything i am missing in the steps. Pls help us out with this issue.
    I am able to create the generic extractor with other tables with usual proceedure.
    Thanks in Advance.
    Regards,
    MSS

    Hi
    This is the problem with the amount and currency reference fields in your extract structure.
    "This operation failed, because the template structure quantity fields or currency fields, for example, field CMPRE_FLT refer to a different table."
    As you have an amount field, the currency reference table might be different and hence, it is giving this error.
    I think u need to create view and then append the currency or quanity fields , and populate them through User exit.
    Hope this helps.
    Sonal...

  • Generic extractor help needed badly.

    Hi Geeks,
    As continuation to questions I posted in the morning.
    1> I have created a generic extractor say ZBW_PRICING.
    2> ZBW_PRICING is based on tables A508 & KONP.
    3> One of the currency fields I am interested in that is
       KBETR has reference field RV13A-KBETR.
    4> Rv13A is a structure not a DB table so I can not give
       reference to RV13A while building view.
    5> So I appended the extract structure with two fields.
       ZZKBETR (rate) & ZZKONWA (currency key) to populate  it  from KONP.
    6> I activated the appended structure as well as extract structure.
    7> In RSA6 when I try to unhide field & save it.
       I get following error.
       The OLTP source still has errors.
       Message no R8417.
    Please help fellows its important for me.
    thanx in advance.
    Monica

    Kunal and Subray,
    I had the same problem while trying to unhide the field.
    I solved the error by giving the proper reference table and field names to the required field in extract structure, which in my case has been a currency field.
    ( Since I have a generic extractor, I changed the Reference Table name to Transparent table name. I changed the field name to corresponding field name within the Transparent table).
    Thank you.
    (Also, I see that Transparent Table name = extract structure name = DataSource name. I think the names might be same for Generice Datasources by default)

  • Delta fo Generic extractor using function module

    Hi,
    I am using the following function module for generic extractor but its always showing me extraction error.Could anyone please suggest to resolve the issue.
    Thanks in advance fo rsuggestion.
    FUNCTION Z_BW_SALESDATA_EXTRACT_CHNG2.
    ""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 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
      TABLES: VBFA,VBRK,tadir.
    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.
    user defined variables.
      DATA : X_UPDMODE(1) Type c,        " Update Type
            X_LastUpdate Like Sy-Datum. " Last Update Date
             X_LastUpdate TYPE RODELTAID. " Last Update Date   "TCS_KAP
    Select ranges
      RANGES: L_R_VBELN   FOR VBAK-VBELN,
              L_R_AUDAT   FOR VBAK-AUDAT.
    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 'Z_BW_SDDATA_CREATEON'.
          WHEN 'Y'.
          WHEN 'Z'.
          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 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
       READ TABLE i_t_select INTO l_s_select WITH KEY fieldnm = 'VBELN'.
       IF sy-subrc <> 0.
         IF 1 = 2. MESSAGE e010(r3). ENDIF.
         log_write 'E'                    "message type
                   'R3'                   "message class
                   '010'                  "message number
                   'PGMID'                "message variable 1
                   ' '.                   "message variable 2
         RAISE error_passed_to_mess_handler.
       ENDIF.
       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.
    Store Update mode in static variable...
       X_UPDMODE = I_UPDMODE.
        Select Single DELTAID
               Into   X_LastUpdate
               From   ROOSGENDLM
               Where  OLTPSOURCE = 'Z_BW_SDDATA_CREATEON'.
        If X_LastUpdate Is Initial.
          X_LastUpdate = '19800101'. " The oldest..., this should not happen
        Endif.
    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
    X_UPDMODE = I_UPDMODE.
    First data package -> OPEN CURSOR
        IF g_counter_datapakid = 0.
    Fill range tables for fixed InfoSources. In the case of generated
    InfoSources, the usage of a dynamical SELECT statement might be
    more reasonable. BIW will only pass down simple selection criteria
    of the type SIGN = 'I' and OPTION = 'EQ' or OPTION = 'BT'.
          LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'VBELN'.
            MOVE-CORRESPONDING l_s_select TO L_R_VBELN.
            APPEND L_R_VBELN.
          ENDLOOP.
          LOOP AT g_t_select INTO l_s_select WHERE fieldnm = 'AUDAT'.
            MOVE-CORRESPONDING l_s_select TO L_R_AUDAT.
            APPEND L_R_AUDAT.
          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 InfoSource table lines and database entries, this is trivial.
    In other cases, it may be impossible and some estimated value has to
    be determined.
    *added by Yogesh
          DELETE FROM ZBWSALEDATA.
    *ended by Yogesh
          l_maxsize = g_s_interface-maxsize.
    Check for supported update mode
          CASE X_UPDMODE.
            WHEN 'F' Or 'I'. " Full or Init
    **get sales orders
              SELECT *
                           INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                           FROM VBAK AS K
                           INNER JOIN VBAP AS P
                                 ON  PVBELN = KVBELN
                           WHERE K~VBELN IN L_R_VBELN
                           AND   K~AUDAT IN L_R_AUDAT
                           AND   K~VBTYP = 'C'.
              IF I_SALESDATA[] IS NOT INITIAL.
                PERFORM F_GET_DATA.                   "get data
                PERFORM F_DEL_VATCOND.                "delete vat conditions
                PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
                PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
                PERFORM F_GET_SALESDATA.
    *write perform with name F_INSERT_DB_ZBWSALEDATA.
                PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
               LOOP AT I_SALESDATA WHERE NETPR = 0.
                 MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
                 APPEND I_SALESDATA_FIN.
               ENDLOOP.
               SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
               DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                               COMPARING VBELN POSNR
                                                         KSCHL.
               INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
              ENDIF.
            WHEN 'D'. " Delta
              SELECT *
                             INTO CORRESPONDING FIELDS OF TABLE I_SALESDATA
                             FROM VBAK AS K
                             INNER JOIN VBAP AS P
                                   ON  PVBELN = KVBELN
                            WHERE K~ERDAT >= X_LastUpdate
                             WHERE K~ERDAT >= X_LastUpdate+0(8)          "TCS_KAP
                             AND   K~VBTYP = 'C'.
              IF I_SALESDATA[] IS NOT INITIAL.
                PERFORM F_GET_DATA.                   "get data
                PERFORM F_DEL_VATCOND.                "delete vat conditions
                PERFORM F_GET_TAR_COSTUNIT.           "get tariff cost unit
                PERFORM F_GET_NETVAL TABLES IT_VBDPA1. "get net val of the item
                PERFORM F_GET_SALESDATA.
    *write perform with name F_INSERT_DB_ZBWSALEDATA.
                PERFORM F_INSERT_DB_ZBWSALEDATA.      "insert into table ZBWSALESDATA
               LOOP AT I_SALESDATA WHERE NETPR = 0.
                 MOVE-CORRESPONDING I_SALESDATA TO I_SALESDATA_FIN.
                 APPEND I_SALESDATA_FIN.
               ENDLOOP.
               SORT I_SALESDATA_FIN BY VBELN POSNR KSCHL.
               DELETE ADJACENT DUPLICATES FROM I_SALESDATA_FIN
                                               COMPARING VBELN POSNR
                                                         KSCHL.
               INSERT ZBWSALEDATA FROM TABLE I_SALESDATA_FIN.
              ENDIF.
            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.
    **end get sales orders
          OPEN CURSOR WITH HOLD g_cursor FOR
          SELECT (g_t_fields) FROM ZBWSALEDATA.
         WHERE pgmid  IN l_r_pgmid AND
                                        object IN l_r_object.
        ENDIF.                             "First data package ?
    Fetch records into interface table. There are two different options:
    - fixed interface table structure for fixed InfoSources have to be
      named E_T_'Name of assigned source structure in table ROIS'.
    - for generating applications like LIS and CO-PA, the generic table
      E_T_DATA has to be used.
    Only one of these interface types should be implemented in one API !
        FETCH NEXT CURSOR g_cursor
                   APPENDING CORRESPONDING FIELDS
                   OF TABLE E_T_DATA
                   PACKAGE SIZE l_maxsize.
        IF sy-subrc <> 0.
          CLOSE CURSOR g_cursor.
          RAISE no_more_data.
        ENDIF.
        g_counter_datapakid = g_counter_datapakid + 1.
      ENDIF.              "Initialization mode or data extraction ?
    Best regards,
    Yogesh

    Dear Yogesh,
    Try to debug the code by putting a break point at select statement...is the FM Syntactically correct ??
    Check the Select statements..if all fields are not required avoid using Select * , and use always for all entries rather than JOINS..
    Note : For Joins you have to specify the Fields in the Select...Dont use Select * ....
    Hope it helps..
    Thanks,
    Krish

  • Error while creating Generic Extractor via Function Module

    Hello Guys
    I have created a Generic Extractor through a Function Module. I took the Standard FM: RSAX_BIW_GET_DATA_SIMPLE, gave it a new name and activated it. I made a few changes in it, like giving my structure name for E_T_DATA and giving the list of tables, from where I need to get the data. Then I created the datasource in RSO2 by giving this function module and the extract structure.
    The DS was created properly, but when I check in RSA3 for records, its giving me an error: ---> <b>The extraction program does not support object YCNA_INVY_TRNS</b>
    What do i do now? Can someone please tell me, what changes I need to make in the standard FM to suit my requirements??
    Thanks.

    Hi,
            Just try to reactivate the structure once again. And when you open the function module, if the problem still persists just try to press Return key several times. The message you are getting is just a warning message.
    PS: I am not sure whether this is the correct way, but i personally resolved this by pressing the ENTER key 4 or 5 times. So just give a try.
    Regards
    Sunil

  • Creation of a generic extractor and data source for the FAGLFLEXA table

    Hi All,
    Need to create a generic extractor and data source for the FAGLFLEXA table to support AR reporting. This table contains the necessary profit center information to perform LOB reporting against the AR data.
    Please advice on how to do this.
    Regards, Vishal

    Hi Vishal,
    Its seems a simple a work out.
    1.Go to RSO2 & choose the relevant option ie. whether you want to create Transactional DS, Master Data DS or Text DS.
    2. Name it accordingly & then create.
    3. Give description to it & then give table name FAGLFLEXA.
    4. Save it & activate. If you need it to be delta enabled then click over Delta & you can choose accordingly.
    If you still face some problem then do mail me at [email protected]
    Assign points if helpful
    Regards,
    Himanshu

  • How to identify update mode in function module for generic extractor

    Hi All,
    I have created generic extractor using function module which supports delta load.
    Delta logic is handeled in coding...by using ROOSGENDLM table.
    Now problem is we need to identify the update mode, requested from infopackage in our function module in order to apply logic for Repair full.
    I would like to know table or parameter in source system, which contain the update mode (Init , Delta , Full).
    Thanks,
    Niraj

    Hi Niraj
    You can use the FM import parameter "i_updmode" (This is of type "SBIWA_S_INTERFACE-UPDMODE") to determine if infopackage triggerred in full or delta mode.
    I_REQUNR     TYPE     SBIWA_S_INTERFACE-REQUNR                                                                               
    I_ISOURCE     TYPE     SBIWA_S_INTERFACE-ISOURCE                               InfoSource Name
    I_MAXSIZE     TYPE     SBIWA_S_INTERFACE-MAXSIZE                               Data Packet size
    I_INITFLAG     TYPE     SBIWA_S_INTERFACE-INITFLAG                               Initial Flag
    I_UPDMODE     TYPE     SBIWA_S_INTERFACE-UPDMODE                               Update Mode
    I_DATAPAKID     TYPE     SBIWA_S_INTERFACE-DATAPAKID                               Datapacket Id
    I_PRIVATE_MODE                                                                               
    I_CALLMODE     TYPE     ROARCHD200-CALLMODE                               Single-Character Flag
    I_REMOTE_CALL     TYPE     SBIWA_FLAG                                                                               
    Cheers
    Vasu Sattenapalli

  • How to reduce long extraction time - Generic extractor based on view

    Hello. The previous thread about this error was closed without any answer.
    I'm in the same configuration.
    "Using a generic extractor (Delta enabled on confirmation date) based on view to load data from ECC6 to BI.
    Now my issue is that the delta extraction is running for a long time (around 1 hr) even if the data volume is very small
    While checking the job overview in source system i saw that the job is hanging at the below step for almost 1 hr."
    1 LUWs confirmed and 1 LUWs to be deleted with function module MF RSC2_QOUT_CONFIRM_DATA.
    I am not understanding why this is happening.
    Here is the log of the job:
    30.05.2011 03:58:11 Job started
    30.05.2011 03:58:11 Step 001 started (program SBIE0001, variant &0000000166864, user ID ALEREMOTE)
    30.05.2011 03:58:11 Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
    30.05.2011 03:58:11 DATASOURCE = 0CO_OM_WBS_6
    30.05.2011 03:58:11 *************************************************************************
    30.05.2011 03:58:11 *          Current Values for Selected Profile Parameters               *
    30.05.2011 03:58:11 *************************************************************************
    30.05.2011 03:58:11 * abap/heap_area_nondia......... 4000000000                              *
    30.05.2011 03:58:11 * abap/heap_area_total.......... 8000000000                              *
    30.05.2011 03:58:11 * abap/heaplimit................ 100000000                               *
    30.05.2011 03:58:11 * zcsa/installed_languages...... DEFS                                    *
    30.05.2011 03:58:11 * zcsa/system_language.......... E                                       *
    30.05.2011 03:58:11 * ztta/max_memreq_MB............ 2047                                    *
    30.05.2011 03:58:11 * ztta/roll_area................ 6500000                                 *
    30.05.2011 03:58:11 * ztta/roll_extension........... 2000000000                              *
    30.05.2011 03:58:11 *************************************************************************
    30.05.2011 03:58:11 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA
    30.05.2011 05:02:53 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 171 records
    30.05.2011 05:02:53 Result of customer enhancement: 171 records
    30.05.2011 05:02:53 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 171 records
    30.05.2011 05:02:53 Result of customer enhancement: 171 records
    30.05.2011 05:02:53 Asynchronous send of data package 1 in task 0002 (1 parallel tasks)
    30.05.2011 05:02:53 IDOC: Info IDoc 2, IDoc No. 4667050, Duration 00:00:00
    30.05.2011 05:02:53 IDoc: Start = 30.05.2011 03:58:11, End = 30.05.2011 03:58:11
    30.05.2011 05:02:53 tRFC: Data Package = 1, TID = AC11082D38B44DE308DD028A, Duration = 00:00:00, ARFCSTATE = RECORDED
    30.05.2011 05:02:53 tRFC: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
    30.05.2011 05:02:53 Altogether, 0 records were filtered out through selection conditions
    30.05.2011 05:02:53 Asynchronous transmission of info IDoc 3 in task 0003 (0 parallel tasks)
    30.05.2011 05:02:53 IDOC: Info IDoc 3, IDoc No. 4667051, Duration 00:00:00
    30.05.2011 05:02:53 IDoc: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
    30.05.2011 05:02:53 Synchronized transmission of info IDoc 4 (0 parallel tasks)
    30.05.2011 05:02:53 IDOC: Info IDoc 4, IDoc No. 4667052, Duration 00:00:00
    30.05.2011 05:02:53 IDoc: Start = 30.05.2011 05:02:53, End = 30.05.2011 05:02:53
    30.05.2011 05:02:53 Job finished
    Thanks for your help.
    Yann

    Parth Kulkarni,
    following the note and the other thread, I've check the index 4 of the table COEP.
    Here is what I got:
    Index ID           COEP             - 4
    Short text         MANDT/TIMESTMP/OBJNR, Index for Delta read method (CO-PA)
    Last changed       SAP             04.01.2010
    Status             Active          Saved
                       Does not exist in the database
    DB index nme
        Not defined as DB index in the ABAP Dictionary
    Is the fact that it doesn't exist in the database a problem ?
    Is the fact that it is active is good enough ?
    By the way thanks for your speedy reply !
    Yann
    Edited by: Yann GOFFIN on May 30, 2011 1:35 PM

  • Create generic extractor based on 2 tables

    hey BI gurus,
    I have to create a generic extractor based on these 3 tables:
    eban - i need all fields
    vttk - i need only 4 fields i.e
                                         route,
                                         tknum,
                                         datbg,
                                         daten
    ekbe - budat.
    now the problem is thr is no common field between vttk & eban AND vttk & ekbe. but thr is a common field between eban & ekbe.so i can create a view only on these 2 tables but i want 3 tables
    how do i proceed???

    Hi,
    Sometimes, if your application or requirement makes it necessary, you have to create your own function module to extract the data from whatever sap system to bw.
    Therefore you normally make a copy of the standard fm 'RSAX_BIW_GET_DATA_SIMPLE'. To make this new function work for you, you have to realize the following.
    1.) the fm gets called by the extraction api for at least 2 times. First time is for initialization and from the 2nd time on it is for data extraction.
    2.) right after the last data package (somehow you need to make sure that it is the last one) you have to raise the exception no_more_data.
    Refer this links for more Info
    SAP BI Generic Extraction Using a Function Module
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33
    SAP Network Blog: Generic Extraction via Function Module
    /people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
    Take the help of an ABAPer if your are new to this process
    Regards
    Karthik
    Assigning points is the way to say thanks

Maybe you are looking for