Show TOC

Example documentationASR Aggregate Extraction Change Example


This example shows a problem with the saved data volume of the ASR aggregate (see Troubleshooting BW-Based ABAP Statistics Reporting), from diagnosis to resolution.

Note Note

The values and systems are examples; your system landscape would show other values.

End of the note.


Analyze Table Size and Structure of ASR Aggregates

Use the program SMBI_ASR_BW_ANALYZE to analyze the memory requirement and resulting system load caused by saving ASRs in the associated BW of your SAP Solution Manager. The program is described under Check Table Size and Structure of ASR Aggregates). The analysis is performed as follows in this example:

  1. Call transaction SE38, enter SMBI_ASR_BW_ANALYZE in the Program field, and choose Execute (Execute).

  2. The number of data records is displayed by ASR profile. The PROFILE column contains the profile name. In this example, RFC Server has the largest number of data records. Double-click on this profile.

  3. The next screen shows the memory usage (RECS_TOTAL) for the various ganularities, for the selected profile. You can see which granularity has a particularly high memory usage, and should be examined further. In this example, the granularity MD (monthly) has a particularly high memory usage. Double-click on this granularity.

  4. The next screen shows the memory usage by data from the various managed systems for the selected profile and granularity. You can drill down further to system level, by double-click. In this example, double-click on the managed system PRD to examine the number of its data records.

  5. The next screen shows the relative memory usage for the various dimensions of the selected profile, for the selected granularity, for the selected system PRD. The greater the value of this key indicator, the greater the amount of memory used to save the data by this dimension. In this example, the dimensions DIM_PROG and DESTINATION use most of the memory.

So most of the memory usage for the ASR aggregate is by the dimensions DIM_PROG and DESTINATION in the managed system PRD. This program has determined that in system PRD, 3.675 users use 13.746 programs which have made RFC calls to 224.785 destinations.

Check the consequences of reducing the data volume

Now check the consequences for your report of not aggregating by the dimensions DIM_PROG and DESTINATION. ASR Profiles contains this information for each profile.

The profile RFC Server is relevant for our example. Its documentation is under Settings to Save the RFC Server Aggregate in BW. The second table contains an entry for each of the two dimensions, and the Info Objects Affected column indicates that you can no longer analyze individual ABAP reports, job names or RFC destinations if you no longer aggregate by these dimensions.

Configuration Settings in the BI Diagnostic Center

In this section, you change the configuration settings to no longer save individual RFC destinations when you save ASR aggregates. You have determined in the previous section that excluding the dimension DESTINATION in the ASR profile RFC Server would considerably reduce the data volume.

The ASR profile documentation extractor configuration settings tell you that you can make this setting in the BI Diagnostic Center, under Start of the navigation path RFC Server/Client Next navigation step RFC Server Next navigation step Delete Destinations End of the navigation path.

Proceed as follows:

  1. In the navigation bar of the SAP Solution Manager Administration work center, choose Infrastructure, and BI Reporting.

  2. In the table Analysis Scenarios, select the scenario System Analyses, and Scenario Setup.

  3. Go to change mode by choosing Disply/Change.

  4. The settings are in the Data Collection Settings tab. In the Hierarchy drop-down list, select the default setting System/Category/File Name.

  5. To change the settings for a managed system, expand the ABAP system in the list, and in the Statistical Data Records (ABAP) row, choose Expert Settings. In this example, this is the system PRD.

  6. A selection of ASR profiles is displayed below the selected row. In this example, it is the area RFC Server/Client, as indicated in the documentation. Expand this profile.

  7. In this example, you want to delete the destinations for the profile RFC Server. Set the Delete Destinations flag in this area.

  8. Save your changes with Save and Execute.

Configuration Settings in Extractor Framework Management

In this section, you change the configuration settings to no longer save individual program names when you save ASR aggregates. You make this change in the Extractor Framework Management (EFWK).

Proceed as follows:

  1. The RFC Server profile documentation Settings to Save RFC Server Aggregates in BW contains the settings to save job and program names, for the dimension determined, DIM_PROG. You can make a setting in the BI Diagnostic Center table to delete job names, analogously to deleting destinations (see above).

  2. There is no similar way to delete program names, which you must do in the EKWK Administration. You need the parameter (in this example RFC_SRV_NO_PROG), and extractor (in this example WA (Statistical Records Secondary Extractor-0CCMARSH) names from the documentation. Filter by the technical ID0CCMARSH).

  3. In the SAP Solution Manager Administration work center navigation bar, choose Infrastructure, and Start of the navigation path Framework Next navigation step Extractor Framework End of the navigation path.

  4. The Extractor Overview table lists the extractors. To show the extractor whose settings you want to change, filter by its technical ID (in this example *0CCMARSH*).

  5. The extractors for all managed ABAP systems for which data of the ASR profile are collected, are shown. Select the extractor of the desired system. In this example, PRD.

  6. In the Selected Extractorsubscreen under Extractor Overview, choose the Extractor Detail and Configuration tabs.

  7. Go to change mode by choosing Display <-> Change (Display <-> Change).

  8. The XML string is output in the Additional Configuration group box. The extractor settings are in the <Configuration> tag, as XML tags.

    In this example, insert the tag <ConfigItem Parameter="RFC_SRV_NO_PROG" Value="X"/> in this area of the XML string, to specify that no program names are to be saved in the aggregates of this profile.

  9. Save your changes with Save.


You have made all settings required to restrict the data volume.