|Home • Trainings • Quiz • Tips • Tutorials • Functional • Cert Q's • Interview Q's • Jobs • Testimonials • Advertise • Contact Us|
Understanding "Coverage Analyzer"
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.
Log gives general
information, while Monitor Volume gives
detailed information of started server.
the warning is attended, select the row and hit Completed, which will going to turn yellow signal to green signal.
inconsistencies are checked; General Log
should be refreshed.
select more than 1 message, keep Cntrl
8: Display; gives coverage results at author or package level according to
criteria you select under Settings. Display gives high-level view.
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.
Recordings were not switched on; percentage-based progress display over time
cannot be seen for selected SAPDEV02 author.
Display view gives Quality Managers to view the system, the following way;
value indicates how many percent of the processing blocks have the Unicode flag
set (the flag itself is set per program)
value is computed as the ratio of used processing blocks to loaded processing
blocks to loaded processing blocks.
Accumulated Executions (Percent)
value indicates in percent how many processing blocks have been executed since
the start of the Coverage Analyzer.
processing blocks (Percent)
value indicates in percent how many processing blocks have been executed in the
actual version without runtime errors.
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%.
9: Exact Value Table can be viewed for author SAPDEV02; which displays
number processing blocks for author SAPDEV02 on timely manner.
view of the selected row can be seen using
displays graphical view of the individual date and all dates when no row is
rows selected for graphical analysis;
selection for graphical analysis;
saved history can also be viewed for the specific user.
10: Details view; gives summarized and detailed results. Details give low-level
filtering options allow user to select on what conditions results are to be
can be set for range of test-groups, packages and authors pertaining to those
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
Standard Settings is going to reset
all the values.
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.
Current Executions =
Program units currently used / Total no. of Program units.
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
©2006-2007 SAPTechnical.COM. All rights reserved.
product names are trademarks of their respective companies. SAPTechnical.COM
is in no way affiliated with SAP AG.
Graphic Design by Round the Bend Wizards