Error while filling setup tables for 2lis_13_vahdr

Dear friends,
I am getting below Error while filling setup tables for 2lis_13_vahdr.
More faulty documents found than the tolerated 0000000000
Message no. M2222
Can any one guide me how to address this issue.
Thanks and Regards
Nithya

Hello Nithya,
It seems the No of tolerated faulty documents that you have given is 0. So when you initialize try to these.
While executing OLI*BW including a value in the maintain  "No. tolerated faulty documents" - 5000 or 10000.
Then execute the program in background.
Once the job is completed check the background job log if any errors.
Thanks
Chandran

Similar Messages

  • Error while filling setup table for Sales

    Dear Team,
    We are getting following error while filling setup table for Sales (application component 11) and for Billing (application component 13),
    application component 11
    Error determining rate: foreign curr.  local curr. INR date 08.10.2007 (doc. 673624) (JOB - RMCVNEUA)
    Message No M2810
    application component 13
    Billing document 480050000: error determining stats. currency rate (no updating)
    More faulty documents found than the tolerated 0000000000 (JOB - RMCVNEUF)
    I have seen lot of threads based on this but all r showing diffrenent currency to INR but for the above mentioned documents currency is in INR only so why it is showing the error I am not able to determine.
    If anybody faced this problem kindly reply to this.
    Best Regards,
    SG

    Hi There,
    Might be your using a wrong document number.
    I mean if your using the 11 you should use only Sales document number and for 13 you should only use billing document number.
    If you use vice versa that error will throw.
    Regards,
    MQ

  • Strange error while filling setup tables for purchasing

    hi experts,
    while filling setup tables, job is getting cancelled. when I check in sm37 message is
    Enter rate GBP / SGD rate type M for 03.08.2009 in the system settings
    Job cancelled after system exception ERROR_MESSAGE
    It is for only the 8th month of 2009. If I run for other dates it is succesfull.
    I am not able to understand what it mean. 
    Pls guide me how to resolve this.
    regards,
    rajesh.

    hi
    according to sven check this link
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/dc43c445-0d01-0010-23a1-ca348ff5f975?QuickLink=index&overridelayout=true
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0d5bf96-b19b-2c10-e3b6-e2f12a3de99a?QuickLink=index&overridelayout=true
    EUR Conversion to USD
    may help you.

  • Error while filling setup table for 2LIS_03_BF

    Hello,
    I am getting an error while filling set-up table for 2LIS_03_BF.
    Following is the screenshot of the same.
    If I check in ST22, I get following,
    I could fill the setup table for other datasource 2LIS_03_BX without any problem.
    Please suggest.

    Hi,
    Can you try filling the setup table data for that range in background?
    Sometimes because of huge data that you are trying to fill it might through you a dump. So please execute it in background and see if it works?.
    But still can't really say what that dump tells from what you attached.
    Thanks,
    Sathya

  • Short dump error while filling setup tables for 2LIS_06_INV

    Hi All,
    I am trying to fill the setup table.While filling the stup table for 2lis_06_inv datasource, i got the Dump error after some time.
    Error
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text
        SQL error in the database when accessing a table.
    plz can anyone help me out...

    Dear friends,
    I tried it by giving the selection on fiscal year,but again same problem.If i give 1 0r 2 document numbers in selection then extractor works fine.
    error:in detail.
    Runtime Errors         DBIF_RSQL_SQL_ERROR
    Exception              CX_SY_OPEN_SQL_DB
    Short text
        SQL error in the database when accessing a table.
    Information on where terminated
        Termination occurred in the ABAP program "SAPLMRMBW" - in "BW_RETRIEVE_DB_CO".
        The main program was "RMCENEUR ".
        In the source code you have the termination point in line 827
        of the (Include) program "LMRMBWF01".
        The program "SAPLMRMBW" was started as a background job.
        Job Name....... "RMCENEUR"
        Job Number..... 10524100
        The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
        procedure "BW_RETRIEVE_DB_CO" "(FORM)", but it was neither handled locally nor
         declared
        in the RAISING clause of its signature.
        The procedure is in program "SAPLMRMBW "; its source code begins in line
        806 of the (Include program "LMRMBWF01 ".
      806 FORM bw_retrieve_db_co  USING    t_mcrbkey_bv    TYPE mcrbkey_t
      807                                  t_mcrbkey_nbv   TYPE mcrbkey_t
      808                                  t_ekbe_acc      TYPE t_ekbe
      809                         CHANGING t_mcrbco        TYPE mcrbco_t.
      810
      811   TYPES: BEGIN OF s_target.
      812   TYPES: table_left LIKE rbco.
      813   TYPES: table_right TYPE rbex.
      814   TYPES: END OF s_target.
      815   TYPES: t_target TYPE TABLE OF s_target.
      816
      817
      818   DATA: t_rbco_nbv  TYPE t_target,
      819         t_rbco_bv   TYPE t_target,
      820         s_rbco      TYPE s_target,
      821         s_ekbe      LIKE ekbe,
      822         s_mcrbco    TYPE mcrbco,
      823         l_index     LIKE sy-tabix.
      824
       825 * Data source: invoice item non-background
      826   IF NOT t_mcrbkey_nbv[] IS INITIAL.
    *>>>>>     SELECT * FROM  rbco AS r LEFT OUTER JOIN rbex AS i*
      828        ON   ( rmandt = imandt AND
      829               rbelnr = ibelnr AND
      830               rbuzei = ibuzei AND
      831               rcobl_nr = icobl_nr )
      832        INTO TABLE t_rbco_nbv
      833        FOR ALL ENTRIES IN t_mcrbkey_nbv
      834        WHERE r~gjahr = t_mcrbkey_nbv-gjahr AND
      835              r~belnr = t_mcrbkey_nbv-belnr.
      836   ENDIF.
      837 * Data source: invoice item background
      838   IF NOT t_mcrbkey_bv[] IS INITIAL.
      839     SELECT * FROM  rbco AS r LEFT OUTER JOIN rbex AS i
      840        ON   ( rmandt = imandt AND
      841               rbelnr = ibelnr AND
      842               rbuzei = ibuzei AND
      843               rcobl_nr = icobl_nr )
      844        INTO  TABLE t_rbco_bv
      845        FOR ALL ENTRIES IN t_mcrbkey_bv
      846        WHERE r~gjahr = t_mcrbkey_bv-gjahr AND
    Thnks in advance

  • Error while filling setup table for Quality Mangement D/Sources

    HI Experts,
    Iam trying to fill the QM setup tables.
    Steps iam following are
    1.T-code OLIQBW
    2.Selecting Event QV, QE and gave selection parameters and name for Run.
    3. Execute
    4.Run Time Error CALL_FUNCTION_PARM_UNKNOWN
       Exception  CX_SY_DYN_CALL_PARAM_NOT_FOUND
       Date and Time          27.08.2009 11:21:01                                                                               
    Function parameter "I_ADDITIONAL_DATA" is unknown.

    Hi Mansi,
    Runtime Errors         CALL_FUNCTION_PARM_UNKNOWN                                                 
    Exceptn                CX_SY_DYN_CALL_PARAM_NOT_FOUND                                             
    Date and Time          27.08.2009 11:56:20                                                                               
    ShrtText                                                                               
    Function parameter "I_ADDITIONAL_DATA" is unknown.                                                                               
    What happened?                                                                               
    Error in ABAP application program.                                                                               
    The current ABAP program "SAPLQMER" had to be terminated because one of the                  
         statements could not be executed.                                                                               
    This is probably due to an error in the ABAP program.                                                                               
    Function module "QEEA_COMBINE_TO_ONE_FEATURE" was called                                     
         with the parameter "I_ADDITIONAL_DATA".                                                      
         This parameter is not defined.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below                     
         . The exception, which is assigned to the class                                              
          'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither                                               
         caught nor passed along using a RAISING clause, in the procedure                             
          "QMER_EXTRACTION_RD_RESULTS" "(FUNCTION)"                                                   
    Since the caller of the procedure could not have expected this exception                     
          to occur, the running program was terminated.                                               
         The reason for the exception is:                                                             
         The reason for the exception is:                                                       
         Function module "QEEA_COMBINE_TO_ONE_FEATURE" was called                               
         with the parameter "I_ADDITIONAL_DATA".                                                
         This parameter is not defined.                                                                               
    Missing RAISING Clause in Interface                                                        
         Program                                 SAPLQMER                                       
         Include                                 LQMER$01                                       
         Row                                     5                                              
         Module type                             (FUNCTION)                                     
         Module Name                             QMER_EXTRACTION_RD_RESULTS                                                                               
    Trigger Location of Exception                                                              
         Program                                 SAPLQMER                                       
         Include                                 LQMERU01                                       
         Row                                     488                                            
         Module type                             (FUNCTION)                                     
         Module Name                             QMER_EXTRACTION_RD_RESULTS

  • Timeout error while filling setup tables

    HI all
    I am getting timeout error while filling setup tables(OLI1BW).I clicked on execute button on hte screen.Its not scheduled as a background job.
    Going through threads i have come to know that to solve this issue
    1.BASIS team have to increase backgroung processses or memory
    2.run it as a background job.
    When I went to Program->Executein the backgroundPrint background parameters window has popped up.
    What to do in there?I am afraid if I include parameters like printer name....what is it and how long is it going to print?
    Please let me know.
    Thanks,
    Harika.

    thanks for the reply.
    it was set to LOCL only.
    But i have 3 options in the dropdown  windowsprinter :Send to onenote2007
                                      Microsoft XPS document writer
                                      OUrprinteraddress
    WHich one to choose here?
    Edited by: harikag on Aug 10, 2011 8:47 AM

  • Error while filling setup table

    Hello all
    I am trying to fill a setup table for 2lis_11_vahdr DS. I deleted setup table firts using LBWG and then proceeded the setup process by using OLI7BW , while i did that i got an error message "Error determing rate:foreign curr.DEM local curr.EUR date 02.01.1997(doc 4969)"
    could anyone tell me what this error is referring to ?
    thanks

    Hi DK.............
    I also think this is a problem of Exchange rate only..............maintain the exchange rate in SPRO >> General Settings >> Enter Exchange Rates.(Tcode : OB08 )
    Exchange rate table is TCURR.
    Exchange rates are maintained in r/3 and transfer to bw.................rsa1>>source system>>r/3 source system>>right click Transfer...........
    Regards,
    Debjani...........

  • Error while filling setup tables

    Hi All,
    By mistake my Delta queue for SD Deliveries (2LIS_12_). NOw as a solution we are filling in the setup tables again.
    But the request for filling up the tables cancelled giving the error "Document number does not exist".
    I donot know, how to solve this? Plz help me ,....Its really really urgent.
    Thanx in advance.

    Hi Preet,
    Go through this links:
    Re: problem when initializing setup tables for lo update
    "No extraction structure active or no BW connected"
    LO: No extraction structure active or no BW connected
    Thanks,
    Ajay

  • Order is locked by user while filling setup table

    Hi Experts,
    Yesterday while i am filling setup table for 2LIS_DM_VAITM (DBM Sales) data source it got cancelled.
    It showed that " Order xxxxxx is locked by user".
    Because we have DSO concept in our CUBE, we didn't lock users.
    But then the basis checked the users and removed from the system.
    But still after removing the users, when we do the setup filling it still gets cancelled showing the same error.
    Please help on this. Now i am stuck in filling setup section.
    Thanks,
    Thilini

    Hi,
    Thanks. I followed your instructions and removed * , last two check boxes and selected sales org.
    Now i am filling setup and its still running. I used a background job.
    In sm37 it shows as "active"
    But when I check in NPRT, It shows no logs were found.
    I want to know that, is everything fine?
    Setup table is filling right?
    expects a reply please...
    Thanks,
    Thilini

  • LO-COCKPIT: error in Filling Setup tables

    Dear Guru's:
    While filling setup tables from tcode: sbiw, I am getting following error:
    EXTRACT STRUCTURE NOT ACTIVE OR BW NOT CONNECTED.
    Bw is connected with R/3- I also have checked the connection thr' SM59, its working.
    And even Extract structure is Active.
    Then why this error is coming?
    Pls let me kno.
    Points will be rewarded.
    Thank you.

    Are you on Developement? If it is, please go to RSA6, look for the data source, and see if the extract structure is actually active, there may be one or more includes, check each one of them, if everything is fine, I would just reactivate it and move it to quality and production. If that happens only in Production, but it is fine in development, then I would make sure the development and production sytem extract structure matchs. Sometimes, someone modifies the development but never moved it to production. Check the last transport created for that extract structure too.
    thanks.
    Wond

  • What do exactly mean by 'document is lost' while filling setup table

    Hi ,
    In various threads its mentioned that, while extraction of logistics data .. say sales billing document, the document is 'lost', if its posted/changed while filling setup table . Hence we need to have system downtime while filling setup table.  So my questions are as follows :
    1)What exactly do u mean by 'Document is Lost'?  (I mean the document entries,will always be there in application tables ).
    2)Suppose we have DSO in "Over Write" mode at first level (after datasource). Will we need system downtime for filling setup table?  (I read n some forum that overwrite mode DSO at first level eliminates the need for system downtime)
    Please let me know your opinion on above questions
    Regards
    Mohit
    Edited by: Mohit Gupte on Jan 23, 2010 9:12 AM

    Hi Mohit,
    1) If document created/changed during filling of setup tables, it will not be available in corresponding extract queue and therefore not be available for delta update. Right?
      Sorry ,the answer is 'No' , because if you make any changes at the time of filling the set-up table, then those changes will be captured either in the set-up table or in the extraction queue and hence you will not miss any documents.Condition is ,you have to use 'Queued delta' .If you use 'Direct delta' then you miss the documents becasue of 'no' extraction queue .
    All documents are permanently stored in your application tables(VBRK,VBRP etc) always , but at the time of filling the set-up tables these documents will be collected from the application tables and will be moved to set-up table and then the changes will be stored in the extraction queue. At the time of set-up table running,new/changed documents will be stored either in the set-up table or in the extraction queue .So if you follow the correct loading method,you will not miss any documents.
    2)However these documents (changed/created during setup run) will be stored in application tables (VBRP & VBRK, in case of sales billing). Hence we can always retrieve consolidated list of such documents , by querying 'CREATED ON'/'CHANGED ON' fields of base tables. Then we can upload these consolidated records, via Full Repair Requests , to BI data targets. So documents are not permanently lost.
    Yes. Antyime later you can retrieve the records even if you missed at the time of loading.
    Hope it clears your doubts.
    Thanks.

  • How to Fill Setup tables for MAP (IS- Retail)

    Hello,
    I am working on MAP scenario, I found the following data sources as a part of it. Can anybody please tell me how to fill the setup tables for these and what are the base tables for it??
    2LIS_40_REVAL
    2LIS_40_S202
    2LIS_40_S207
    2LIS_40_S208
    Your reply is highly appreciated.
    Regards,
    Naresh

    Hi Naresh,
    We cannot fill setup tables for each data source.
    ORISBW -- This is the t-code to fill the setup tables for all the data sources which are related to application component 40.
    If you want setup tables names of your data sources please check below.
    2LIS_40_REVAL      ---   MC40RP0REVSETUP.
    Comes to your second post.
    2LIS_40_S202
    2LIS_40_S207
    2LIS_40_S208   these are LIS data sources, whic are replaced with LO data sources in SAP BI 7.0
    If you are using LO data sources then no need to use LIS data sources.
    Regards,
    Venkatesh

  • Can we select desire fields while filling setup tables?

    Hi
    When we fill setup tables we have some fields over there on which we can put some conditions & we can fill setup tables for that particular conditions..
    Now take example of datasource 2LIS_04_P_COMP..
    To fill setup tables I went in tcode OLI4COMP... I want to fill setup tables for some particular date range...
    I have only 5 fields in OLI4COMP.. I dont have field Posting date BUDAT there...
    I want to refill setup tables by usiing selections range on BUDAT but its not available in OLI4COMP..
    How to achieve this?? Please Help..
    Regards
    Swati

    Hello Swati,
    You can not do the fill with the date range if there is no entry.
    The alternative approach is that you can collect the document which belongs to your date range and then give that selection at the Document selections.
    For this you need to check the documents from the base tables of your application.
    This will solve your issue. I hope you might have deleted the earlier Setup tables before doing this activity.
    Hope this helps.
    Thanks

  • How to fill setup table for Application 18 Customer services

    Hi,
    How can I fill setup table for application 18.
    Regards,
    ST

    Hi,
    To fill LIS, first set your LIS to update. use the central Tcode OMO1(for SD), OMO2(for MM) or OMO3(for other logistics) or you can set it in MC24 also(activate button).
    SBIW -> settings for application specific datasources -> Logistics -> managing transfer information structures ->.... -> statistical setup Sales. (Application component 17 >transaction OLIIBW,Application component 18> OLISBW )-->select the relevent one whether sales/billings/deliveries etc in the pop-up. enter your LIS, give a name to job and execute.
    Also pls chk this;
    Re: query on setup table filling
    Regards
    CSM Reddy

Maybe you are looking for