RSRV t-code
what is RSRV Transaction code
Hello narasimha42 raja ,
RSRV: BI Data and Metadata Test and Repair Environment.
RSRV checks the consistency of data stored in BI. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BI system.
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 are not 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 can therefore only be executed as a whole (or not at all).
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 (test package) or by opening a test folder.
A popup appears in which you have to enter the required parameter values. Often, there is value help available. After the parameters are entered, 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 glance for which parameter values the test is to be executed. It is possible, and often useful, to select the same test several times and give it different parameters. 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.
Repairs
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.
After a repair, the test package should be executed again in order to check that the error has been fixed.
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 Package -> Save Test Package from the main menu. You can do the following from options in the Test Package menu:
Load packages; locks are not set for the package; it can only be saved under different names.
Load for processing - the package is then locked against changes by others - and you can save the package again under a different name.
Delete and
Schedule execution at a later date or at regular intervals in background processing.
Note that the execution of test packages can be integrated in process chains. See below for how you do this.
Settings
In the Settings menu option, you can make user-specific settings (adjust the size of the screen areas, for example) and save them. These settings are read automatically when starting the test environment. Additional settings options are being delivered with support packages since the test environment is currently still under development. 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
The currently selected test package is deleted using the New Selection function (from the memory, though not from the database if the test package had already been saved).
Filter
Use Filter to delete all elementary tests without errors or warnings from the test package after a test run.
Executing Test Packages in Process Chains
In process chain maintenance, transaction RSPC, add your process chain to ABAP program RSRV_JOB_RUNNER. (To do this, in the process type view under General Services, choose the ABAP Program process type by Drag&Drop. When you maintain the process variants, you are asked to specify the program name and a program variant. Enter RSRV_JOB_RUNNER as the name of the program. Choose a program variant name and then Change. On the next screen, you can change or display already existing variants and create new variants. When creating a new variant you are asked to specify the package name (value help is available), the level of detail for the log (to which the RSRV log is to be integrated in the process chain log), and a message type that signifies process chain processing is to be terminated.
The RSRV processes log in the process chain is structured as follows:
It starts with a summary of any errors or warnings that have been produced for each elementary test.
It finishes with a view of the log from the RSRV test package, up to and including the specified level of detail.
Example: If you choose 3 as the level of detail, only messages at levels up to 3 are included in the Process Chain log. Messages produced for a more detailed level of the test package when it is tested are not displayed in this log. Note that, in contrast to the application log, errors are not passed from more to less detailed levels in the process log. For example, if a single error is produced at level 4, the initial summary reports that the test has produceded an error, but this error is not listed in the second part of the log.
A complete log is always written, independently of the log for the RSRV process in the process chain. You can view this log from the menu option Application Log -> Display Log -> From Batch.
Note that there are currently no transport objects for test packages, meaning that these cannot be transported. Process chains that execute RSRV test packages have to be postprocessed manually after being transported into another system: You have to create the corresponding test packages.
With Warm Regards,
Vineeth
Similar Messages
-
When do u go for elementary test and combined test(rsrv)
hi all,
Can anyone explain me with an realtime scenario ? when do we go for elementary test in rsrv trns code and combined test.
thanxs
harihi hari,
RSRV is used for analysis and repair of all BW objects.You can perform consistency checks on the data and metadata stored in BW System.RSRV tests the foriegn key relationships between the individual tables of the enhanced starschema of the BW system
There are 2 types of tests
1.Elementary Tests- these tests are related to master data,transaction data,ODS objects,Hierarchies.database(indices,parametres,statistics),aggregates,PSA tables and documents.
2.Combined Tests-This test determines which elementary tests are performed according to the parametres entered.
Hope this helps!
partha -
What r the diff. error that can be solved using RSRV tcode?
Hi ,
what r the diff. error that can be solved using RSRV tcode?
I want to know all the errors that can be solved using RSRV t code
if any body is having good document regarding RSRV please send it to me at
<u><b>[email protected]</b></u>
Thanx in advance,
ravi.Hi,
Refer the below links for more details about RSRV TCODE.
/community [original link is broken]
http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
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.
Repairs
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
Settings
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".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.
Hope This Helps,
This is already there in SDN.
Regards,
rik -
Report doesnt show data same as in the data target
Hi,
We have a report on a Multiprovider. Multiprovider is based on the DSO. There are some orders which are avialable in the DSO for a plant. The same orders for that plant are not shown on the report.
Please advise.
Regards
JohnTry performing couple of checks:
1) Check if query is not filtered using any filter.
2) If the missing records are of the same plant, check if there are any other characteristics which are authorization relevent and not showing you these records because you dont have enough authorization. (Make sure that if any Characteristics is Authorization relevent, you can not run the report keeping this characteristic variable OPEN (without giving any selection value). You have to run the report by giving specific value for that characteristic.
3) Make sure all the requests are activated in the DSO. If they are still in Yellow state, you wont be able to report them.
4) Check the cube/ODS consistency in RSRV t-code.
5) Also check if there is any condition applied in the query?
6) Check if any structure element / selection is restricting these records.
7) If recently master data is changed for these particular trascational data, check if attribute change run is not pending for all the characteristics in the selection screen of the query.
- Danny -
GIVE ME DETAILS FUNCTION ON T CODE RSRV DETAILS
GIVE ME DETAILS FUNCTION ON T CODE RSRV DETAILS
Hi,
RSRV is a diagnostic tool in BW, System will automatically corrects if there are any inconsistancies with the BW objects
It is used for Analysis and Repair purpose of BW objects like:
1. Master Data Consistency Checks
2. Transaction Data Consistency Checks
3. Size of Dimensio tables
4. Checking SID values
5. PSA duplicate record check
6. Checking Aggregates
7. Partitions of Info cuses etc...
You can check everything.
Just expand it > drag n drop the required test to the right panel and give the object > execute.
Transaction RSRV: BI Data and Metadata Test and Repair Environment.
Transaction RSRV checks the consistency of data stored in BI. It mostly examines the foreign key relationships between individual tables in the enhanced star schema of the BI system.
The transaction interface was re-designed for SAP BW release 3.0A. The following provides an introduction to running the transaction.
Starting the Transaction
You can reach the test and repair environment:
by entering the transaction code RSRV
in the SAP Easy Access Menu under SAP Menu -> Administration -> Analysis Tool>/>
from InfoObject maintenance (transaction RSD1)
from transaction RSD1 by choosing Analyze from the initial screen.
in the maintenance screen for a characteristic by choosing Edit -> Analyze InfoObject from the main menu.
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 are not 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 can therefore only be executed as a whole (or not at all).
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 (test package) or by opening a test folder.
A popup appears in which you have to enter the required parameter values. Often, there is value help available. After the parameters are entered, 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 glance for which parameter values the test is to be executed. It is possible, and often useful, to select the same test several times and give it different parameters. 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.
Repairs
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.
After a repair, the test package should be executed again in order to check that the error has been fixed.
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 Package -> Save Test Package from the main menu. You can do the following from options in the Test Package menu:
Load packages; locks are not set for the package; it can only be saved under different names.
Load for processing - the package is then locked against changes by others - and you can save the package again under a different name.
Delete and
Schedule execution at a later date or at regular intervals in background processing.
Note that the execution of test packages can be integrated in process chains. See below for how you do this.
Settings
In the Settings menu option, you can make user-specific settings (adjust the size of the screen areas, for example) and save them. These settings are read automatically when starting the test environment. Additional settings options are being delivered with support packages since the test environment is currently still under development. 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
The currently selected test package is deleted using the New Selection function (from the memory, though not from the database if the test package had already been saved).
Filter
Use Filter to delete all elementary tests without errors or warnings from the test package after a test run.
Executing Test Packages in Process Chains
In process chain maintenance, transaction RSPC, add your process chain to ABAP program RSRV_JOB_RUNNER. (To do this, in the process type view under General Services, choose the ABAP Program process type by Drag&Drop. When you maintain the process variants, you are asked to specify the program name and a program variant. Enter RSRV_JOB_RUNNER as the name of the program. Choose a program variant name and then Change. On the next screen, you can change or display already existing variants and create new variants. When creating a new variant you are asked to specify the package name (value help is available), the level of detail for the log (to which the RSRV log is to be integrated in the process chain log), and a message type that signifies process chain processing is to be terminated.
The RSRV processes log in the process chain is structured as follows:
It starts with a summary of any errors or warnings that have been produced for each elementary test.
It finishes with a view of the log from the RSRV test package, up to and including the specified level of detail.
Example: If you choose 3 as the level of detail, only messages at levels up to 3 are included in the Process Chain log. Messages produced for a more detailed level of the test package when it is tested are not displayed in this log. Note that, in contrast to the application log, errors are not passed from more to less detailed levels in the process log. For example, if a single error is produced at level 4, the initial summary reports that the test has produceded an error, but this error is not listed in the second part of the log.
A complete log is always written, independently of the log for the RSRV process in the process chain. You can view this log from the menu option Application Log -> Display Log -> From Batch.
Note that there are currently no transport objects for test packages, meaning that these cannot be transported. Process chains that execute RSRV test packages have to be postprocessed manually after being transported into another system: You have to create the corresponding test packages.
on RSRV
Thanks,
JituK -
What are all the errors that can be corrected by using tran code rsrv?
hi all,,
what are all the errors that can be corrected by using tran code rsrv?
can anyone list me out a list of errors that can be rectified using rsrv. And let me know the steps involved to rectify those errors using trns code rsrv.
regds
hariHi Kalyan,
I have urgent need of the RSRV DOCS.
Can you mail it to [email protected]
I will highly appreciate.
Thanks in Advance
SS
Points will be awarded -
Document related to t codes RSRT, RSRT1 and RSRV
Hi Gurus,
As This is urgent requirment for me, please help me full points will be awarded.
I want to know what are the difference between T codes RSRT, RSRT1 and their usability.
can any one help me in this regard with documentation part.
advance tanks
sekharhi sekhar,
RSRT is to scan the query as to how the query gets executed, whether it uses aggregates or cubes, full table scan or uses index, etc.
You can also change the performance of a query under the 'Properties' tab.
If you switch the Read Mode to 'A' - 'Query to Read All Data at Once', it can really kill the query performance. Instead of reading data with each navigation, it reads it all before it loads. It will speed up navigation after the report has rendered, but kill the load time.
The 'Generate Report' button can be used with the report has become corrupt. It will regenerate the report. It hasn't happened many times, but I've had reports that just failed to run when no change has been made. Regenerating the report fixed it.
Execute + Debug is a lifesaver when you need to trace user exits in your report. It has a lot of neat options.
RSRV can help you find problems with your InfoProviders. Just last week, one of my ODS objects had a bad activation. I was able to run an analysis and allow the system to correct my error. If you are unsure of the change, you can always not 'correct error' and view the log of the analysis.
hope this helps,
partha -
Hi Experts,
Please help me, it is urgent for me.
can any one give information about the T-code RSRV and its usability.
Thanks
SekharHeres one example :
<b>Issue</b>
When iam trying to load the data from PSA to Infocube, iam getting a error:
Record 2 :Error calling number range object 0LOC_CURRCY for dimension DU ( )
AND
Record 3456 :Time conversion from 0CALDAY to 0FISCPER (fiscal year V3 ) failed with value 00060202
<b>
Solution</b>
RSRV
All Elementry Tests
Master data
Compare number range and maximum sid
Run it
Correct the error -
Can anybody explain me transaction RSRV
Hi,
Please explain me about RSRV
I know it is used for repairing BW OBJECTS
In that we have elementary and combined tests
so kindly explain all the functionalities which r there in elementary and combined tests.
I will assign points.
Thanks in advance,
RAVI ALAKUNTLAhi ravi,
hi
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
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.
Repairs
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
Settings
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".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created.
hope this helps,
partha -
Transaction code to repair/check objects
Hello
Can somebody remind me transaction code to repair/check objects in BW?
Thankshi
you can use rsrv. it is for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
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.
Repairs
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
Settings
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".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created. -
Hi all,
Will you please Post usefull BW T-code.
like:
PFCG maintain role
RSPC Process chain
SU01 User Maintain
SE14 Utility for Database Tables
SE37 Function Builder
Se38 ABAP editor
SM66 Monitor Working Process
RSRT Query Monitor
Thanks in Advance
supriatnaMight be a few duplicates
MC23 Display InfoStructure
OMO1 Updating InfoStructures SD
OMO2 Updating InfoStructures Purchasing
OMO9 Updating InfoStructures Inventory Controlling
OLIS Implementation Guide LIS
BALE ALE Inbound IDOC . ALE manual processing
CMOD SAPEnhancements : Project Management
SNUM Number Ranges Object Maintenance
SPAM SAP Patch Manager
SCC4 Display View "Clients": Overview
SE38 ABAP Editor Programs
SALE ALE Cofiguration
SE37 ABAP Editor Function Modules
SE01 Transport Organizer
SE10 Customizing Organizer
SE11 Dictionary
SE16 Data Browser
SE91 Check error messages
SM04 Ovwerview of Users
SM12 Select Lock Entries
SM30 Maintain Table Views: Initial Screen
SM31 Table maintain
SM37 Job Overview
SM38 Define Job
SM59 Display and maintain RFC Destinations
SM62 Display/Edit Events
SU01 Create User Profile
SWU3 check error message
WE07 IDOC-Statistics
WE20 Partner Profiles
WE21 WF-EDI Port Definition
DB02 Table Space Monitoring
SM66 Processes on all application servers
SM50 Process on current application server
ST22 tRFC-Queue
BWMD Some Check programs on OLTP
RSO2 Generic Extraktion
BALE ALE Inbound IDOC . ALE manual processing
CMOD SAPEnhancements : Project Management
ListCube InfoCube table content
ListSchema List of InfoCube dimensions and characteristics
RSA1 Administrator Workbench
RSD1 Edit InfoObject
RSDCube System Settings - Edit InfoCube
RSDCubem Edit InfoObject
RSDIOBCM Edit InfoObject Catalog
RSDDV Aggregate Maintenance
RSIS InfoSource (Transaction Data)
RSRT Report Monitor
RSU2 Update Change Rules
SNUM Number Ranges Object Maintenance
SPAM SAP Patch Manager
SCC4 Display View "Clients": Overview
SE38 ABAP Editor Programs
SALE ALE Cofiguration
SE37 ABAP Editor Function Modules
SE01 Transport Organizer
SE10 Customizing Organizer
SE11 Dictionary
SE16 Data Browser
SE91 Check error messages
SM04 Ovwerview of Users
SM12 Select Lock Entries
SM30 Maintain Table Views: Initial Screen
SM31 Table maintain
SM37 Job Overview
SM38 Define Job
SM59 Display and maintain RFC Destinations
SM62 Display/Edit Events
SU01 Create User Profile
SWU3 check error message
SAPBWNEWS Documentation
WE07 IDOC-Statistics
WE20 Partner Profiles
WE21 WF-EDI Port Definition
DB02 Table Space Monitoring
RSB1 Check program for InfoSource / InfoCube
RSMD
RSFH
RSD5 Edit Technical Info Objects
FILE Anlegen von logischen Dateinamen
RSIMG BW Customizing Implementation Guide
RSRTRACE OLAP-Tracing für Queries
RSRV InfoCubes überprüfen
RSSB Scheduler im Batch-Betrieb
RSSM Berechtigungsobjekte Reporting pflegen
RZ11 SSO Profiel Parameter
RSBBS Jump Query -
RSRV use......?
Hi gurus,
Please let me know about the transaction code RSRV. what is the use of it. How to use it. I am trying to explore on it. but i unable to find any information onthis. can anyone help me in this.
i know that it is analysis and repair of BW objects. can anyoen tell by taking any example for understanding. or any document on this.
[email protected]
Regards
swethaHi ,
Check this <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/6b/cda64246c6c96ae10000000a155106/content.htm">Help</a>
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/92/1d733b73a8f706e10000000a11402f/content.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/92/1d733b73a8f706e10000000a11402f/content.htm</a>
RSRV is used for index , Database statics ( Eg : Any load problem in cube )
Check These Threads also
regarding rsrv
Regards
Renjith Kumar -
RSRV: W: Function not yet implemented
Hello all. I am trying to view the dimension table status using "transaction code RSRV===>Elementary Tests===>Database Tables===>Database Information about InfoProvider Tables".
Whether I try this particular function or any other function in RSRV, I get the message: "W: Function not yet implemented", and I can't get past it.
Can anyone tell me how I can activate this functionality, using RSRV? We are running BI 7.0, 2004s. You see, I want to verify the stableness of existing cubes/dimension tables, as well as verify any new cubes/dimension tables, I create in the future.
Thank you in advance.
ErnLabHi Franklin,
I tried as per your suggestion but I still get the "Not implemented error" on Windows Phone 8.1. May be I am doing something wrong here. I have attached screenshot of the error.
Below is the code I am trying,
I am having a newDoc folder inside my app.
I want to get all the files from inside this newDoc folder,which in turn have subfolders and files so I am using orderByDate because
CommonFileQuery.defaultQuery will return only files from current folder.
var localAppFolder = Windows.ApplicationModel.Package.current.installedLocation;
localAppFolder.getFolderAsync("newDoc").done(function(folderObject) {
var temp = folderObject;
var CommonFileQuery = Windows.Storage.Search.CommonFileQuery;
var results = folderObject.createFileQuery(CommonFileQuery.defaultQuery);
results.getFilesAsync().done(function getFilesSuccess(sortedFiles) {
var pathArray = [];
sortedFiles.forEach(function forEachFile(item) { pathArray.push(item.path);
The above code works as expected on desktop. Can you kindly tell me where or what I am doing wrong as I am newbie to WinJS.
Also I wanted to post screenshot of the error but was not allowed since my account is yet to be verified. -
hia
can anyone tell , when we have to use RSRV transaction and what are the precautions we have to take to use this transaction . please tell me ...
Any weblog or documentation . please tell me ....
Thanks
byehi
it's for bw objects consistency analysis and repair.
from transaction code RSRV doc itself :
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.
Repairs
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
Settings
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".
Please note that there is currently no transport object for test packages and that consequently these cannot be transported. Process chains that execute RSRV test packages must therefore be manually postprocessed after a transport to a different system: The relevant test packages must be created. -
Hello Friends
Can anyone of u pass me a Document list of all the Tcodes present in R/3 and BW.
It would be a big help.
Thanks & Regards
RohitHi Rohit,
check previous posting
Transaction Codes for BW Developers
SAP BW n R/3 transactions.
table TSTCT contains all the transaction codes
RSA6 Maintain DataSources
RSA7 BW Delta Queue Monitor
RSA8 DataSource Repository
RSA9 Transfer Application Components
RSD1 Characteristic maintenance
RSD2 Maintenance of key figures
RSD3 Maintenance of units
RSD4 Maintenance of time characteristics
RSDBC DB connect
RSDDV Maintaining Aggregates
RSIMPCUR Load Exchange Rates from File
RSISET Maintain InfoSets
RSKC Maintaining the Permittd Extra Chars
RSLGMP Maintain RSLOGSYSMAP
RSMO Data Load Monitor Start
RSMON BW Administrator Workbench
RSOR BW Metadata Repository
RSORBCT BI Business Content Transfer
RSORMDR BW Metadata Repository
RSPC Process Chain Maintenance
RSPC1 Process Chain Display
RSPCM Monitor daily process chains
RSRCACHE OLAP: Cache Monitor
RSRT Start of the report monitor
RSRT1 Start of the Report Monitor
RSRT2 Start of the Report Monitor
RSRTRACE Set trace configuration
RSRTRACETEST Trace tool configuration
RSRV Analysis and Repair of BW Objects
SE03 Transport Organizer Tools
SE06 Set Up Transport Organizer
SE07 CTS Status Display
SE09 Transport Organizer
SE10 Transport Organizer
SE11 ABAP Dictionary
SE24 Class Builder
SE80 Object Navigator
RSCUSTA Maintain BW Settings
RSCUSTA2 ODS Settings
RSCUSTV*
RSSM Authorizations for Reporting
SM04 User List
SM12 Display and Delete Locks
SM21 Online System Log Analysis
SM37 Overview of job selection
SM50 Work Process Overview
SM51 List of SAP Systems
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
LISTCUBE List viewer for InfoCubes
LISTSCHEMA Show InfoCube schema
DB02 Tables and Indexes Monitor
DB14 Display DBA Operation Logs
DB16 Display DB Check Results
DB20 Update DB Statistics
r/3 (bw related)
SBIW BIW in IMG for OLTP
BD61 Activate Change Pointers - Generally
BDLS Convert Logical System Names
BF11 Application Areas
RSA2 OLTP Metadata Repository
RSA3 Extractor Checker
RSA5 Install Business Content
RSA6 Maintain DataSources
RSA7 BW Delta Queue Monitor
RSA8 DataSource Repository
RSA9 Transfer Application Components
RSO2 Oltp Metadata Repository
RSO3 Set Up Deltas for Master Data
LO setup table
OLI1BW INVCO Stat. Setup: Material Movemts
OLI2BW INVCO Stat. Setup: Stor. Loc. Stocks
OLI3BW Reorg.PURCHIS BW Extract Structures
OLI4BW Reorg. PPIS Extract Structures
OLI7BW Reorg. of VIS Extr. Struct.: Order
OLI8BW Reorg. VIS Extr. Str.: Delivery
OLI9BW Reorg. VIS Extr. Str.: Invoices
OLIABW Setup: BW agency business
OLIFBW Reorg. Rep. Manuf. Extr. Structs
OLIIBW Reorg. of PM Info System for BW
OLIQBW QM Infosystem Reorganization for BW
OLISBW Reorg. of CS Info System for BW
OLIZBW INVCO Setup: Invoice Verification
Check out AHP's reply specifically in the link:
urgent
Assign Points if Helpful *****
Regards,
Ravikanth
Maybe you are looking for
-
How to clear "file open" dropdown list?
I have Quicktime installed on my Windows 7 system. When click the "Open File" option I get a dialog box that is a regular Windows "Open a File" box in which I can either select from the directory tree on the left or type an entry directly into the "F
-
Playing a series of extrernal audio files
Hi, I am bulding a slide show with syncronised audio I have a working version which will load a series of jpgs names 1.jpg, 2.jpg and a series of mp3s (1.mp3 etc). The problm comes when I wanted to add play and pause buttons. It works until on the se
-
TS1292 My iTunes voucher keeps saying the code is invalid
My daughter received some iTunes vouchers for Christmas, she has been able to redeem one of them but the other one keeps saying the number is invalid every time she enters the number. We have double checked that we are entering the number correctly.
-
Return Delivery when the material document has been archived
Hi There, We have a situation in which we need to return some consignment material to a vendor because we don't need it anymore. We have 74 units in unrestricted stock. The thing is that the PO's material documents have been archived. This causes we
-
I have an application that uses cursors to "zoom" onto user-selected portions of a waveform that can be acquired at different sample rates. Everything works fine except I cannot keep my cursors on the same portion of the graph when I change the sampl