Start of Content Area

Procedure documentation Creating and Processing Inspections  Locate the document in its SAP Library structure

Creating and Processing a Recurrent Inspection with Results Storage

...

       1.      You can call the Code Inspector using transaction code SCI or through the path SAP Menu à Tools à ABAP Workbench à Test à Code Inspector.

       2.      Decide whether the inspection is to be visible This graphic is explained in the accompanying text locally for one user or This graphic is explained in the accompanying textglobally for all users.

To be able to create an inspection globally, you require the appropriate authorizations.

       3.      Assign a name for the inspection.

       4.      Choose Create.

The system will then:

¡        Automatically assign a version number

¡        Propose a deletion date when the inspection should be deleted.

       5.      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 pushbutton – whether it is a local or a global set of objects.

       6.      Enter a check variant.

If you specify a check variant, you can decide – using the appropriate pushbutton – whether it is a local or a global check variant.

       7.      Save your entries.

       8.      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.

                             a.      To execute immediately on the local server, choose This graphic is explained in the accompanying textExecute.

                             b.      If you wish to execute the inspection in parallel on several application servers, choose This graphic is explained in the accompanying text.

The system shows a selection screen where you can decide the following:

                                                  i.       The server group on which the inspection is to run.

                                                ii.       Whether the inspection is to run in the background.

                                               iii.        

       9.      Choose Execute or Execute...

The system performs the inspection run.

   10.      Choose This graphic is explained in the accompanying textResults.

The system displays a results tree.

                            a.      To see the individual results, click the appropriate node of the results tree.

                            b.      To get details of the individual results, choose Information.

 

Creating and Executing an ad hoc Inspection

...

       1.      Call the Code Inspector using the transaction code SCI or choose the path Test à Code Inspector in the SAP menu.

       2.      Choose Create or Change without specifying a name.

If you enter a name and choose Create, the inspection and its result will be stored (see recurrent inspection.).

       3.      Select the objects to be checked.

To do this, you can specify a predefined set of objects, a transport request, or a single object. Remember that the set of objects or the transport request may only contain up to 50 single objects.

       4.      Enter a check variant.

If you specify a check variant, you can decide – using the appropriate pushbutton – whether it is a local or a global check variant.

       5.      In addition to a predefined check variant, you can also choose single checks from the displayed tree.

       6.      Choose Execute.

The system executes the check on the local application server and automatically displays the results.

This graphic is explained in the accompanying text The results are not stored. If you go to another screen, the results will be lost.

However, you have the option of changing the inspection and executing it again using the repeat function

 

 

 

 

End of Content Area