
Creating and Processing a Recurrent Inspection with Results Storage
You can call the Code Inspector using transaction code SCI or through the path .
Decide whether the inspection is to be visible
for one user or
for all users.
To be able to create an inspection globally, you require the appropriate authorizations.
Assign a name for the inspection.
Choose Create.
The system will then:
Automatically assign a version number
Propose a deletion date when the inspection should be deleted.
Select the objects to be checked.
To do this, you can specify a predefined set of objects, a transport request, or a single object.
If you specify a set of objects, you can decide - using the appropriate button - whether it is a local or a global set of objects.
Enter a check variant.
If you specify a check variant, you can decide -using the appropriate button - whether it is a local or a global check variant.
Save your entries.
Decide whether the inspection is to be executed locally (that means, on the current application server) or parallel on several application servers in a server group.
To execute immediately on the local server, choose Execute.
If you wish to execute the inspection in parallel on several application servers, choose Execute....
The system shows a selection screen where you can decide the following:
The server group on which the inspection is to run.
Whether the inspection is to run in the background.
Choose Execute or Execute....
The system performs the inspection run.
Choose Results.
The system displays a results tree.
To see the individual results, click the appropriate node of the results tree.
To get details of the individual results, choose Information.