Analysis and Repair Environment

Purpose
In the analysis and repair environment of SAP BW you can perform consistency checks on the data and metadata stored in a BW system. This predominantly tests the foreign key relationships between the individual tables of the enhanced star schema of the BW system.

Integration
You can call the analysis and repair environment in the following ways: Choose Administration Analysis Tool (transaction code RSRV) from the SAP Easy Accessscreen. Choose Modeling Object Maintenance InfoObject (Transaction RSD1) from the SAP Easy Access screen. Select the InfoObject you want. Or: Choose Analyze from the initial screen.

Choose Maintain. You get to the maintenance screen. Choose Edit Analyze InfoObject. You get to the Analysis and Repair of BW Objects screen.

If you are using the analysis and repair environment for the first time you will see the message values have not been found for all setting parameters. This warns that no settings have yet been saved for your user

Features
The screen Analysis and Repair of BW Objects comprises two separate screen areas: 1. In the left-hand screen area you see a hierarchy with the list of available tests. You can select elementary or compound tests: An elementary test is a test that cannot be subdivided into smaller tests and therefore can only be executed as a whole. Elementary tests relate to master data and transaction data, ODS objects, hierarchies, a database (indices, parameters, statistics), aggregates, PSA tables, and documents. A combined test determines which elementary tests are to be performed according to the parameters entered.

You can display a short description of a test by choosing Description from the context menu of a test. 2. The right-hand screen area is empty to begin with. The tests you select are recorded here.

A selection of tests is referred to as a test package.

Compiling and executing a test package

1. Select the test you want. You can transfer an individual test or a whole folder with all the tests that exist in the hierarchical structure of this folder in your test package in the following ways: by double-clicking on the required test or folder in the left-hand side of the screen

with Drag&Drop, by transferring the required test or folder from the test list to the right-hand screen area Each selected test is displayed in the right-hand side of the screen as a closed folder.

2.

An exception to this is elementary tests without parameters. These do not appear as folders. Provide parameters for the tests. You can start parameter input in the following ways: by double-clicking on a test (a test package) by expanding the folder for the test

You do not need to provide parameters for tests that do not have them. Take note of the appropriate message after selecting the test. You get to the Parameter Input dialog box. Enter the required parameters. Input help is available in many cases. After parameters have been entered, a folder with the name Parameter is inserted under the test in question. This contains the values of the parameter. In some circumstances the name of the test is also changed so that you can see, at a glance, the parameter values for which the test is to be performed. This is particularly helpful if you have selected the same test several times and want to provide different parameters for it. If you have provided parameters for a combined test an additional Elementary Tests folder is inserted along with the Parameter folder. This folder contains the elementary tests from which the combined test is built.

You can delete individual elementary tests from the test package by using Drag&Drop to move this back to the list of tests. You can reduce the runtime of the test in this way. 3. After you have provided parameters for all tests, you can start the test run. Choose Execute. During execution the symbol for the test is changed from to to to if no errors occurred for the test, if warnings only were output, if the test produced errors.

To delete all elementary tests from the current test package that did not output errors or warnings, choose Deselect Tests Without Errors. If you want to delete the whole test package currently selected, choose Delete.

Test output
The output of the test is written to the application log and stored in the database. This means they are available for comparison with subsequent test runs. Settings can also be made for the system so that the log is automatically displayed after a test run (see under Settings). Otherwise, choose the Objects screen. You get to the Log screen. Display function from the Analysis and Repair of BW

The left-hand area of the screen contains an overview of the most recently performed test runs. By double-clicking on a folder, the system displays all messages hanging under this node as a flat list in the right-hand screen area. As long as it is available, you can display further information using the following functions: Detail Information

Long Text for Message Technical Information

Repairs
Some tests can repair any errors and inconsistencies that are discovered. However, automatic corrections are not generally possible.

If, for example, entries are missing in the SID table for a characteristic but the lost SIDs are still being used in a dimension table of an InfoCube (and the corresponding dimension key in the fact table), this can only be corrected by loading the transaction data for the InfoCube again. You must also remember that the execution of repairs depends on you executing the repairs in the right order.

