Understanding "Coverage Analyzer"


Count1 and RABAX1 indicate the number of programs executed and runtime errors since the Coverage Analyzer was started.

Count2 and RABAX2 indicate the number of programs executed and runtime errors since the last reset.  

Further, assign package to be used during analysis. When a package is pre-selected, the evaluation for the Global view is only performed for this package. If this restriction is not applied, all of the programs are included together with those from local packages ($*) and programs generated locally without packages ( ).

[SCM]actwin,-240,-319,792,427;Coverage Analyzer: Settings
8/19/2009 , 11:30:57 AM

If ABAP programs with a set Unicode flag are only to be traced by the Coverage Analyzer, then select Unicode checkbox. Checking Unicode is to mark it as ‘X’, else leave it unattended.

[SCM]actwin,-238,-402,794,344;Coverage Analyzer: Settings    
8/19/2009 , 11:33:20 AM
[SCM]actwin,-238,-401,794,345;Coverage Analyzer: Settings    
8/19/2009 , 11:35:26 AM

It’s optional to set the lights; lights provide a visual means of representing the status of the results for the degree of coverage in the Global and Detail views.

Lights are set by default, which can be set according to developer’s way of analysis.

RED                  0   LT 33  %

YELLOW          33 LT 66  %

GREEN 66 LE 100%   

  [SCM]actwin,-237,-405,795,341;Coverage Analyzer: Settings 
8/19/2009 , 11:42:54 AM

Further, Monitor Settings have to be done, which includes setting Trace Level and Maximum Entries Log and Maximum Entries Data Monitor.

There are 4 different trace levels (1-4), the higher the trace level, the more information is drawn for debugging.  

[SCM]actwin,-239,-488,793,258;Coverage Analyzer: Settings 
8/19/2009 , 11:56:15 AM

Tip: The values for Maximum Entries Log and Maximum Entries Data Monitor limit the lines displayed for the General Log and Monitor Data Volumes in the monitor function.

The defaulted lines for log file are 100 and for data volume are 200.  

Background server has to be specified, where precisely data is to be collected. Moreover, the period for which background job has to be repeated is also to be specified.

The defaulted value for Data Collection: Period (Min) is 30 mins, which can be modified based on developer’s way of analysis. In this case, current server is specified as Background server.

[SCM]actwin,-238,-544,794,202;Coverage Analyzer: Settings
8/19/2009 , 3:58:26 PM

Further, Summarization function facilitates checking the same processing blocks in several systems simultaneously.

Tip to remember: The results from the individual systems are local and those from the remote systems are summarized.

Local Degree of coverage                        LE        100%.

Summarized degree of coverage LE        100%.

Local Degree of coverage GE Summarized degree of coverage.  

To determine RFC connection with current server, call up transaction SM59->RFC Destinations->R/3 Connections->E6SCLNT900.  

Desired RFC connections in Summarize coverage results can be specified; moreover period and start time for summarize data can also be specified.

[SCM]actwin,-241,-575,791,171;Coverage Analyzer: Settings
8/19/2009 , 3:56:49 PM

Finally, save the Settings.  

STEP 3: Choose On/Off, Status in the Administration node and start up the Coverage Analyzer.

Switch Coverage Analyzer On/Off: This displays the number of programs that have been initialized.

Switch Automatic Recordings On/Off: This displays the automatic recording period and the version number for the Global view.

Switch Data Aggregations from Different Remote Systems: This displays background server and all of the other systems whose results are used for Data-aggregation.


If the server is in switched-off mode exception shows RED signal, GREEN signifies server to be in switched-on mode and YELLOW represents either RFC problem or database and shared memory inconsistency.  

In this case, we’ll proceed without switching on Switch Automatic Recording On/Off.

[SCM]actwin,-236,-145,796,601;Coverage Analyzer: On/Off Status
8/19/2009 , 4:02:15 PM

The servers which are actually running are shown as flagged up.  

STEP 4: Create Test-Groups; Test-Groups are made to summarize and display the results of the Coverage Analyzer for a particular set of users under one generic key/heading.

Tip to remember: Test-groups should not be created more than 10. Moreover, only users assigned a role with the authorization object S_COV_ADM are allowed to define group.  

Two pre-defined Test-groups are always available;

ALL    Coverage results summarized for all test groups on the local system.

COND – Coverage results on the local system as well as remote system.  

In this case, we create a test-group.

To create a test-group; switch on the Change Mode, click Append Row icon provided in the application tool-bar.

[SCM]actwin,2147483175,2147483501,0,0;Coverage Analyzer: Define Test Groups    
8/19/2009 , 2:21:50 PM

Define a Test-group following Y/Z naming convention; then save it.

[SCM]actwin,-238,-148,794,598;Coverage Analyzer: Define Test Groups
8/19/2009 , 2:29:26 PM

STEP 5: Next step is to assign users to the just-made test-group.

To assign Users to a test-group; switch on the Change Mode, click Append Row icon provided in the application tool-bar.

[SCM]actwin,2147483175,2147483501,0,0;Coverage Analyzer: Define Test Groups    
8/19/2009 , 2:21:50 PM

Select desired test-group for which users have to be assigned; in this case we assign SAPDEV02 as user to test-group ZTST.

[SCM]actwin,-237,-146,795,600;Coverage Analyzer: Registration
8/19/2009 , 2:32:23 PM

Tip: A test-group can contain any number of users, for example, all HR developers in one group. That makes filtering pretty easy. Moreover, comparison of performance of test-groups can be done in Global view.  

STEP 6: An optional function to be done is Reset; explicitly this function is intended for situations in which the results of the previous analyses are no longer required. It resets all the counters of the Coverage Analyzer to 0 for all the programs of a selected group.

Further more, implicit reset is carried out automatically as soon as the flow or the data of a program changes.

After successful reset, an information message is popped-up;

[SCM]actwin,0,0,1020,38;Coverage Analyzer: Reset    
8/19/2009 , 2:46:25 PM

STEP 7: Consistency check has to be done for all the servers including remote ones, before proceeding to actual analysis; [SCM]actwin,-237,-148,795,598;Coverage Analyzer: Consistency Checks    
8/19/2009 , 2:52:20 PM

Check Status of All Servers checks whether the status in the shared memory matches the status in the database.

Check Status of Background Jobs checks whether all the batch jobs of the Coverage Analyzer are activated. If this is not the case, the batch jobs are all rescheduled by means of the Repair function.

Check Table Consistency (Long Runtime) may become inconsistent if the Coverage Analyzer fails on an application server due to system error.

Repair function also bridges the gap between activating and generating a program.  

So, in order to check inconsistencies, check the types of inconsistencies accordingly and Execute Checks, and then choose monitor to check for the inconsistency messages,

GREEN indicates Information message, YELLOW indicates Warning message and RED indicates Error message.

[SCM]actwin,-245,-221,787,525;Coverage Analyzer: Monitor
8/19/2009 , 4:07:19 PM

Click here to continue...

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