Show TOC

Function documentationConfiguring ASR Overload Protection

 

BW-based reporting and other applications extract ABAP statistics (ASR) from managed systems, into the Business Warehouse assigned to the SAP Solution Manager. The ASRs take the form of individual profiles which each contain details of one aspect of ABAP system usage.

The resulting volume of data depends heavily on the usage of the managed systems, and cannot be predicted accurately. Im the worst case, the volume of data can be so large that resource bottlenecks impair the entire Solution Manager system.

To avoid such an impairment of the system, there is an ASR overload protection which automatically restricts the volume of data. The data is compressed by the removal of details, which reduces the system load, but some information which may be important for reporting applications, is also lost.

The default configuration stores up to 10000 data records per hour, per instance of the managed system, and per ASR profile.

Activities

You can configure the overflow protection in three ways:

  • When the overload protection becomes active, the system sends the message ABAP Stat. Data Overflow; Protection Active, in the BW-Based Reporting Self-Monitoring. You can accept the activated compression for the managed system and the ASR profile (and thus forego details), or deactivate the compression, when your technical infrastructure can handle the data volume, or it was a one-off overflow situation (see Confirm or Deactivate ASR Overload Protection).

  • The default configuration of 10000 data records per hour can be too many or too few, depending on the scenario and usage of the data, or the technical prerequisites of your IT infrastructure, so you can adjust the number of data records from which overflow protection is active, per managed system and ASR profile (see Configuring Activation of ASR Overflow Protection).

  • Overflow protection deletes the details of some fields in the ASR profile. The field sequence is determined automatically. You can also configure the overflow protection so that specified field, which you need for your reporting, are protected from compression(see Retain Specified Fields in ASR Overflow Protection).

To summarize, you can configure overflow protection as follows:

  • You can deactivate protection on system and profile level.

  • You can specify the threshold values from which the protection is activated.

  • You can specify which data is deleted by the protection.

You can also influence the data volume by configuring extractors. For more information, see Changing ASR Aggregate Extraction Settings.