Performance Tuning of webi report BO4.0

Hi ,
I have report which has two data providers in 1st Data Provider i have 10 objects and in 2nd Data provider i have 3 objects the issue is performance report is taking 6 minutes to run.
Please help me out how we can increase the performance at Query Level.
Thanks
Siva

Hi
There are various levels to which you have to check to improve the performance of reports could be at connection levels, query, database etc.
some of them you can try
1. check array fetch size in relational connection parameters, deactivating array fetch size can increase the efficiency of retrieving your data, but slows server performance.
2. Setting options for the default list of values in business layer and data foundation layer
Automatic refresh - If this is selected, the list of values is automatically refreshed each time the
list is called. This can have an effect on performance each time the list of values is refreshed. You should disable this option if the list of values returns a large number of values.
3. set query stripping (Optimize query with Query Stripping in Web Intelligence - Business Intelligence (BusinessObjects) - SCN Wiki)
4. also check Performance Tuning Methods in BO
Regards,
Raghava

Similar Messages

Performance tuning of this report

Hello friends iam attaching my report give the performance tuning for this report to avoid nested endloops. how to do without using nested endloops.
give me the reply urgent.
REPORT ZDEMO9          NO STANDARD PAGE HEADING
                        LINE-SIZE 250
                        LINE-COUNT 22(3).                             .
            TABLES DECLARATION                    *
TABLES : MARA,              "general material data
         MAKT,              "material description
         MARC,              "plant data for material
         VBAP,              "sales document for item data
         EKKO,              "purchasing document header
         EKPO,              "purchasing document item
         KNA1.              "customer master details
            INTERNAL TABLE DECLARATION             *
DATA : BEGIN OF T_MARA OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MTART LIKE MARA-MTART,
       MEINS LIKE MARA-MEINS,
       END OF T_MARA.
DATA : BEGIN OF T_MAKT OCCURS 0,
       MATNR LIKE MAKT-MATNR,
       MAKTX LIKE MAKT-MAKTX,
       SPRAS LIKE MAKT-SPRAS,
       END OF T_MAKT.
DATA : BEGIN OF T_MARC OCCURS 0,
       MATNR LIKE MARC-MATNR,
       WERKS LIKE MARC-WERKS,
       END OF T_MARC.
DATA : BEGIN OF T_KNA1 OCCURS 0,
       KUNNR LIKE KNA1-KUNNR,
       NAME1 LIKE KNA1-NAME1,
       LAND1 LIKE KNA1-LAND1,
       END OF T_KNA1.
DATA : BEGIN OF T_VBAP OCCURS 0,
       MATNR LIKE VBAP-MATNR,
       POSNR LIKE VBAP-POSNR,
       MATKL LIKE VBAP-MATKL,
       VBELN LIKE VBAP-VBELN,
       END OF T_VBAP.
DATA : BEGIN OF T_EKPO OCCURS 0,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       BUKRS LIKE EKPO-BUKRS,
       WERKS LIKE EKPO-WERKS,
       LGORT LIKE EKPO-LGORT,
       MATNR LIKE EKPO-MATNR,
       MANDT LIKE EKPO-MANDT,
       END OF T_EKPO.
                 FINAL INTERNAL TABLE                *
DATA : BEGIN OF T_FINAL OCCURS 0,
       MATNR LIKE MARA-MATNR,
       MTART LIKE MARA-MTART,
       MEINS LIKE MARA-MEINS,
       WERKS LIKE MARC-WERKS,
       MAKTX LIKE MAKT-MAKTX,
       SPRAS LIKE MAKT-SPRAS,
       VBELN LIKE VBAP-VBELN,
       POSNR LIKE VBAP-POSNR,
       MATKL LIKE VBAP-MATKL,
       EBELN LIKE EKPO-EBELN,
       EBELP LIKE EKPO-EBELP,
       BUKRS LIKE EKPO-BUKRS,
       KUNNR LIKE KNA1-KUNNR,
       LAND1 LIKE KNA1-LAND1,
       NAME1 LIKE KNA1-NAME1,
       LGORT LIKE EKPO-LGORT,
       END OF T_FINAL.
