Show TOC

Component documentationSelf-Monitoring of BW-Based Reporting


BW-based reporting provides you with a large number of scenarios in SAP Solution Manager, in which reporting data is collected across systems in SAP NetWeaver Business Warehouse (BW). This means that all of the possibilities of the BW are available for your reporting. The Extractor Framework is used across scenarios as the infrastructure for centrally loading the data. For more information about managing the Extractor Framework, see Extractor Framework.

The BI Diagnostic Center is available to support you in troubleshooting and administering BW-based reporting. The status of the connections between the SAP Solution Manager system and the associated BW are shown here; you can also see the current staus of BW-based reporting, broken down by the different scenarios. This includes the following information:

  • Overall Status

    Are there problems that are affecting the functioning of the scenario?

  • Status of the Data Loading

    Is this scenario being provided with data by all managed systems? Are the RFC destinations in the managed systems functioning correctly?

  • Used Storage in the Database

    How much space does the reporting data collected for this scenario in BW require?

  • Result of the Self-Checks

    Are there problems that are affecting the correct functioning of the scenario? If problems occur, the cause and consequences are described in detail, together with options for solving the relevant problem.

Scenarios including the following are currently reporting values in the self-monitoring of BW-based reporting:


To call the self-monitoring of the BW-based reporting, in the navigation bar of the SAP Solution Manager Administration work center, choose Infrastructure, and BW Reporting.

The different subscreens provide the following information:

  • BI Status

    For the correct functioning of BW-based reporting, RFC destinations are required in both directions between the SAP Solution Manager system and the associated BW. The status of these destinations, which are created in the SAP Solution Manager configuration, is displayed; you can also edit the RFC destinations. If there are no problems for the RFC destinations, this subscreen is collapsed, by default.

    The overall storage requirement and the fill level of the BW database are also shown.

  • Reporting scenarios

    This subscreen displays a table of all scenarios that report values to the self-monitoring, containing the following information:

    Column Title



    Status of the relevant scenario; the time stamp of the last check is shown as a quick link


    Name of the scenario

    Date of Last Load Process

    <time zone>

    Time of the last extractor run and therefore the currentness of the data that exists for the selected scenario in the BW

    Note Note

    For each scenario, there can be multiple extractor types with different load intervals that read different data types from the managed systems. One of these extractors is always identified as the main extractor (for example, for interactive reporting, there are extractors for monitoring data and threshold values; in this case the main extractor is the one that reads the monitoring data).

    This column shows the start of the main extractor from the managed system that was started longest ago. This ensures that the data from all managed systems is at least as current as the currentness shown here.

    End of the note.

    Date of Next Load Process

    <time zone>

    Time at which the next extractor run of the extractor from the Date of the Last Data Load is scheduled.

    Load Interval

    Planned period between two successive extractor runs of the main extractor

    Total DB Storage Space

    Entire storage of the database that this storage is currently using; this includes both data that is required only for this scenario and data that is also used by other scenarios.

    Performance (s/Call)

    Average response time for a call of a report for the relevant scenario (last 24 hours)

    You can call additional information that is primarily intended for experts by choosing the Expert Mode button:

    Column Title


    Exclusively-Used DB Storage Space

    The storage on the database that is exclusively required for this scenario; it is therefore the storage that you would gain if you removed this scenario

    Last 24 Hours: Report Calls

    Number of reports calls for the relevant scenario (last 24 hours)

    Performance (s/Call)

    Average response time for a call of a report for the relevant scenario (last 24 hours)

    Last 7 Days: Report Calls

    Number of report calls for the scenario (last 7 days)

    Performance (s/Call)

    Mean response time in seconds to a call of a report in the scenario (in the last 7 days), i.e the time that the user has to wait when calling the report.

    Note Note

    You can start or repeat the configuration for the displayed scenarios from this screen. To do this, choose the Scenario Setup button. This configuration is initially performed in the SAP Solution Manager configuration (transaction SOLMAN_SETUP).

    End of the note.

To display additional details of the status of a scenario, choose the corresponding row in the table Analysis Scenarios. The following tab pages are displayed in another subscreen for this scenario:

  • Data Loading Process

    This tab page displays the status messages about loading data, broken down by managed systems. For more information about this tab page, see Monitoring Data Loading.

  • Self-Checks

    For the scenarios of BI-based reporting, a large number of self-checks have been created that check the prerequisites for correct functioning of the relevant scenario and monitor the scenario itself for possible errors. The associated messages are displayed with the results in a list, grouped by checks. For more information about this tab page, see Messages of the BW-Based Reporting Self-Check.

  • Data Quality

    For the System Reporting scenario (interactive reporting), the reliability of the data provision for the reports, depending on the managed system, is shown. The current status of the reports, by managed object types, is displayed in various tabs. The data quality of the overview report is output in the System Overview tab.

    The report status is Green if the following conditions are fulfilled:

    • If Technical Monitoring data is displayed in the report, there must be data which is less than 24 hours old, for all metrics displayed in the report, so data must have been provided within the last 24 hours. For more information about saving MAI data in BW, see Passing and Saving MAI Data in the Business Warehouse. If the data quality status is red, troubleshooting information is under MAI: Troubleshooting Tool.

    • If the report shows ABAP statistics (ASR) , the last runs of the secondary extractors which get data for the report, must have run without errors. For more information about saving ABAP statistics in BW, see Passing ABAP Statistics to the Business Warehouse. If the data quality status is red, troubleshooting information is under ASR: Troubleshooting Tool.

    Note Note

    The status of a report and system in the Data Quality ist gray, if no values have yet been determined for them. This can be the case, for example, if the system has not been configured. The System Overview also shows the status "Gray" for a lot of reports, because their data is only collected for ABAP systems, and all types of managed objects are displayed in the System Overview.

    End of the note.

You can call additional information that is primarily intended for experts by choosing the Expert Mode button:

  • DB Usage

    This tab shows the entire memory in the database that this scenario is currently using, sorted by Info Providers. The sum corresponds to the Total DB Memory, above. This tells you which data in the scenario use which database space - the Info Providers are objects in BW, and typically contain data for a topic, or technically-related data, within a scenario. The documentation of the Info Providers is under BI Content for SAP Solution Manager.

    System Reports (Interactive Reporting) is often the scenario which uses the most DB memory, above all the reports which use ABAP statistics. The DB Usage tab shows the ASR profiles which use the most memory, under ABAP Statsitics, under Info Provider Name. If the ASR data volume is too great, you can see here, where forgoing certain detail data would have the most effect. For more information, seeTroubleshooting BW-Based ABAP Statistics Reporting.

  • Report Performance

    The usage and the performance of the reports for the various scenarios are output. Report Path runs the report, if the application is running. Report Name is the Web template which the report calls.

    It shows which reports were called how often, in the last 24 hours and the last seven days, and the report creation response time. This information indicates performance problems, and whether, and how intensively, which reports are used.