During an inspection, individual objects or sets of objects are checked as to whether they adhere to certain programming guidelines or meet certain search criteria. The result of an inspection is a list of the conducted checks together with the created errors, warnings, and information messages.
There are two types of inspections, which differ with respect to whether the results are made persistent or not.
●
Persistent
inspections, the results of which are stored.
These inspections are executed on the local server or parallel in a server
group. You can plan persistent inspections in the background and in a periodic
job and run them on any size of object set.
You can create and maintain server groups for persistent inspections using the RFC server groups (transaction RZ12)
●
Anonymous
inspections, the results of which are not stored.
These inspections are executed on the local server and can only be run on no
more than 50 objects. You can execute anonymous inspections in online mode
only.
The results of an inspection are subdivided into check categories. These can be, for example, performance, security, syntax, or search. Each check category contains the individual check results, sorted by error, warning, and information messages. Each of the latter contains the position in the source code (for program-like objects), and a short explanation.
See also:
Creating and Executing Persistent Inspections
Creating and Executing Anonymous Inspections