*DATA: BEGIN OF V_matnr OCCURS 0,
       matnr LIKE mara-matnr,
     END OF t_matnr.
data:
      a(32) type c.
a = 'IBT000000000000000001000000000000000050'.
                   SELECTION SCREEN                         *
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS : S_BUKRS FOR EKPO-BUKRS,
                 S_KUNNR FOR KNA1-KUNNR,
                 S_WERKS FOR MARC-WERKS,
                 S_MATNR FOR MARA-MATNR obligatory.
SELECTION-SCREEN END OF BLOCK B1.
                 START OF SELECTION                           *
START-OF-SELECTION.
SELECT MATNR mtart meins
          FROM MARA
          INTO CORRESPONDING FIELDS OF TABLE T_MARA
          WHERE MATNR IN S_MATNR.
SELECT MATNR WERKS
          FROM MARC
          INTO CORRESPONDING FIELDS OF TABLE T_MARC
          FOR ALL ENTRIES IN T_MARA
          WHERE MATNR = T_MARA-MATNR
          and werks in s_werks.
select matnr maktx spras
        from makt
        into corresponding fields of table t_makt
        for all entries in t_mara
        where matnr = t_mara-matnr
        and spras = sy-langu.
select matnr posnr matkl vbeln
         from vbap
         into corresponding fields of table t_vbap
         for all entries in t_mara
         where matnr = t_mara-matnr.
select matnr werks bukrs ebeln ebelp lgort
         from ekpo
         into corresponding fields of table t_ekpo
         for all entries in t_mara
         where matnr = t_mara-matnr
         and werks in s_werks.
LOOP AT T_MARA.
    MOVE T_MARA-matnr TO T_FINAL-matnr.
    move t_mara-mtart to t_final-mtart.
    move t_mara-meins to t_final-meins.
    loop at t_marc where matnr eq t_mara-matnr.
      move t_marc-werks to t_final-werks.
      loop at t_makt.
        move t_makt-maktx to t_final-maktx.
        move t_makt-spras to t_final-spras.
        loop at t_vbap.
          move t_vbap-posnr to t_final-posnr.
          move t_vbap-matkl to t_final-matkl.
          move t_vbap-vbeln to t_final-vbeln.
        loop at t_ekpo.
        move t_ekpo-bukrs to t_final-bukrs.
        move t_ekpo-ebeln to t_final-ebeln.
        move t_ekpo-ebelp to t_final-ebelp.
        move t_ekpo-lgort to t_final-lgort.
          append t_final.
        endloop.
      endloop.
    endloop.
endloop.
endloop.
SELECT werks KUNNR LAND1 NAME1
INTO CORRESPONDING FIELDS OF TABLE T_KNA1
FROM KNA1.
WHERE WERKS in s_werks.
loop at t_kna1.
    move t_kna1-kunnr to t_final-kunnr.
    move t_kna1-name1 to t_final-name1.
    move t_kna1-land1 to t_final-land1.
    append t_final.
endloop.
"endloop.
loop at t_final.
    write :   4 t_final-matnr,
             20 t_final-mtart,
             28 t_final-meins,
             46 t_final-werks,
             58 t_final-maktx,
             71 t_final-spras,
             78 t_final-posnr,
            100 t_final-matkl,
            115 t_final-vbeln,
            130 t_final-kunnr,
            142 t_final-name1,
            156 t_final-land1,
            168 t_final-bukrs,
            190 t_final-ebeln,
            205 t_final-ebelp,
            208 t_final-lgort.
endloop.
              TOP-OF-PAGE                       *