SAP recommends that you always read the test documentation first and obtain a clear idea of where the errors lie, before you execute repairs. To perform repairs, return to the Analysis and Repair of BW Objects screen. If you want to start a repair, choose Remove Error. As the dataset may have changed between running the analysis and the repair, the necessary tests are executed again before the actual repair. The test output can be found in the application log.

Additional functions on the Analysis and Repair of BW Objects screen

Test package menu When you leave the analysis and repair environment, you lose the test package you see in the display. However, you can save this: Choose Edit Test Package Save (see under Menu Application Log). You can select further functions under Edit Test Package: Load (load test package) Edit (load test package for editing; the test package is then locked against external changes) Delete

Schedule (schedule test package to be executed subsequently or regularly in background processing; see under "Jobs Menu") Jobs menu If you have scheduled a test package and want to monitor its status, choose Jobs Job Overview. Application log menu This option allows you to display old logs, both from previous test runs and from scheduled test runs. You also have the option to delete test logs here. Settings menu You can make user-specific settings and save these settings using Settings Change Settings. Setting Display Result After Test Run Screen Size Selection Always / With Errors / Never

Adjust the screen areas: Control the size of the ri areas

Application Log The settings are read automatically when you start the test environment.

Modify the layout, specify an expiry date and a de

If no values are available for the settings options, the user will be notified with a message.

Executing test packages in process chains

You insert ABAP program RSRV_JOB_RUNNER to your process chain in process chain maintenance (transaction code RSPC). (To do this, select the process type ABAP Program with Drag&Drop under General Services in the process type view.) To edit process variants you have to specify the program name and the name of a program variant. Enter RSRV_JOB_RUNNER as the program name and choose a program variant name. ChooseChange. On the following screen you can either change or display variants that already exist, or create a new variant. When creating a new variant you have to specify the following: The package name (input help is available). The level of detail in which the log is to be integrated into RSRV in the process chain log.

The message type that signifies that the processing of the process chain is to be terminated. The log for the RSRV process in the process chain consists of the following parts: A summary that specifies whether errors, warnings, or no errors at all where output for each individual elementary test. A view of the log for the test package, in the level of detail specified.

If you have chosen the value 3 for the level of detail, only messages up to level 3 are included in the log of process chain processes. Messages that have been output at a lower level of a test in the test package are not displayed in this log. Note that (unlike the application log) in the processes log errors are not propagated from levels of detail to lower levels of detail. If, for example, a single error was output on level 4, it would be recorded in the summary that the corresponding test had delivered an error, but this error would not be recorded in the second part of the log. A complete log is always written, independently of the RSRV processes log in the process chain. You can display this with Application Log Display Log From Background Processing.

Restrictions
Note that there is no transport object for test packages. Therefore they cannot be transported. Process chains that execute RSRV test packages therefore have to be reworked manually after a transport to another system. The corresponding test packages have to be created.

RSRV t-code to identify partition tables

This question has been Answered.

Sap bi developer Oct 10, 2012 12:04 AM

Hi Experts, I know from SDN related articles and blog that RSRV can be used to identify the partition tables on an infocube. Can any one of you please explain the steps to follow to identify the partition tables? Our payroll cubes has partition but its not showing the following path. I followed the following path: RSRV-->TESTS IN TRANSACTION RSRV-->All elementary tests-->aggregates-->Check partitioning of aggregates for an infocube-->drag and drop and the execute by giving the cube name. I get the following message: Checks if aggregates for InfoCubes do not exist--> 2 No aggregates for non-existent InfoCubes--> 1 Also, Can you please let me know whats the way to identify the cubes which are partitioned? I have 20 cubes and I know that only 4 are partitioned. thanks!

Correct Answer by Vijay R on Oct 10, 2012 7:56 AM Hi, I guess you going with different testing at RSRV, insted of Test of Partitioning Column for InfoCube you are testing Check partitioning of aggregates for an InfoCube which is related to aggregates. Hope you need to do testing by using Test of Partitioning Column for InfoCube under Transaction Data. Regards, Rvc

CAN WE add RSRV in Process Chains???

Hi Yes we can Execute RSRV in Process Chains, for doing so SAP has provided a slandered program RSRV_JOB_RUNNER which we need to add in the process type "ABAP Program" under "General Services" in the process type view. and provide a variant of ur required RSRV activity .