Skip to Content
author's profile photo Former Member
Former Member

hi guru's how we check out the perfomence of the report

hi guru's how we check out the perfomence of the report

Add a comment
10|10000 characters needed characters exceeded

Related questions

5 Answers

  • Posted on Jan 28, 2008 at 04:43 AM

    Hi sri,

    You can use SQL TRACE to analyse the database select statements and know the performance of the report.

    SQL TRACE :

    SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05

    to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05

    and click on list trace to view the details.

    You can also perform traces on other items such as authorisation objects.

    Authorisation trace analysis 1. Open two sessions

    2. Execute transaction ST01 in one of the sessions

    3. Select the authorisation checkbox, note the other traces

    you can perform (SQL, RFC, Table Buffer etc)

    4. Click the 'Trace On' button

    5. Within your other session execte the transaction/report

    you want to trace or get the user in question to do it

    6. Return to the session where you turned the trace on and

    click on 'Trace Off' otherwise it will continue to record

    all athorisation checks

    7. Click on the 'Analysis' button

    8. Enter appropriate data into selection screen such as

    Username, type of trace records (i.e. Authorization check)

    9. Click on the Execute button.

    10. Report displaying trace results will now be displayed

    Reward Points if helpful.

    Regards,

    Sachin M M

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 28, 2008 at 04:47 AM

    Tools for Performance Analysis

    Run time analysis transaction SE30

    SQL Trace transaction ST05

    Extended Program Check (SLIN)

    Code Inspector ( SCI)

    Run time analysis transaction SE30 :

    This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.

    SQL Trace transaction ST05:

    The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.

    The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.

    The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.

    To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.

    Extended Program Check

    This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.

    Code Inspector (SCI)

    You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).

    The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.

    Run time analysis transaction SE30

    In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.

    For our case, let this be “ZABAP_PERF_TUNING”

    After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the “BACK” button.

    On the original SE30 screen, now click on “ANALYZE” button.

    The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.

    SQL Trace – ST05

    Starting the Trace:

    To analyze a trace file, do the following:

    ...

    Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.

    Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).

    If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter. Typical filter criteria are: the name of the user, transaction name, process name, and program name.

    Now run the program to be analyzed.

    Stopping the Trace:To deactivate the trace:

    ...

    Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.

    Select the trace functions that you want to switch off.

    Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-

    Analyzing a Sample trace data:

    PREPARE: Prepares the OPEN statement for use and determines the access method.

    OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.

    FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

    http://www.thespot4sap.com/Articles/SAPABAPPerformanceTuning_PerformanceAnalysisTools.asp

    Reward if usefull

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jan 28, 2008 at 09:25 AM

    Read my two blogs on the basic traces:

    SQL trace:

    /people/siegfried.boes/blog/2007/09/05/the-sql-trace-st05-150-quick-and-easy

    SE30

    /people/siegfried.boes/blog/2007/11/13/the-abap-runtime-trace-se30--quick-and-easy

    and if your report is supposed to handle mass data, then you should invest about an hour to get used to the

    trace compare report, this is a very powerful tool to find problems with scaling in a report

    Nonlinearity Check

    /people/siegfried.boes/blog/2008/01/24/nonlinearity-check-using-the-zse30compare

    Z_SE30_COMPARE

    /people/siegfried.boes/blog/2008/01/15/a-tool-to-compare-runtime-measurements-zse30compare

    Siegfried

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 06:09 AM

    hi!

    you can check out the performance by using sql trace and code inespector with the help of transaction codes STO5 and SCI respectively..

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 29, 2008 at 09:31 AM

    Hi

    Tools for Performance Analysis

    Run time analysis transaction SE30

    SQL Trace transaction ST05

    Extended Program Check (SLIN)

    Code Inspector ( SCI)

    Run time analysis transaction SE30 :This transaction gives all the analysis of an ABAP program with respect to the database and the non-database processing.

    SQL Trace transaction ST05: The trace list has many lines that are not related to the SELECT statement in the ABAP program. This is because the execution of any ABAP program requires additional administrative SQL calls. To restrict the list output, use the filter introducing the trace list.

    The trace list contains different SQL statements simultaneously related to the one SELECT statement in the ABAP program. This is because the R/3 Database Interface - a sophisticated component of the R/3 Application Server - maps every Open SQL statement to one or a series of physical database calls and brings it to execution. This mapping, crucial to R/3s performance, depends on the particular call and database system. For example, the SELECT-ENDSELECT loop on a particular database table of the ABAP program would be mapped to a sequence PREPARE-OPEN-FETCH of physical calls in an Oracle environment.

    The WHERE clause in the trace list's SQL statement is different from the WHERE clause in the ABAP statement. This is because in an R/3 system, a client is a self-contained unit with separate master records and its own set of table data (in commercial, organizational, and technical terms). With ABAP, every Open SQL statement automatically executes within the correct client environment. For this reason, a condition with the actual client code is added to every WHERE clause if a client field is a component of the searched table.

    To see a statement's execution plan, just position the cursor on the PREPARE statement and choose Explain SQL. A detailed explanation of the execution plan depends on the database system in use.

    Extended Program Check

    This can be called in through transaction SE38 or through transaction SLIN. This indicates possible problems that may cause performance problems.

    Code Inspector (SCI)

    You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).

    The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.

    Run time analysis transaction SE30

    In Transaction SE30, fill in the transaction name or the program name which needs to be analyzed for performance tuning.

    For our case, let this be “ZABAP_PERF_TUNING”

    After giving the required inputs to the program, execute it. After the final output list has been displayed, PRESS the “BACK” button.

    On the original SE30 screen, now click on “ANALYZE” button.

    The percentage across each of the areas ABAP/ Database/System shows the percentage of total time used for those areas and load on these areas while running the program . The lesser the database load faster the program runs.

    SQL Trace – ST05

    Starting the Trace:

    To analyze a trace file, do the following:

    ...

    Choose the menu path Test  Performance Trace in the ABAP Workbench or go to Transaction ST05. The initial screen of the test tool appears. In the lower part of the screen, the status of the

    Performance Trace is displayed. This provides you with information as to whether any of the Performance Traces are switched on and the users for which they are enabled. It also tells you which user has switched the trace on.

    Using the selection buttons provided, set which trace functions you wish to have switched on (SWL trace, enqueue trace, RFC trace, table buffer trace).

    If you want to switch on the trace under your user name, choose Trace on. If you want to pass on values for one or several filter criteria, choose Trace with Filter. Typical filter criteria are: the name of the user, transaction name, process name, and program name.

    Now run the program to be analyzed.

    Stopping the Trace:

    To deactivate the trace:

    ...

    Choose Test Performance Trace in the ABAP Workbench. The initial screen of the test tool appears. It contains a status line displaying the traces that are active, the users for whom they are active, and the user who activated them.

    Select the trace functions that you want to switch off.

    Choose Deactivate Trace. If you started the trace yourself, you can now switch it off immediately. If the performance trace was started by a different user, a confirmation prompt appears before deactivation-

    Analyzing a Sample trace data:

    PREPARE: Prepares the OPEN statement for use and determines the access method.

    OPEN: Opens the cursor and specifies the selection result by filling the selection fields with concrete values.

    FETCH: Moves the cursor through the dataset created by the OPEN operation. The array size displayed beside the fetch data means that the system can transfer a maximum package size of 392 records at one time into the buffered area.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.