top-of-page.
uline.
write : /60 'G E N E R A L   D E T A I L S' COLOR 2 INVERSE OFF.
ULINE.
write :/ SY-VLINE,    'MATERIAL'       COLOR 4, "12 SY-VLINE,
        13 SY-VLINE,    'IND SECTOR',
        28 SY-VLINE,    'UNITS',
        43 SY-VLINE,    'PLANT',
        55 SY-VLINE,    'MAT DESC',
        68 SY-VLINE,    'LANGU',
        70 SY-VLINE,    'SALES DOC ITEM',
        95 SY-VLINE,    'MAT GROUP',
       110 SY-VLINE,    'SALES DOC',
       125 SY-VLINE,    'CUST ID',
       140 SY-VLINE,    'NAME',
       155 SY-VLINE,    'COUNTRY',
       165 sy-vline,    'company code',
       205 sy-vline,    'storge loc'.

*& Report YTESTCHA                                                    *
REPORT ytestcha NO STANDARD PAGE HEADING
LINE-SIZE 250
LINE-COUNT 22(3). .
TABLES DECLARATION *
TABLES : mara, "general material data
makt, "material description
marc, "plant data for material
vbap, "sales document for item data
ekko, "purchasing document header
ekpo, "purchasing document item
kna1. "customer master details
INTERNAL TABLE DECLARATION *
*DECLARE TYPES FIRST AND THE INTERNAL TABLES
*DONT USE MATNR LIKE MARA-MATNR ,INSTEAD USE MARA TYPE MATNR WHERE MATNR
*IS THE DATA ELEMENT FOR FIELD MATNR.
TYPES: BEGIN OF ty_mara,
         matnr TYPE matnr,
         mtart TYPE mtart,
         meins TYPE meins,
         kunnr TYPE wettb,
       END OF ty_mara.
TYPES: BEGIN OF ty_makt,
        matnr TYPE matnr,
        maktx TYPE maktx,
        spras TYPE spras,
       END OF ty_makt.
TYPES: BEGIN OF ty_marc,
        matnr TYPE matnr,
        werks TYPE werks_d,
        END OF ty_marc.
TYPES : BEGIN OF ty_kna1,
          kunnr TYPE kunnr,
          name1 TYPE name1_gp,
          land1 TYPE land1_gp,
          END OF ty_kna1.
TYPES: BEGIN OF ty_vbap,
         matnr TYPE matnr,
         posnr TYPE posnr_va,
         matkl TYPE matkl,
         vbeln TYPE vbeln_va,
         END OF ty_vbap.
TYPES: BEGIN OF ty_ekpo,
         ebeln TYPE ebeln,
         ebelp TYPE ebelp,
         bukrs TYPE bukrs,
         werks TYPE werks_d,
         lgort TYPE lgort_d,
         matnr TYPE matnr,
         mandt TYPE mandt,
        END OF ty_ekpo.
DATA:t_mara TYPE TABLE OF ty_mara WITH HEADER LINE,
     t_makt TYPE TABLE OF ty_makt WITH HEADER LINE,
     t_marc TYPE TABLE OF ty_marc WITH HEADER LINE,
     t_kna1 TYPE TABLE OF ty_kna1 WITH HEADER LINE,
     t_vbap TYPE TABLE OF ty_vbap WITH HEADER LINE,
     t_ekpo TYPE TABLE OF ty_ekpo WITH HEADER LINE.
FINAL INTERNAL TABLE *
TYPES: BEGIN OF ty_final,
     matnr TYPE matnr,
     mtart TYPE mtart,
     meins TYPE meins,
     werks TYPE werks_d,
     maktx TYPE maktx,
     spras TYPE spras,
     vbeln TYPE vbeln_va,
     posnr TYPE posnr_va,
     matkl TYPE matkl,
     ebeln TYPE ebeln,
     ebelp TYPE ebelp,
     bukrs TYPE bukrs,
     kunnr TYPE kunnr,
     land1 TYPE land1_gp,
     name1 TYPE name1_gp,
     lgort TYPE lgort_d,
     END OF ty_final.
DATA : t_final TYPE TABLE OF ty_final WITH HEADER LINE.
*DATA: BEGIN OF V_matnr OCCURS 0,
matnr LIKE mara-matnr,
END OF t_matnr.
DATA:
a(32) TYPE c.
a = 'IBT000000000000000001000000000000000050'.
SELECTION SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : s_bukrs FOR ekpo-bukrs,
                 s_kunnr FOR kna1-kunnr,
                 s_werks FOR marc-werks,
                 s_matnr FOR mara-matnr OBLIGATORY.
