Show TOC

Function documentationMonitoring Data Loading


In the context of BW-based reporting, the required data is transferred from the administered systems and then written to the associated Business Warehouse of your SAP Solution Manager. This is done using the Extractor Framework. For more information about managing the Extractor Framework, see Extractor Framework. Extractors are regularly started in the SAP Solution Manager system, which load the desired data from the administered systems. So that you always have an overview of the status of the data loading, the Data Loading tab page is available in the context of the Self-Monitoring of BW-Based Reporting for each scenario used.

The status messages for data loading are sorted by the administered systems. A system can appear in the list of status messages more than once, if data from a system was loaded using different extractors in the context of a scenario. This is the case, for example, if the retention period or the requested currentness of different data types is very different in a scenario. In this type of case, there are different extractors with a data loading frequency adjusted to the requirements of the respective data types.

Example Example

The performance data and the threshold values in the context of interactive reporting are loaded with different frequencies. There are therefore different extractors for each administered system that are called with different frequencies. There are therefore at least two entries in the list of status messages for each administered sytsem, with the data types Threshold Values and Monitoring Data.

End of the example.

In addition to the status of the respective data loading process, the following information is also displayed:

Column Title


System ID

System ID of the administered system, from which the corresponding extractor loads data

Data Type

Data type that the corresponding extractor loads; there can be multiple extractors active for each monitored system and scenario that load different data types

Description of Data Loading Status

Status of the last run of the corresponding extractor; if an error occurred, the error description is displayed here

Last Load

<time zone>

Time of the last extractor run and therefore the currentness of the data that exist for the selected scenario and the respective administered system in the BW

Next Load

<time zone>

Time at which the next extractor run is scheduled

Load Interval

Planned period between two successive extractor runs

Time Period

Planned time period in which the corresponding extractor is to run; this time period has two different functions:

  • The time period restricts the times during which the corresponding extractor can run at all. Therefore, if the extractor is to run every 12 hours, for example, but the time period is defined as 00:00 – 12:00, it will only run once a day, since the second run would take place outside the permitted timeframe and therefore a start would not be possible.

  • The time period specifies the range within which an extractor run is regarded as timely. If a time period of 00:00 – 02:00 is set, and the extractor is to next run at 01:00, a status message that the extractor was not started at the correct time is only displayed when the time period expires.

Data Records Loaded

Number of data records loaded in the last extractor run


Status of the connection to the administered system through which the data is transferred. You can also execute the maintenance transaction for RFC destinations (transaction code SM59), to check and edit the corresponding connection, and to correct any errors that occur. To do this, choose the Edit button.


To display the monitoring of the data loading in the context of the self-monitoring of BI-based reporting, choose the desired scenario in the Reporting Scenarios subscreen. You can find the associated information on the Data Loading tab page.