ASR Profile

There are the following ASR profiles for interactive reporting and other reporting applications in the SAP Solution Manager. Follow the links, to find out more about configuration settings, to reduce the system load caused by data collection or storage:

Profile	Description of changes in BW collection settings
TREX Client	Settings to Save TREX Client Aggregates in BW
Time Profile	Settings to Save Time Profile Aggregates in BW
Web Service Consumer	Settings to Save Web Service Consumer Aggregates in BW
Web Service Provider	Settings to Save Web Service Provider Aggregates in BW
ESI Time Profile	Settings to Save ESI Time Profile Aggregates in BW
Load from External Systems	Settings to Save External System Load Aggregates in BW
Inbound Queue	Settings to Save Inbox Queue Aggregates in BW
RFC Client	Settings to Save RFC Client Aggregates in BW
RFC Client Destination	Settings to Save RFC Client Destination Aggregates in BW
RFC Server Destination	Settings to Save RFC Server Destination Aggregates in BW
RFC Server	Settings to Save RFC Server Aggregates in BW
Response Time Distribution	Settings to Save Response Time Distribution Aggregates in BW
Web Server	Settings to Save Webserver Aggregates in BW
Web Server Destination	Settings to Save Webserver Destination Aggregates in BW

The following information is shown for each profile:

Extractor Name
The secondary extractor in the Extractor Framework (EFWK) administration (e.g. WA (Statistical Records Secondary Extractor-0CCMSATPH)).
Extractor Class
All ASR profiles are processed by the same secondary extractor E2E_LUW_SECONDAR_EXTRACTOR_SSR. They only differ in the assigned extractor class (e.g. E2E_LUW_ECL_0CCMSATPH).
Analysis View in ST03
Profile in System Load Monitor (e.g. time profile). Most of the ASR profiles in BW are based on the corresponding profiles in transaction ST03.
Data Loader Profile
EFWK calls the generic function module ASRSTAT_BI_DATALOADER. This function knows a data loader profile for each ASR profile, which describes which granularity is written in which data destination, and how the data is reorganized (e.g. 0CCMAW). The profiles are defined in the table ASRSTAT_PROFILES.
Data Destinations

Each granularity is distributed among 3 data destinations per profile. The data is first written into a DSO. As soon as a granularity is completed (e.g. at the beginning of the next month for monthly granularity), the data is moved into one of two identical InfoCubes, by a subsequent process. As a profile exists in several granularities, it can have up to 18 data destinations. There are also Multicubes, which combine several data destinations, and are the basis for BW queries (see also Statistics Data Flow).
Usage

The data can be used by several applications. Changes to the settings of the extractor or data loader profiles can affect these applications.
Configuration Settings
There are several configuration possibilities for each profile, which affect the level of detail and the data volume, and thus also the data processing performance:
- BI Diagnostic Center setting
- Parameter Name
  
  Technical parameter name, used in the extractor configuration of the XML string. You can display and change the value of this parameter in the Extractor Framework administration.
  
  Note
  Change ASR Aggregate Extraction Settings tells you how to use this information to change the configuration settings.
  
  End of the note.
- Dimension
  
  The column in the program SMBI_ASR_BW_ANALYZE which is semantically linked to the configuration (see Check Table Size and Structure of ASR Aggregates).
- Info objects affected
  Info object that is no longer saved in BW in the aggregation when the associated dimension is deleted, so it is no longer available for reports.