SELECTION-SCREEN END OF BLOCK b1.
START OF SELECTION *
START-OF-SELECTION.
*USE SUBROUTINES
*get data
PERFORM get_data.
*populate final table
PERFORM populate_final_table.
END-OF-SELECTION.
*display output
PERFORM display_output.
TOP-OF-PAGE *
TOP-OF-PAGE.
ULINE.
WRITE : /60 'G E N E R A L D E T A I L S' COLOR 2 INVERSE OFF.
ULINE.
WRITE :/ sy-vline, 'MATERIAL' COLOR 4, "12 SY-VLINE,
13 sy-vline, 'IND SECTOR',
28 sy-vline, 'UNITS',
43 sy-vline, 'PLANT',
55 sy-vline, 'MAT DESC',
68 sy-vline, 'LANGU',
70 sy-vline, 'SALES DOC ITEM',
95 sy-vline, 'MAT GROUP',
110 sy-vline, 'SALES DOC',
125 sy-vline, 'CUST ID',
140 sy-vline, 'NAME',
155 sy-vline, 'COUNTRY',
165 sy-vline, 'company code',
205 sy-vline, 'storge loc'.
*&      Form GET_DATA
      text
--> p1        text
<-- p2        text
*TRY TO CLEAR AND REFRESH TABLES BEFORE SELECT
FORM get_data .
CLEAR t_mara.
REFRESH t_mara.
SELECT matnr
         mtart
         meins
         kunnr
         FROM mara
         INTO TABLE t_mara
         WHERE matnr IN s_matnr.
IF NOT t_mara[] IS INITIAL.
    CLEAR t_marc.
    REFRESH t_marc.
    SELECT matnr
           werks
           FROM marc
           INTO TABLE t_marc
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
                 AND werks IN s_werks.
    CLEAR t_makt.
    REFRESH t_makt.
    SELECT matnr
           maktx
           spras
           FROM makt
           INTO TABLE t_makt
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
           AND spras = sy-langu.
    CLEAR t_vbap.
    REFRESH t_vbap.
    SELECT matnr
           posnr
           matkl
           vbeln
           FROM vbap
           INTO TABLE t_vbap
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr.
    CLEAR t_ekpo.
    REFRESH t_ekpo.
    SELECT ebeln
           ebelp
           bukrs
           werks
           lgort
           matnr
           mandt
           FROM ekpo
           INTO TABLE t_ekpo
           FOR ALL ENTRIES IN t_mara
           WHERE matnr = t_mara-matnr
           AND werks IN s_werks.
ENDIF.
CLEAR t_kna1.
REFRESH t_kna1.
SELECT kunnr
         land1
         name1
         INTO TABLE t_kna1
         FROM kna1.
WHERE WERKS in s_werks.
ENDFORM.                    " GET_DATA
*&      Form POPULATE_FINAL_TABLE
      text
--> p1        text
<-- p2        text
FORM populate_final_table .
*AVOID LOOPS AND TRY TO USE READ
CLEAR t_final.
REFRESH t_final.
LOOP AT t_mara.
    MOVE t_mara-matnr TO t_final-matnr.
    MOVE t_mara-mtart TO t_final-mtart.
    MOVE t_mara-meins TO t_final-meins.
    READ TABLE t_marc WITH KEY matnr = t_mara-matnr.
    MOVE t_marc-werks TO t_final-werks.
    READ TABLE t_makt WITH KEY matnr = t_mara-matnr.
    MOVE t_makt-maktx TO t_final-maktx.
    MOVE t_makt-spras TO t_final-spras.
    READ TABLE t_vbap WITH KEY matnr = t_mara-matnr.
    MOVE t_vbap-posnr TO t_final-posnr.
    MOVE t_vbap-matkl TO t_final-matkl.
    MOVE t_vbap-vbeln TO t_final-vbeln.
    READ TABLE t_ekpo WITH KEY matnr = t_mara-matnr.
    MOVE t_ekpo-bukrs TO t_final-bukrs.
    MOVE t_ekpo-ebeln TO t_final-ebeln.
    MOVE t_ekpo-ebelp TO t_final-ebelp.
    MOVE t_ekpo-lgort TO t_final-lgort.
    READ TABLE t_kna1 WITH KEY kunnr = t_mara-kunnr.
    MOVE t_kna1-kunnr TO t_final-kunnr.
    MOVE t_kna1-name1 TO t_final-name1.
    MOVE t_kna1-land1 TO t_final-land1.
    APPEND t_final.
    CLEAR :t_final,t_mara,t_marc,t_makt,t_ekpo,t_vbap.
