Inspection

During an inspection, individual objects or sets of objects are checked as to whether certain programming guidelines have been adhered to. The result of an inspection run is a list of the individual checks made with errors, warnings, or information messages.

There are two types of inspections. They differ with respect to whether the results are made persistent or not.

• Recurrent inspections with results storage For execution on the local server or parallel execution on the server group. You can plan recurrent inspections as background jobs and use them for any size of object set.

• Anonymous or ad-hoc inspections without results storage For execution on the local server and for fewer than 50 objects. You can execute ad-hoc inspections in online mode only.

As an ABAP developer or quality manager, you can use the inspections to find out whether the most important programming guidelines in static ABAP coding or other object definitions have been adhered to.

The results list of the inspection consists of the following overview levels:

• The executed checks are subdivided into the check categories: performance, security, syntax, search, general.

• Each check category contains the individual test results, sorted by error, warning, or information messages.

• Each of these messages contains:

  • The position of the source code (or the name of the TADIR object)

  • A short explanation

You can create and process server groups for recurrent inspections using the transaction SE59 -> RFC groups.