Setup table no summarization result

Hi,
While loading the set up table i am getting error "no summarization result is selected. what to do
Thanks
Prashant

Hi Ram,
I hope you are using the same tcode - Go to Txn OLIQBW
give the Name of run and execute in Background.
I hope you done the same thing, if not please let me know
Regards,
Kiran

Similar Messages

  • No summarization result is selected

    Hi all,
    When Iam trying to fill up setup tables for QM, its giving the error as "No summarization result is selected".
    I have initailly deleted the setup tables before running the set up.
    Pls give ur Valuable suggestions.Its urgent.
    Thanks in advance,
    Mohan

    HI,
    please check LBWE application 05 weathe your data sources in active or not. then directly goto OLIQBW t-code and select the check boxes for Notifications, inspection lot and inspection results and then execute.
    Regards,
    Chandra,
    Edited by: chandrasekhar reddy on Feb 16, 2011 11:56 AM

  • Setup table for Inventory

    Hi Friends !
    Was reading the inventory docs for the setup table. How to perform step 2?
    2. Setup of statistical data for material documents in the R/3 source system. Here, all
    historical material movements are to be set up that has lead to the opening stock in
    step 1 (this makes it later possible in BW to calculate historical stock values). Ideally
    you still keep the posting block during this run. If this is not possible you have to
    make sure that by restrictions for posting date or the material document number you
    only select those material documents that have created the opening stock (step 1).
    Please consider that material movements that have been posted into the future for a
    date (field BUDAT) after the initial stock date are not getting selected if the upper
    restriction bound is exactly this date. In this case you have to choose an appropriate
    upper bound like 31st December 2099 and to keep the posting block. Also if you
    post new documents to a date (field BUD AT) earlier than the initial stock date you
    have to keep the posting block as time restrictions wonu2019t help to determine the right
    documents (maybe restrictions by document number help).
    With Regards
    Rekha

    Hi Rekha,
    Posting block is nothing but downtime. While filling the setup tables you should ensure that no postings happen in the system. To summarize step 2 -
    You should run the BX load and the Init BF load for the same selections. If there is any difference, it would lead to wrong stock values in BW. BX is used to setup the opening balance. BF init should be run with same selections so that it brings all movements which resulted in a stock setup by BX. We compress BF init load without marker (NO MARKER ticked) so that the stock doesn't get doubled because the result of the movements setup by BF is already extracted by BX.

  • Error when filling setup table

    Hi!
    I'm trying to fill the set-up table in R3 for SD Billing Documents.
    SBIW (Display IMG (Settings for App Specific Datasources --> Logistics --> Managing Extract Structures --> Initialization --> Filling in the Setup Table --> App. specific setup of statistical data)..
    When running the program i get this error msg:
    "More faulty documents found than the tolerated 0000000000"
    The result is that the program stops. Some of the data is coming into the set up tables, but this seems to be inconsistent.
    Anybody know what I could do?
    BR
    Bjørn

    Thanks a lot..
    How can I find the log of dumped jobs?
    BR
    BJørn

  • Dump While filling setup table

    Hi Frineds,
    We have moved some fields from Cimmunication structute to Extract structure at LBWE.
    We deleted data at setup table and also at RSA7.
    While filling the setup tables it is giving the below Dump.
    Please provide me solution.
    Runtime Errors         COMPUTE_BCD_OVERFLOW
    Except.                CX_SY_ARITHMETIC_OVERFLOW
    Date and Time          02.12.2010 12:41:24
    Short text
         Overflow during the arithmetical operation (type P) in program "SAPLMCEX".
    What happened?
         Error in the ABAP Application Program
         The current ABAP program "SAPLMCEX" had to be terminated because it has
         come across a statement that unfortunately cannot be executed.
    Error analysis
         An exception occurred that is explained in detail below.
         The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not
          caught in
         procedure "MAPPING_VA_MC11VA0ITM" "(FORM)", nor was it propagated by a RAISING
          clause.
         Since the caller of the procedure could not have anticipated that the
         exception would occur, the current program is terminated.
         The reason for the exception is:
         An overflow was discovered in an ongoing arithmetical operation with
         operands of type P. Possible causes are:
         1. The result field of type P is too small for the result.
        2. The result or a intermediate result has more than 31 decimal places.
    Missing RAISING Clause in Interface
        Program                                 SAPLMCEX
        Include                                 LMCEXM03
        Row                                     53
        Module type                             (FORM)
        Module Name                             MAPPING_VA_MC11VA0ITM
    Trigger Location of Exception
        Program                                 SAPLMCEX
        Include                                 LMCEXM03
        Row                                     105
        Module type                             (FORM)
        Module Name                             MAPPING_VA_MC11VA0ITM
    Source Code Extract
    Line  SourceCde
       75   MOVE-CORRESPONDING MC11VA2ITM_STR TO  MC11VA0ITM_TAB.
       76   MOVE-CORRESPONDING MC11VA4ITM_STR TO  MC11VA0ITM_TAB.
       77   MOVE-CORRESPONDING MC11VA5ITM_STR TO  MC11VA0ITM_TAB.
       78   MOVE-CORRESPONDING MC11VA6ITM_STR TO  MC11VA0ITM_TAB.
       79
       80 * Felder Mit Sonderbehandlungen
       81   MOVE P_XMCVBAK-SPART  TO MC11VA0ITM_TAB-SPARA.
       82   MOVE P_XMCVBAK-WAERK  TO MC11VA0ITM_TAB-WAERK_VBAK.
       83   MOVE P_XMCVBAK-VGTYP  TO MC11VA0ITM_TAB-VGTYP_AK.
       84   PERFORM CONVERT_PROJ_NUM USING    P_XMCVBAP-PS_PSP_PNR
       85                            CHANGING MC11VA0ITM_TAB-PS_POSID.
       86
       87   MOVE 1  TO MC11VA0ITM_TAB-ANZAUPO.
       88
       89   PERFORM READ_T001 USING P_XMCVBAK-BUKRS.
       90   MC11VA0ITM_TAB-PERIV = T001-PERIV.
       91
       92   MOVE P_XMCVBKD-CAMPAIGN TO MC11VA0ITM_TAB-MCEX_APCAMPAIGN.
       93   PERFORM get_apoplanned_va
       94     USING p_xmcvbak p_xmcvbap
       95     CHANGING MC11VA0ITM_TAB-APOPLANNED.
       96
       97   IF P_XMCVBAK-ABDIS NE SPACE.
       98     MC11VA0ITM_TAB-MCBW_NETPR_AVKM = P_XMCVBAP-NETPR.
       99     IF P_XMCVBAP-KPEIN NE 0.
      100       MC11VA0ITM_TAB-MCBW_NETPR_AVKM =
      101                    MC11VA0ITM_TAB-MCBW_NETPR_AVKM / P_XMCVBAP-KPEIN.
      102     ENDIF.
      103   ELSE.
      104     IF P_XMCVBAP-KWMENG NE 0.
    >>>>>       MC11VA0ITM_TAB-MCBW_NETPR_AVKM =
      106                         P_XMCVBAP-NETWR / P_XMCVBAP-KWMENG.
      107     ENDIF.
      108   ENDIF.
      109
      110 * ROCANCEL ermitteln
      111   PERFORM ROCANCEL_SETZEN
      112           USING P_XMCVBAK-SUPKZ MC11VA0ITM_TAB-ROCANCEL.
      113
      114   APPEND MC11VA0ITM_TAB.
      115
      116 ENDFORM.                               " MAPPING_VA_MC11VA0ITM
      117 &----
      118 *&      Form  MAPPING_VA_MC11V_0ITM
      119 &----
      120 *       text
      121 ----
      122 *      -->P_XMCVBAK  text                                              *
      123 *      -->P_XMCVBUK  text                                              *
      124 *      -->P_XMCVBAP  text                                              *
    Thanks &Regards,
    Anand.

    Hello friend,
    I have got the same dump error. Do you have the solution. How was it done.
    Please respond soon. Thanks.

  • SETUP tables steps required

    <Moderator Message: Please search before posting. You can find a lot of information related to this issue searching the forums, the blogs and of course the online help.>
    Hi friends,
    I want do purchase extraction using LO cockpit extraction before doing this i want to know about R/3 steps & setting if any in R/3 system.
    I know about LO extraction steps apart from that if we have any steps in R/3 setting kindly forward to me.
    thanks
    Siri
    Edited by: Siegfried Szameitat on Jan 26, 2009 12:31 PM

    Hi Siri........
    U want to extract Logistic data........
    The following section describes the steps that are necessary to configure a data
    flow for logistics data extraction.
    1. Transfer the logistics DataSource for transaction data from Business Content
    With the transfer of the DataSource, the associated extraction structure is
    also delivered, but the extraction structure is based on LIS communication
    structures. Furthermore, based on the extraction structure for the DataSource,
    a restructuring table that is used for the initialization and full update to BI
    is generated.
    Naming convention:
    DataSource 2LIS_<Application>_<Event><Suffix>; where <Event> is
    optional
    Examples:
    2LIS_11_VAITM: 11 = SD Sales VA = sales order, delivery schedule ITM
    (u2192 ITEM) = document position
    2LIS_02_HDR: 02 = MM purchasing HDR (u2192 HEADER ) = Document
    header
    Extraction structure MC<Application><Event/group of
    events>0<Suffix>; where MC is derived from the associated communication
    structures and <Suffix> is optional
    Examples:
    MC11VA0ITM: Extraction structure for the DataSource 2LIS_11_VAITM
    MC02M_0HDR: Extraction structure for the DataSource 2LIS_02_HDR,
    where M_ indicates the group for the events MA (order), MD (delivery
    schedule), ME (contact) and MF (request).
    Restructuring table (= setup table) <Extraction structure>SETUP
    Example:
    Extraction structure: MC11VA0IT u21D2 Restructuring table:
    MC11VA0ITSETUP
    2. Maintain extraction structure (transaction LBWE)
    This means that fields can be added to the extraction structure that is
    delivered with the DataSource without modifying anything. On the one
    hand, fields from the LIS communication structures that are assigned to the
    extraction structure can be used, that means standard fields that SAP has
    not selected, and on the other hand, customer fields that were attached to
    the LIS communication structures with the append technique can be used.
    After the extraction structure is created, it is generated automatically and the
    associated restructuring table is adapted.
    3. Maintain/generate DataSource
    In the DataSource maintenance, you can assign the properties Selection,
    Hide, Inversion (= Cancellation) and Field Only Known in Customer Exit to
    the fields of the extraction structure. After enhancing the extraction structure,
    the DataSource always has to be generated again!
    4. Replicate and activate DataSource in SAP BI (=metadata upload)
    5. Maintain Data Target (Data Store Object, InfoCube)
    6. Maintain Transformations between DataSource and Data Target
    7. Create a Data Transfer Process
    the Data Transfer Process will be used later to update the data from the PSA
    table into the Data Target.
    8. Set extraction structure for updating to active (transaction LBWE)
    In this way, data can be written to the restructuring table or the delta queue
    from then on using the extraction structure (see following steps).
    9. Filling the restructuring table/restructure (OLI*BW)
    During this process, no documents should be created or changed in the
    system! In some applications, it is possible to fill the restructuring table
    beforehand in simulation mode. These results are listed in a log (transaction
    LBWF). Before filling the restructuring table, you must ensure that the
    content of the tables is deleted (transaction LBWG), preventing the table
    from being filled multiple times. Once the restructuring tables are filled,
    document editing can resume as long as Unserialized V3 Update or Queued
    Delta is selected in the next step. Be absolutely sure that no V3 collection
    run is started until the next successful posting of an InfoPackage for delta
    initialization (see step 11).
    10. Select update method
    • Unserialized V3 update
    • Queued delta
    • Direct delta
    11. Create an InfoPackage for the DataSource and schedule the Delta
    Initialization in the Scheduler
    This updates the BI-relevant data from the restructuring table to the
    PSA table. Since the restructuring table is no longer needed after delta
    initialization, the content can be deleted (transaction LBWG).
    Use the Data Transfer Process created in step 7 to update the data from
    the PSA table into the Data Targets. After successful delta initialization,
    document editing can resume, as long as the direct delta update method
    was selected in step 13. This means that BI-relevant delta data is written
    directly to the delta queue.
    Note:
    If the DataSource supports early-delta initialization, the delta data can
    be written to the delta queue during delta initialization. This feature is
    controlled with an indicator in the Scheduler.
    12. Start V3 collection run (transaction LBWE)
    This step is only necessary when the update method unserialized V3 Update
    or Queued Delta was selected in step 10. By starting a corresponding job for
    an application, the BI-relevant delta data is read from the update tables or
    extraction queue and written to the delta queue.
    13. Create an InfoPackage for the DataSource in BI and schedule the Delta
    Update in the Scheduler
    The BI-relevant delta data from the delta queue for the DataSource is updated
    to the PSA table. Use the Data Transfer Process created in step 7 to update
    the data from the PSA table into the Data Targets.
    Hope this helps.......
    Regards,
    Debjani......

  • Error in Setup Tables for QM Inspection Lots

    Hi,
    I have an issue when I attempt to fill the setup tables for QM that I receive the following error for the Inspection Lots (QV) only. When I fill the setup tables for Notifications and Inspection Results, then these are OK and use the same standard function module 'qmex_inspection_lot_import_ini'.
    "Internal error in program SAPLQMEX, function module / subroutine qmex_inspection_lot_import_ini, code 1".
    Has anyone any ideas of the cause or have you experienced this before?
    Thanks,
    Scott

    Hi,
    The most likely reason that leads to the above error message in your
    system is an inconsistency of the inspection lots.
    To get the inconsistent inspection lot,please check your system in the
    following way:
    - transaction OLIQBW for running Setup table
    - switch on debugging mode
    - set break point in the function  QMEX_INSPECTION_LOT_IMPORT_INI
    on the line:
    ELSE.
       MESSAGE e011(qmex) WITH sy-repid
                               'qmex_inspection_lot_import_ini'
                               '1'.
      > then excecute F8 to go to this break point.
    - double klick on ' l_qals-prueflos'
    on line 77 in the same function  QMEX_INSPECTION_LOT_IMPORT_INI:
    READ TABLE qave_tab INTO l_qave
                        WITH KEY prueflos = l_qals-prueflos  <      here !
                        BINARY SEARCH.
    Please check following note:
    305244 Missing operations for the inspection lot
    89541 Inspection lot exists w/o status object: EM BS001
    536769 Inspection lots without status object
    Thanks,
    Venkat

  • Does setup tables shud be deleted every time in delta

    hi gurus
    can u tell me how the setup tables run(work) when delta loading taken place....
    tell me the diffe between following tables and there names.. ex vbak, vbep etc..
    application tables i know vbak,vbap,vbep, vbup etc
    application tables = update tables.?
    statistical tables?

    Hi,
    Setup tables(one time used) holds historical data which is very important for initialization.
    For daily delta run the data will be picked from application tables(say for SD:sales order data , VBAK(header level info),VBAP(item level),VBEP(schedule line) tables )depending on the collection mode to delta Q:
    we have three types of collection mode:
    Direct Delta
    Direct transfer of extraction data to delta queue(use T- code to check RSA7 delta Q)
    Each posting to a document results to a LUW in the delta queue
    Queued Delta
    Extraction data is collected in a so-called extraction queue(LBWQ)
    Collective run transfers data from extraction queue to delta queue(RSA7)
    Unserialized V3 Update
    As for the Unserialized V3 Update, extraction data is stored intermediately in the update queue.
    Collective run transfers data from update queue(SM13) to delta queue without keeping the chronological sequence of the data.
    Once data reaches delta Que,from here the data will be sent to the target by scheduling an info package.
    Hope you are clear now!!!!!!!!!!!!!!
    Assign points if it helps.
    Regards,
    Swapna.G

  • STATISTICAL SETUP TABLE

    hi,
    please help me; after the activation of the 2LIS_03_BF extractor in the R/3 system ( transaction LBWE), i have tested it but (transaction RSA3) and the result is 0 record extracted.
    Probably i have forgotten some phases in the configuration process like the statistical setup table.
    Can explain me how do it
    thanks

    Luigi
    Check this link
    Re: setup tables
    also
    check this
    https://websmp105.sap-ag.de/bi
    You need service market place ID to check this
    Hope this helps
    Thanks
    Sat

  • Any precautions while filling setup tables

    Hi Experts,
    Are there <b>any precautions to be taken while filling in the setup tables</b>. I'm doing this in the production server, does it effect the performance of the production system in any way, does it result in any fatal consequences regarding the performance of the production server. Are there any time specifications for the termination time(i.e how much time for how many records).
    plz shed light on the above issues.
    thanks & regards.

    Hi Vamshi,
    While filling the setup tables you need to take transaction outage for the application area you are performing this action. this means locking the users from posting new documents.
      Please make sure that the V3 job has been deactivated . Delete the data in the delta queue for all the datasources of that particulat application area.
    for ex : for the application area 02 you need to delete the data in delta queue for the data sources 2LIS_02_HDR, 2LIS_02_ITM etc..
    Regards
    Murali

  • 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 a setup table

    Hi,
    While i filling a setup table, i got this error message,
    "Error determining Rate:foreign curr .local curr
    INR date 27.06.2007 (doc.8166) "
    any body tell me the meaning of this and how to rectify it.
    -Arun.M.D

    Hello Arun
    You are getting this error because Currency Exchange Rate is not being loaded to your system for INR. Ask FI team to maintain this.
    Reward points if it is helpfull.
    Thanks
    Tripple k

  • Enhancing the standard  Data source without deleting setup tables

    Hi all,
    I am in the the Support Project. My requirement is I want to Enhance u201C2LIS_13_VDITMu201D LO- data source with two fields without disturbing the delta.
    Please suggest me how I have to do this.
    As Per my Knowledge ,
    1. we have to delete setup tables
    2. Enhance the data source & re populate the setup tables.
    3. Delete the data in the cube & add the two new fields in the cube & repopulate the cube with new Initial .
    4. after that delta will be enabled through job control.
    But this process is not suitable for our requirement because delta was enabled long back it is going very smooth till date, I donu2019t want to disturb that process.
    So please suggest me is there any other procedure to do this.
    Thanks,
    Kiran Manyam

    Hi,
    If historical data (loaded earlier in to BW) are not required for the two enhance field, then it is not required to deleted the setup table and reload them to BI.
    In this case simply you can follow the following procedure.
    1. Enhance the fields, and update the transfor structure(to unhide these fields). In BI update the required data target with respective IO. and in exit populate the enhance fields. No need to disturb the delta
    2. Replicated the DS in BI and do the mappings in tranformation.
    Here the existing delta is working, and you will be populating the two fields in the exit only.
    Thanks,
    Jugal.

  • SOME DOUBTS IN SETUP TABLES

    HI,
    TO ALL BW GURUS,
    I WANT TO KNOW THE ARCHITECTURE OF SETUP TABLES.
    WHAT IS THE MAIN DIFF'S BETWEEN NORMAL TABLES AND POOLED AND CLUSTERED TABLES.
    2.
    WHAT IS PSEUDODELTA.
    WHERE IT IS USED AND WHAT IS THE PURPOSE OF THIS DELTA.
    THANKS
    ANAND.

    Hi,
    check the beow link for table types:
    http://help.sap.com/saphelp_47x200/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
    regards,
    raju

  • Data not seen in RSA3 after setup table was filled

    HI
    We have an issue where we do not see data for Sales Orders and Deliveries in RSA3  (and hence is missing in BW).
    For sales orders we are missing 6 months' data and for Deliveries we are missing data from june to october 2007.
    We checked the sales order and delivery documents in R/3 and they exist for the above date ranges. We deleted and filled up the setup tables. But still don't see the data in RSA3.
    There were no extractor changes done.
    Any tips?
    Thanks
    Pooja

    Go to SE11 and search for setup and look for the specific data source and see the content, if the content is actually zero, then there is nothing in the setup table.
    thanks.
    Wond

Maybe you are looking for