ENDLOOP.
ENDFORM.                    " POPULATE_FINAL_TABLE
*&      Form DISPLAY_OUTPUT
      text
--> p1        text
<-- p2        text
FORM display_output .
LOOP AT t_final.
    WRITE : 4 t_final-matnr,
    20 t_final-mtart,
    28 t_final-meins,
    46 t_final-werks,
    58 t_final-maktx,
    71 t_final-spras,
    78 t_final-posnr,
    100 t_final-matkl,
    115 t_final-vbeln,
    130 t_final-kunnr,
    142 t_final-name1,
    156 t_final-land1,
    168 t_final-bukrs,
    190 t_final-ebeln,
    205 t_final-ebelp,
    208 t_final-lgort.
ENDLOOP.
ENDFORM.                    " DISPLAY_OUTPUT

The action cannot be performed error for Webi Report

HI,
I am getting the error The action cannot be performed error for Webi Report. I am getting this error after i save the report and open it again.

This is happening for only 1 particular report. In the end i removed some of the objects from the query and added some new ones.
Strangely it worked!

Performance Tuning for Concurrent Reports

Hi,
Can you help me with Performance Tuning for Concurrent Reports/Requests ?
It was running fine but suddenly running slow.
Request Name : Participation Process: Compensation program

What is your application release?
Please see if (Performance Issues With Participation Process: Compensation Workbench [ID 389979.1]) is applicable.
To enable trace/debug, please see (FAQ: Common Tracing Techniques within the Oracle Applications 11i/R12 [ID 296559.1] -- 5. How does one enable trace for a concurrent program INCLUDING bind variables and waits?).
Thanks,
Hussein

Bad performance of Java Web Report in BI 7

We are experiencing poor performance with Java web application(EP)
comparing to that with ABAP web.
We migrated our BI reports from the ABAP web interface to the Java web
interface due to our upgrade to Netweaver2004 environment.
The problem is that it takes much longer time to load the BI reports in
Java web than in ABAP web.
It is the same situation in RSRT. Java web needs more time to execute
the same query.
there is no EP logon performance delay, so I think the EP is configured good.
But the response time of BI Java Web Report is delayed average of 4~5
seconds in every Query compared in that of ABAP Web report.
Anyone experience this situation?

Hi,
I am facing similar problem. How did you solve it?
Regards,
Apurva

Performance Tuning for OBIEE Reports

Hi Experts,
I had a requirement for which i have to end up building a snowflakt model in Physical layer i.e. One Dimension table with Three snowflake tables(Materialized views).
The key point is the Dimension table is used in most of the OOTB reports.
so all the reports use other three snowflakes tables in the Join conditions due to which the reports take longer time than ever like 10 mints.
can anyone suggest good performance tuning tips to tune the reports.
i created some indices on Materialized view columns and and on dimension table columns.
i created the Materialized views with cache Enabled and refreshes only once in 24 hours etc
is there anything i have to improve performance or have to consider re-designing the Physical layer without snowflake
Please Provide valuable suggestions and comments
Thank You
Kumar

Kumar,
Most of the Performance Tuning should be done at the Back End , So calculate all the aggregates in the Repository it self and Create a Fast Refresh for MV and you can also do one thing you can schedule an IBOT to run the report every 1 hour or some thing so that the report data will be cached and when the user runs the report the BI Server extracts the data from Cache
Hope that helps
~Srix

