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
swetha

Hi ,
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

Similar Messages

  • Best Practice For Cube Design

    All,
    First post here and was wondering if anyone out there has a best practice for cube design or optimisation. Currently have 7 Cubes that have been populated for the last 6 months and am now looking at ways of speeding up their population.
    Are there any hard and fast rules about dimensions?
    Should they be kept to a percentage of the fact table?
    When should line item dimensions be used?
    Regards
    Gary Boyle

    Hi Gary,
    Ideally the DIM tables should be 20% of the fact table and preferably less. You can check the size ratios in RSRV using the Database tables test > Database info about InfoProvider tables. Line items dimensions should be employed where the char has a large number of unique values (like 0MATERIAL, or 0CUSTOMER), so that anothe DIM ID is not created, but the SID values are used directly in the Fact Table.
    See these for more:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/10b589ad-0701-0010-0299-e5c282b7aaad
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/08f1b622-0c01-0010-618c-cb41e12c72be
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84
    Hope this helps...

  • ODS Bex Reporting Indicator

    Hello All
    We are using BW V3.5 and an ODS 0FIGL_O02. In the data model,  this ODS was feeding up to a cube and we were reporting off a multiprovider. We encountered load and performance issues so as part of a model review we switched off the Bex Reporting Indicator in the ODS settings. It made little difference to our performance problem so we simplified the model and decided to report off the ODS after switching back on the indicator. We transported the ODS and the report separately.
    This solution worked fine in our DEV and QAS clients but not in the live system. Using Bex we can open the query in prod but when we run (via a portal) we are getting the error message that "ODS 0FIGL_O02 not configured for Bex Reporting". Also if we attempt to create a new report on the ODS in Bex the ODS cannot be found.
    We can see the Bex indicator is on in all clients. We have used RSDG_ODSO_ACTIVATE to check the ODS consistency in all clients and in Prod we get an amber light with the message "The Bex reporting was switched on for ODS object  0FIGL_O02" and a green light with the message "ODS object 0FIGL_O02 is consistent".
    We have tried creating a new ODS using 0FIGL_O02 to copy from but again encounter the same problem in Prod.
    Does anyone have any input or come across the same problem ? Should we create a brand new ODS ...?
    Thanks in advance for your input.

    Helen,
    You can switch On BEx reporting, even ODS contains data. Initial activation of ODS takes time, as it tries to create/generates SID's for historic data.
    Using "Foreign Key Relationship of Reporting-Relevant ODS Object and SID Table Characteristics" showed 2 red lights for data entries in the ODS, fine, but a data issue shouldnu2019t affect the ODS Object status?
    We also get an amber light that BEx Reporting was switched on for the ODS u2013 how would we get this light to green given we canu2019t change settings in live client u2013 have already tried OSDG_ODSO_ACTIVATE and as previous posting re transporting.
    Try to correct in RSRV, using option correct at menu bar. Have you tried, are you getting any message...? after correction do test again... it should be green.
    Try to find out any program or function module and reactivate ODS data again to generate SID's again.
    Hope it Helps
    Srini

  • How to handle the errors using RSRV tcode

    Hi all,
           Could any one give tell me how to handle the errors,(if possible give me some example errors)and correct the errors using RSRV tcode.
    Thanks & Regards,
    Aswini.

    Hello Aswini,
    For further details on RSRV go through the link:
    http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/frameset.htm
    Hope it helps
    Cheers
    SRS

  • 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
    hari

    Hi 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

  • What is RSRV why we use it.

    Hi Experts,
    I need to know about SAP BW tool RSRV.
    please share your knowledge of RSRV (what is it, why we use).

    Hi Sulochan,
    Kindly have a look at below links,
    http://help.sap.com/saphelp_nw70/helpdata/en/6b/cda64246c6c96ae10000000a155106/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/92/1d733b73a8f706e10000000a11402f/content.htm
    http://wiki.sdn.sap.com/wiki/display/BI/10EasyStepstoRunanyRSRVcheckinbackground!!
    Hope this helps.
    Regards,
    Mani

  • 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

  • Use of rsrv

    Hello All,
              iam doing consitency on different objects using RSRV for fiist time. please tell me how to check consistency of objects.how does succesful indicates?

    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.

  • Problem Facing while analyzing Dim/Fact Table % using RSRV

    Hi All,
    When we analyzing the infocube in RSRV to see percentage of Dimension tables, system is showing 0% for all the dimensions and also for Fact tables.
    But data is existing in fact table of infocube and also in dimensions tables, when we see in SE11.we also executed report SAP_INFOCUBE_DESIGNS in SE38, in their also we are not able to find any entry for particular infocube.Please advice on this ASAP.
    Regards
    Manoj

    Hi,
      Check whethere the statistics for the cube is run. If not refresh the stats ans then chk in RSRV or in SAP_INFOCUBE_DESIGNS you will get the ratio betwene ur dim and fact table
    Hope it helps.
    Regards,
    Malar B

  • Fact/Dim Tables entries analyzing using RSRV

    Hi All,
    When we analyzing the infocube in RSRV to see percentage of Dimension tables, system is showing 0% for all the dimensions and also for Fact tables.
    But data is existing in fact table of infocube and also in dimensions tables, when we see in SE11.we also executed report SAP_INFOCUBE_DESIGNS in SE38, in their also we are not able to find any entry for particular infocube.Please advice on this ASAP.
    Thanks & Regards
    Manoj

    1) transaction se16 -> fact table name, /bic/f[infocube name] and /bic/e[infocube name] or /bi0/f.. and /bi0/e for business content infocube, click 'number of entries'
    2) transaction db02 -> 'detail analysis' -> object name = [infocube name]
    Hope it Helps
    Chetan
    @CP..

  • Query runs forever when using selection on line item dim

    we have a cube zcube which has po number as a line item dimension .
    everymonth users run queries this cube using po number as selection
    criterai and using a wild card search on this field . every time
    queries have run fine . however , this month when we try to do so
    the query runs forever and no results are returned . i also tried
    listcubing with similar selection but it also did not return any results .
    our production system has lot of data . i tried in test system it worked fine
    i checked the cube for compression and indices in production , they look fine
    can anyone think of anything that could have gone wrong ? also did rsrv tests ..
    but all come green
    we have not done any developments on this cube , however we have shifted to
    a new hardware in the past month . can anyone think of any reasons ?
    anything that can help me catch the issue ? all suggestions welcome

    Not sure,
    Are you saying that you need both the counts seperately? or a combined count?
    how are you joining alpha and beta tables? what is the join condition?
    you need to do something like this,
    SELECT COUNT(CASE WHEN
                        (A.col1 = 'Pete' AND SUBSTR(A.col2,,1,12)=SUBSTR(B.col2,,1,13))
                     OR ( A.col1 != 'Pete' AND SUBSTR(A.col2,,1,15)=SUBSTR(B.col2,,1,15))
                    THEN 1 ELSE 0
                 END)
    FROM alpha A, beta b
    WHERE alpha.join_cloumn= beta.join_columnG.

  • What are the transactions we use day to day in the bw before go live

    what are the transactions we use most in the bw before go live?
    Tcodes for backend objects like creating infocube and so on.
    Tcodes for front end objects like creating queries and so on.
    Thank you.
    York

    Hi Les,
    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

  • Error reading data from Infocube using shell script.

    Dear all ,
    I am facing a problem while reading data from an infocube using a shell script.
    The details are as follows.
    One of the shell script reads the data from the infocube to extract files with the values.
    The tables used for extraction by the shell script are :
    from   SAPR3."/BIC/F&PAR_CUBE.COPA"     FCOPA,
           SAPR3."/BIC/D&PAR_CUBE.COPAU"    COPAU,
           SAPR3."/BIC/D&PAR_CUBE.COPAP"    COPAP,
           SAPR3."/BIC/D&PAR_CUBE.COPA1"    CCPROD,
           SAPR3."/BIC/D&PAR_CUBE.COPA2"    CCCUST,
           SAPR3."/BIC/D&PAR_CUBE.COPA3"    COPA3,
           SAPR3."/BIC/D&PAR_CUBE.COPA4"    COPA4,
           SAPR3."/BIC/D&PAR_CUBE.COPA5"    COPA5,
           SAPR3."/BIC/MCCPROD"      MCCPROD,
           SAPR3."/BIC/SCCPROD"      SCCPROD,
           SAPR3."/BIC/MCCCUSTOM"    MCCCUSTOM,
           SAPR3."/BIC/SCCCUSTOM"    SCCCUSTOM,
           SAPR3."/BIC/SORGUNIT"     SORGUNIT,
           SAPR3."/BIC/SUNIMOYEAR"   SUNIMOYEAR,
    /*     SAPR3."/BI0/SFISCPER"     SFISCPER, */
           SAPR3."/BI0/SREQUID"      SREQUID,
           SAPR3."/BI0/SCURRENCY"    SCURRENCY,
           SAPR3."/BIC/SSCENARIO"    SSCENARIO,
           SAPR3."/BIC/SSOURCE"      SSOURCE
    The problem is that the file generation by this script (after reading the data from teh infocube) is taking an unexpected time of 2 hours which needs to be maximum 10 mins only.
    I used RSRV to get the info about these tables for the infocube:
    Entry '00046174', SID = 37 in SID table is missing in master data table /BIC/MCUSLEVEL2
    Entry '00081450', SID = 38 in SID table is missing in master data table /BIC/MCUSLEVEL2
    and so on for SID = 39  and SID = 35 .
    Checking of SID table /BIC/SCUSLEVEL2 produced errors
    Checking of SID table /BIC/SCUSLEVEL3 produced errors
    Can you please let me know if this can be a reason of delay in file generation (or reading of data from the infocube).
    Also , Please let me know how to proceed with this issue.
    Kindly let me know for more information, if required.
    Thanks in advance for your help.
    -Shalabh

    Hi ,
    In continuation with searching the solution to the problem , I could manage to note a difference in the partition of the Fact table of the infocube.
    Using SE14 -> Storage Parameters, I could find the partition done for the fact table as :
    PARTITION BY: RANGE
    COLUMN_LIST: KEY_ABACOPA
    and subsequently there are partitions with data in it.
    I need to understand the details of these partitions .
    Do they correspond to each requests in the infocube(which may not be possible as there are 13 requests in infocube and much more partitions).
    Most importantly, since this partition is observed for this onfocube only and not for other infocubes, it is possible that it can be a reason for SLOW RETRIEVAL of data from this ionfocube( not sure since the partition is used to help in fast retreival of data from the infocubes).
    Kindly help.
    Thanks for your co-operation in advance.
    -Shalabh

  • 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
    hari

    hi 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

  • RSRV? Drilling through Report times out sometimes

    Hi,
    I have reviewed several documents on RSRV on SDN but I have some specific questions.
    1.  While drilling down on a particular report, sometimes it would timeout. Can you direct me how to use RSRV to figure out the problem and fix?
    2.  Also, I saw a caution in one of the postings to be careful running RSRV on production. Does RSRV automatically begins the repairs or you get the chance after the diagnoses to make a decision to repair or not?  What really can go wrong during the repairs?
    3. Also, I know RSRV has these options:
       a. Master Data Consistency Checks
       b. Transaction Data Consistency Checks
       c. Size of Dimension tables
       d. Checking SID values
       e. PSA duplicate record check
       f.  Checking Aggregates
       g. Partitions of Info cubes etc...
    Which of these options really will help me identify the intermittent problem I am having with the report? I will appreciate some stepwise guidelines on how to step through to figure out the problem.
    Thanks

    Hi,
    I tried RSRT; entered Query name; Query Display: List   
    Parameter 1 or 2  (I chose 1)
    I then selected:
    Display run schedule
    Do not use cache
    Do not suppress messages/warning
    The selection screen of the report came up report and I completed it. After execute+Debug I get the data below.
    What do I do from this point to figure out the problem and fix it:
    SQL Statement                                                                               
    SELECT                                                                               
    /*+                                                                               
    STAR_TRANSFORMATION  FACT(F)                                                                    
    "DT"."SID_0CALMONTH" AS "S____022" ,"D5"."SID_0DOC_TYPE" AS "S____130" ,                        
      "DU"."SID_0CURRENCY" AS "S____023" ,"S1"."MATL_GRP_4" AS "K____404" ,                           
      SUM (  "F"."G_AVV010"  )  AS "Z____084" , SUM (  "F"."G_AVV140"  )  AS "Z____093" ,             
      SUM (  "F"."G_AVV150"  )  AS "Z____223" , COUNT( * )  AS "Z____030"                             
    FROM                                                                               
    "/BIC/FATRUMMNP" "F" JOIN "/BIC/DATRUMMNP3" "D3" ON  "F" . "KEY_ATRUMMNP3" = "D3" . "DIMID" JO
      N "/BI0/SMATL_GRP_4" "S1" ON  "D3" . "SID_0MATL_GRP_4" = "S1" . "SID" JOIN "/BIC/DATRUMMNPP" "DP
    Execution Plan                                                                               
    SELECT STATEMENT ( Estimated Costs = 42 , Estimated #Rows = 1 ) 
         5  30 HASH GROUP BY                                         
               ( Estim. Costs = 42 , Estim. #Rows = 1 )              
               Estim. CPU-Costs = 15,234,394 Estim. IO-Costs = 34                                                                               
    5  29 HASH JOIN                                         
                   ( Estim. Costs = 41 , Estim. #Rows = 1 )          
                   Estim. CPU-Costs = 13,191,632 Estim. IO-Costs = 34
                   Access Predicates Filter Predicates               
    5  12 PARTITION RANGE SINGLE                               
           ( Estim. Costs = 5 , Estim. #Rows = 0 )              
           Pstart: KEY Pstop: KEY                               
           Estim. CPU-Costs = 19,122 Estim. IO-Costs = 4        
         5  11 TABLE ACCESS BY LOCAL INDEX ROWID /BIC/FATRUMMNP
               ( Estim. Costs = 5 , Estim. #Rows = 0 )          
               Pstart: KEY Pstop: KEY                           
               Estim. CPU-Costs = 19,122 Estim. IO-Costs = 4    
             5  10 BITMAP CONVERSION TO ROWIDS                                                                               
    5  9 BITMAP AND                                                                               
    5  4 BITMAP MERGE                                                                               
    5  3 BITMAP KEY ITERATION              
    Thanks

Maybe you are looking for