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


Hai all,

Can somebody refer me to any documentation that has detailed docuementaiton about RSRT- debugging queries, setting break points, testing for performance..

THank you.

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jun 10, 2005 at 03:56 PM

    Hi Visu,

    The Best Thing to learn about RSRT is goto eLearning

    there is some Performance related eClasses(SAP BW Query Performance Tuning with Aggregates -Ron Silberstein ).

    You will get the whole picture how it works !

    Check out other performance related eClasses.

    Hope this helps!!


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 10, 2005 at 03:07 PM

    Hi Visu

    Tracing the query <b>(RSRT)</b>

    The Query Monitor (transaction RSRT) allows you to execute queries and to trace queries in a debug mode with several parameters (e.g., do not use aggregates, do not use buffer, show SQL statement). In a BW 3.x system it is sufficient to enter the technical name of the query in field ‘Query’, the corresponding InfoProvider is added automatically. In a BW 2.x system you have to enter both InfoProvider and query in the format: <InfoProvider>/<Query>, without the brackets.

    There are three different display modes available, usually it does not matter which mode you choose.

    In the debug mode, you can investigate if the correct aggregate(s) are used and which statistics the query execution generates. For checking reasons, you can switch off the usage of aggregates or display the SQL statement and the run schedule.

    Moreover, in ‘Properties’ you set some performance-related query features in RSRT: read mode and OLAP query cache mode. ‘Cache Monitor’ jumps directly to transaction RSRCACHE.

    In ‘Technical Information’ you can get an overview of important technical settings of a query. Important fields are:

    • General data

    o Data Trgt(s)

    Is the query based on an ODS (O), InfoCube (B), Multiprovider (M), virtual Cube (V)? For a Multiprovider the corresponding InfoCubes and ODS objects are also listed.

    • OLAP-Relevant Data

    o Read mode

    Should be ‘Read During Navigation/Hierarchy Drilldown’’

    • Cache-Relevant Data

    o Query can use the cache

    Should be ‘Y’ except for queries based on virtual Infocubes.

    Note: The green, yellow and red signs do not necessarily mean that a problem exists. They can only give a hint.

    The Query Trace Tool (transaction RSRTRACE) allows you to record some important function module calls and process and debug them at a later stage.

    Transaction RSRCATTTRACE takes the log of RSRTRACE as input and gives aggregates suggestions for the first execution AND all further navigations performed. The functionality is similar to the Query Monitor.

    It is also possible to replay a trace within RSRTRACE (button ‘User logs’, then doubleclick on the trace). For the suggestion of optimal aggregates you have to select “DB debugging” then.

    Attention: activate the trace before you start the BEx Analyzer and don’t forget to switch off the trace after you are done!

    More information can be found in <b>SAP note 99010.</b>


    Transaction RSRV: BW Data and Metadata Test and Repair Environment.

    Transaction RSRV checks the consistency of data stored in BW. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BW system.

    The transaction interface was re-designed for SAP Portals release 3.0A. A brief guide about how to use the transaction follows.

    Starting the Transaction

    You can reach the test and repair environment

    By entering the transaction code RSRV

    From InfoObject maintenance (Transaction RSD1)

    By clicking on the "Analyze" button in the intial screen.

    After selecting a characteristic in the maintenance screen via the "Processing -> Analyze InfoObject" menu option.

    The Initial Screen

    When using the test and repair environment for the first time, the message "Values were not found for all setting parameters" draws your attention to the fact that there aren't any saved settings for your user.

    After confirming the dialog box, you reach the initial screen of the transaction. This is divided into two parts:

    1. On the left-hand side, you can see a tree structure with the pool of available tests.

    2. The right-hand side is empty at first. The tests you have selected will be put here. A selection of tests is called a Test Package here.

    Combined and Elementary Tests

    An Elementary Test is a test that cannot be divided into smaller tests and that can therefore only be executed as a whole.

    In this regard, a Combined Test determines which elementary tests are to be executed after entering the parameters. You can remove individual elementary tests from the test package before carrying out the actual test run, in order to reduce run time, for example.

    Combining a Test Package and Executing it.

    Firstly select one or more tests with drag&drop or by double-clicking. Each selected test appears as a closed folder in the view of your test package. (An exception is elementary tests without parameters: These do not appear as a folder). You can also drag a whole folder of tests from the test pool across to the right-hand screen area; all tests that are located in the hierarchical structure under this folder are then added to the test package. You can also display a short description of the test, if required. Do this right-clicking on a test and choosing "Description" from the context menu.

    Afterwards, you must supply the tests with parameters. Tests without parameters must not be given parameters. You are given notification of this when selecting them. You can enter parameters by double-clicking on a test (or a test package) or by expanding the folder of the test.

    A dialog box appears in which you must enter the required parameters. Input help is often available. After entering the parameters, a folder with the name "Parameter" is added under the test. This contains the parameter values. The test name can change in some circumstances, enabling you to see at first sight for which parameter values the test is to be executed. It is possible to select the same test several times and give it different parameters, which may even be preferable in some situations. When you have supplied the combined test with parameters, the folder with the name "Elementary Tests" is added under this one. It contains the elementary tests, from which the combined test is built. You can delete individual elementary tests in the test pool using drag & drop.

    After supplying all tests with parameters, you can start the test run by clicking on the "Execution" button. After execution, the test icons change from a gray rhombus to a red, yellow or green one, depending on whether the test had errors, warnings or was error-free.

    Test Results

    The test results are written to the application log. Depending on the settings, the system jumps automatically to this display, or you can reach it by clicking on the "Display" button. The results are saved in the database, and can therefore be compared later with additional test runs.

    In the left-hand side of the window, you can see an overview of the most recent test runs. Double-clicking on a folder displays all messages under these nodes as a flat (non-hierarchical) list in the right-hand screen area. Long texts or detail data may be available for individual messages, which can be displayed with a mouse click.


    Some tests can repair inconsistencies and errors. Automatic correction is generally not possible: If entries are missing from the SID table for a characteristic, in which case the lost SIDs are still being used in a dimension table (and the corresponding dimension keys are still being used in the fact table) of an InfoCube, you can only remove the inconsistency by reloading the transaction data of the InfoCube. Also note that you must make repairs in the correct sequence. You must always read the documentation for the test and have a good idea about how the error occured, before making the repairs.

    After executing the test run, go from the application log back to the initial screen to make these repairs. Click on the "Fix Errors" button to start an error run. Since the dataset could have changed between the test and the repair run, the required tests are executed again before the actual repair. The results can be found in the application log once again.

    Test Packages

    The test package is deleted if you do not save the test package in the display before leaving the test environment. Choose "Test Packages -> Save Test Package" in the option menu. You can do the following via options in the "Test Package" menu:

    Load packages

    Load for processing - the package is then locked against changes by others.

    Delete and

    Schedule execution at a later date or at regular intervals in background processing


    In the "Settings" menu option, you can make settings (adjust the size of the screen areas, for example) and save them. The settings are automatically read when starting the test environment. Support packages are being delivered with additional settings options since the test environment is under development at the moment. A message notifies the user at the start if there aren't any values for the setting options.

    Jobs Menu Option

    You can access the job overview via the Jobs -> Job Overview menu. Use this when you want to check the status of a test package you have scheduled.

    Application Log Menu Option

    You can display old logs from previous test runs in the dialog box, as well as scheduled ones. The option of deleting test logs can also be found here.

    New Selection Button

    The currently selected test package is deleted when you press this button.

    Filter Button

    After a test run, click on this button to remove all elementary tests without errors or warnings from the test package.

    Executing Test Packages in Process Chains

    You can add a process chain to the ABAP Programm RSRV_JOB_RUNNER in the process chain maintenance transaction, RSPC. To do this, use drag & drop to select the process type "ABAP Program" under "General Services" in the process type view. When maintaining process variants you will be asked for the program name and a program variant. Enter RSRV_JOB_RUNNER for the program name. Choose a program variant name and click on "Change". In the next screen you are able to either change or display an already existing variant, or create a new variant. When creating a new variant you will be asked for the following: Package name (an imput help on this is available), the detail level for the log to which the RSRV log in the process chain log is to be integrated, and a message type severity at which process chain processing should be terminated.

    The RSRV process log in the process chain is built as follows:

    First is a summary specifying whether errors, warnings, or no errors occurred for each elementary test.

    A log view of the RSRV test package at the specified detail level follows.

    Example: If you choose the value '3' for the detail level, only messages up to and including detail level 3 will be included in the log processes for the process chain. Messages occuring at a lower layer of the test package test are not displayed in this log. Please note that, unlike the application log, the process log does not propagate errors from deep detail levels to low detail levels. For example, if a single detail level 4 error occurs the summary will show that the relevant test delivered an error. However, this error will not be listed in the second part of the log.

    A complete log is always written independantly of the RSRV process log in the process chain. You can view this in the menu option "Application Log->Display Log->From Batch".

    I hope it is useful for you.


    Bhima Chandra Sekhar G

    Message was edited by: Bhima Chandra Sekhar Guntla

    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.