ABAP Programs Performance Tuning and Web Services

Hi,
Can anyone give me any good material link or eBook on SAP ABAP programs Performance Tuning. What are the things that needs to be done for performance tuning etc..
Also, any material or simple eBook on web services.
my email is [email protected]
Thanks a ton in advance.
Swetha.

Check this link ABAP Development Performance Tuning
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/abap/performance%2btuning
Check these threads.
How do you take care of performance issues in your ABAP programs?
http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9bd335c111d1829f0000e829fbfe/frameset.htm

Performance tuning of a report.

hello all,
          I have been assigned a report to improve the performance.Initially after studying the report i found that all the data was fetched by using select * from... query,hence i changed the query by selectin the particular feilds from the tables.the tables used in my report r bsid and bsad majorly..after these changes there was not much of a diff in the performance,after tracing the report thru st05 it was realized that the select for bsad is taking the max time to fetch..as bsad is a huge table and has huge amount of data..is ther any way i can reduce this time..by using indexes n all..can u please provide me with an example to reduce the time taken for fetchin data from bsid and bsad..
thanks and regards,
seema.

hello again,
SELECT
      KUNNR
      UMSKZ
      AUGDT
      AUGBL
      ZUONR
      GJAHR
      BELNR
      BUZEI
      BUDAT
      BLDAT
      WAERS
      XBLNR
      BLART
      MONAT
      BSCHL
      SHKZG
      GSBER
      DMBTR
      SGTXT
      AUFNR
      HKONT
      ZFBDT
      ZTERM
      SKNTO
      REBZG
      MANSP
      MSCHL
      MADAT
      MANST
      MABER
      MWSK1
      VBELN
      XREF1
      XREF2
      KKBER
      EMPFB
      PRCTR
      XREF3
      QSSKZ
      BUPLA
    FROM   BSAD
    INTO   CORRESPONDING FIELDS OF TABLE T_BSID_TEMP
    WHERE KUNNR IN S_KUNNR
    and    BUKRS = P_BUKRS
    AND    AUGDT GT S_BUDAT-HIGH
    AND    GSBER IN S_GSBER
    AND    BUDAT IN S_BUDAT
AND    BLDAT IN S_BLDAT
    AND    KKBER IN S_KKBER
    AND    XREF1 IN s_wERKS
    AND    UMSKZ NOT IN ('B', 'G')
    AND    BSTAT NOT IN ('S').
if this is my select qury and these r the selection criteria in the wher condition how could i modify the query for better performance,
Regards,
seema.

Performance Issue with Webi report uses SAP BI Query as the data source

Hello.
I have created a Webi ad-hoc report which connects to a SAP BI query through BO OLAP universe.
The layout of Webi is the exactly the same as the BI query. There are filters in the Webi to restrict the number of data extraction, but even with data result of 5000 rows, it took about 30 seconds.
If I execute the BI query with the same filter restriction, it tooks less than 10 seconds.
It seems that large percentage of time is consumed at the MDX part.
Is there any tuning method that could speed up the process time of MDX?
Thank you.
Justine
Edited by: Justine Liu on Mar 18, 2009 6:59 AM

