Understanding "Coverage Analyzer"


In the present case; no inconsistencies have been found while starting All Servers. In case, there arise any warning or error messages, those problems are to be fixed and then select particular row of the warning/error message and click Completed.  

General Log gives general information, while Monitor Volume gives detailed information of started server.

[SCM]actwin,-247,-222,785,524;Coverage Analyzer: Monitor
8/19/2009 , 4:09:17 PM

Once the warning is attended, select the row and hit Completed, which will going to turn yellow signal to green signal.

[SCM]actwin,-244,-327,788,419;Coverage Analyzer: Monitor
8/19/2009 , 4:09:35 PM

Tip: Every time inconsistencies are checked; General Log should be refreshed.

To select more than 1 message, keep Cntrl key pressed.  

STEP 8: Display; gives coverage results at author or package level according to criteria you select under Settings. Display gives high-level view.

Views can be based on Author or Package. ALL signifies all the authors on local system based on view given and the COND (y/z test groups) signifies all the authors on both local and remote systems based on view given. If ‘Other view’ is selected as Package, then selection is done accordingly.

[SCM]actwin,0,0,313,200;Coverage Analyzer: Change View      
8/19/2009 , 4:27:00 PM

Note: Since Automatic Recordings were not switched on; percentage-based progress display over time cannot be seen for selected SAPDEV02 author.  

Normally, Display view gives Quality Managers to view the system, the following way;


This value indicates how many percent of the processing blocks have the Unicode flag set (the flag itself is set per program)  

Capacity Utilization:

This value is computed as the ratio of used processing blocks to loaded processing blocks to loaded processing blocks.  

Accumulated Executions (Percent)

This value indicates in percent how many processing blocks have been executed since the start of the Coverage Analyzer.  

Tested processing blocks (Percent)

This value indicates in percent how many processing blocks have been executed in the actual version without runtime errors.

In the example above you can see that currently 98% of the processing blocks in the system belong to a program that has the Unicode flag set, 26% have been executed since start of the coverage analyzer, 9% have been executed in the active version without errors and the capacity utilization is 29%.  

STEP 9: Exact Value Table can be viewed for author SAPDEV02; which displays number processing blocks for author SAPDEV02 on timely manner.

Graphical view of the selected row can be seen using [SCM]actwin,-428,-30,438,695;Value Table      
8/19/2009 , 4:36:33 PM
 icon; that displays graphical view of the individual date and all dates when no row is selected.

All rows selected for graphical analysis;

[SCM]actwin,156,9,1022,734;Value Table      
8/19/2009 , 4:45:08 PM

Individual selection for graphical analysis;


Tip: Moreover, previous saved history can also be viewed for the specific user.  

STEP 10: Details view; gives summarized and detailed results. Details give low-level view.

Strong filtering options allow user to select on what conditions results are to be displayed.  

[SCM]actwin,-238,-147,794,599;Coverage Analyzer: Detail
8/19/2009 , 4:52:17 PM

Conditions can be set for range of test-groups, packages and authors pertaining to those test-groups.

In the present example; test-group ZTST and Author SAPDEV02 is taken as single-value selection, which gives results pertaining to specified criteria. Moreover, other filters can also be set and settings should be done defining access via Package Object, Package and Author. Defaulted access-via is Program Object.

[SCM]actwin,-240,-181,792,565;Coverage Analyzer: Detail
8/19/2009 , 4:55:34 PM

Hitting Standard Settings is going to reset all the values.  

Once settings are done; hit execute button, that is going to get detailed information, including number of calls made to that particular object, number of  processing blocks, load size in Kilo byte. Besides all the information given; double-clicking the object name will navigate to the particular program or executing block where exactly error has been found.

[SCM]actwin,-240,-151,792,595;Coverage Analyzer: Program Objects
8/19/2009 , 5:04:54 PM

[SCM]actwin,-242,-209,790,537;Coverage Analyzer: Processing Blocks
8/19/2009 , 5:07:59 PM

Note: Current Executions = Program units currently used / Total no. of Program units.

Capacity Utilization = No. of Program units currently used / Loaded Program units.  

Conclusion: Likewise, many such program executions, runtime errors and program resets can be easily traced using this powerful ABAP runtime analysis tool - Coverage Analyzer.

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image