Hi,
please take a look here:
[https://service.sap.com/sap/support/notes/1142664] (Look under related notes)
It includes references to various performance improvements of the MDX interface. From what I saw there it is advisable to upgrade your SAP BI (7.0) up to at least Support Package 21 (you are currently on SP 15).
This may also be interesting for you: There is a new Fix Pack 1.4 coming out for BOBJ XI 3.1. Combined with the related SAP Enh.Pack (not sure about the version of this one) should also improve WebI performance. This fix pack is not yet officially released though but it should not take look.
I recommend that you try the upgrade to Support Package 21 first.
BTW it is also advisable to take a look in the results of your MDX query (e.g using the MDXTEST transaction). You should make sure that your query is indeed restricted as expected. Sometimes the results you see in SAP native reporting tools (e.g. BEx Analyzer) differ from those returned from the MDX component, depending on the way variables/restrictions where defined in the query designer. It is all about making sure that there is no apples/oranges comparison here.
Regards,
Stratos

Performance issues- query/ web reports

Hi all,
i am facing some problems related to performance in queries and in web.
In web, some times i even getting timed out errors. could any one suggest me the ways to improve the both.
regards
kiran

see if this helps...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/4c0ab590-0201-0010-bd9a-8332d8b4f09c
Thanks,
Raj

Performance Tuning for a report

Hi,
We have developed a program which updates 2 fields namely Reorder Point and Rounding Value on the MRP1 tab in TCode MM03.
To update the fields, we are using the BAPI BAPI_MATERIAL_SAVEDATA.
The problem is that when we upload the data using a txt file, the program takes a very long time. Recently when we uploaded a file containing 2,00,000 records, it took 27 hours. Below is the main portion of the code (have ommitted the open data set etc). Please help us fine tune this, so that we can upload these 2,00,000 records in 2-3 hours.
select matnr from mara into table t_mara.
select werks from t001w into corresponding fields of table t_t001w .
select matnr werks from marc into corresponding fields of table t_marc.
loop at str_table into wa_table.
if not wa_table-partnumber is initial.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
   EXPORTING
     INPUT         = wa_table-partnumber
     IMPORTING
    OUTPUT        = wa_table-partnumber
endif.
clear wa_message.
read table t_mara into wa_mara with key matnr = wa_table-partnumber.
if sy-subrc is not initial.
concatenate 'material ' wa_table-partnumber ' doesnot exists'
into wa_message.
append wa_message to t_message.
endif.
read table t_t001w into wa_t001w with key werks = wa_table-HostLocID.
if sy-subrc is not initial.
concatenate 'plant ' wa_table-HostLocID ' doesnot exists' into
wa_message.
append wa_message to t_message.
else.
case wa_t001w-werks.
when 'DE40'
or 'DE42'
or 'DE44'
or 'CN61'
or 'US62'
or 'SG70'
or 'FI40'
read table t_marc into wa_marc with key matnr = wa_table-partnumber
                                        werks = wa_table-HostLocID.
if sy-subrc is not initial.
concatenate 'material' wa_table-partnumber ' not extended to plant'
wa_table-HostLocID into wa_message.
append wa_message to t_message.
endif.
when others.
concatenate 'plant ' wa_table-HostLocID ' not allowed'
into wa_message.
append wa_message to t_message.
endcase.
endif.
    if wa_message is initial.
      data: wa_headdata type BAPIMATHEAD,
      wa_PLANTDATA type BAPI_MARC,
      wa_PLANTDATAx type BAPI_MARCX.
      wa_headdata-MATERIAL = wa_table-PartNumber.
      wa_PLANTDATA-plant = wa_table-HostLocID.
      wa_PLANTDATAX-plant = wa_table-HostLocID.
      wa_PLANTDATA-REORDER_PT = wa_table-ROP.
      wa_PLANTDATAX-REORDER_PT = 'X'.
      wa_plantdata-ROUND_VAL = wa_table-EOQ.
      wa_plantdatax-round_val = 'X'.
      CALL FUNCTION 'BAPI_MATERIAL_SAVEDATA'
        EXPORTING
          HEADDATA                   = wa_headdata
         PLANTDATA                  = wa_PLANTDATA
         PLANTDATAX                 = wa_PLANTDATAX
      IMPORTING
         RETURN                     = t_bapiret
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
write t_bapiret-message.
endif.
clear: wa_mara, wa_t001w, wa_marc.
endloop.
loop at t_message into wa_message.
write wa_message.
endloop.
Thanks in advance.
Peter
Edited by: kishan P on Sep 17, 2010 4:50 PM

Hi Peter,
I would suggest few changes in your code. Please refer below procedure to optimize the code.
Steps:
           Please run SE30 run time analysis and find out if ABAP code or Database fetch is taking time.
           Please run extended program check or code inspector to remove any errors and warnings.
           Few code changes that i would suggest in your code
          For select query from t001w & marc remove the corresponding clause as this also reduces the performance. ( For this you can define an Internal table with only the required fields in the order they are specified in the table and execute a select query to fetch these fields)
          Also put an initial check if str_table[] is not initial before you execute the loop.
          where ever you have used read table. Please sort these tables and use binary search.
          Please clear the work areas after every append statment.
          As i dont have a sap system handy. i would also check if my importing parameters for the bapi structure is a table. Incase its a table i would directly pass all the records to this table and then pass it to the bapi. Rather than looping every records and updating it.
Hope this helps to resolve your problem.
Have a nice day
Thanks

Report running for long time & performance tuning

Hi All,
(1). WebI report is running for long time.so what are the steps i need to check for it ?
(2). Can you tell me about performance tuning in BO ?
please help me.....
Thanks
Kumar

(1). WebI report is running for long time.so what are the steps i need to check for it ?
The first step is to see if the problem lies in the query on the data source or in webi itself. Depending on the data source there are different ways to extract the query and try to run it against the database. Which source does your report uses?
(2). Can you tell me about performance tuning in BO ?
I would recommend to start by reading the administrator's guide. There is a section about how to improve performance.
Regards,
Stratos

Web reporting performance

Hi,
We are experiencing very slow response times when viewing reports over the web. We get a connection time out in most cases. Can somebody provide any guidance as to how to optimize/improve web reporting performance. Thanks for your help.
SC

Hello:
Since you stated explicitly "when viewing reports over the web", I assume that your performance issue has been isolated to some extent (web queries instead of general query problems). Therefore things like aggregates and the timeout parameter are not likely your main bottleneck (you would notice the issue for all queries).
I would start here - on SDN, Business Information Warehouse > Performance Tuning section. The whitepaper on the performance tuning topic is available there, which is quite comprehensive.
Since the issue appears to be web-related, I would speculate that there may be an IGS issue. When analyzing the performance data, make sure that the front-end times for the queries you have problems with are high. Network overhead is a component to this - since BWQ results are compressed this shouldn't be a big overhead though.
In terms of optimizing/improving web performance, your killer apps are precalaculate template / information broadcasting. These techniques allow you to run the query ahead of time in the background and store the result set to deliver immediately when the user runs a query.
Good luck with the performance analysis. If you hit a wall you may consider contacting SAP Active Global Support or SAP Consulting for further assistance.
Regards -
Ron Silberstein, SAP

2004s Web report performance is not good ,though that of 3x web is OK.

Hi,
I feel 2004s Web report performance is bad, though that of 3x web is no problem (the same query is used.) it is worse than BEx analyzer.
This query has more than 1,000 records and those queries that have many records result in the same bad performance.
Of course there are many reason for this bad performance, please tell me your solution by which you solve the same problem like this.
the SIDs of EP and BI is difference here.
CPU is not consumed when 2004s web report is executed.
And I have cancelled virus scan to this web report...
Kind regards,
Masaaki

It is bad, am sure it's down to the new .net and java based technology. Aggregates are a way forwards though from what i've heard of the BI Accelerator this is the real way forwards.

How to increase performance in webi report?

Hi Experts,
I have create report top of universe with 1 query.But inside report i created multiple tabs.Data also less but while executing the report it will take so much time. How should decrease the waiting time.
I followed performance optimization:
1. ALL formula created in Bex itself.
2.Enable Query Stripping
3. Remove auto width and auto height.
4.scheduling the report.
Please tell another some performance tuning.

You'll want to determine where the time is being spent. You can trace the BW side to see how long it is taking on that end but it is probably the design of the report that is taking the time. Are you using a UNV universe going to a BEx query or a BICs based connection?
Query Stripping is automatically on for BI 4.0 SP5+ for BICs connectivity. There are also a number of optimizations that can help improve performance in the newer Support Packages.
Determining where the bottleneck is is the first step.
thanks
Jb

Performance Tuning of webi report BO4.0

Similar Messages

Maybe you are looking for