Creating Check Steps 
You would like to create a check step to check whether one or more of the following object types are used actively:
Transaction
Report
Business Add-In (BAdI)
Database table
For check steps for database tables you can create subtypes of SQL check steps that check the following cases:
Whether a certain database table is present
Whether a certain field of a database table is present
Whether certain values in fields of a database table occur
How often certain values in fields of a database table occur
You can also create descriptive SQL check steps. These checks do not return a value, instead they display the content of the selected database table in the form of a results list.
You have called the Solution Documentation Assistant.
Under Common Tasks choose Create Check Step.
Under Rule Database choose Create.
You branch to the Create Check Step view.
Define the following attributes of the check step:
Check Step Type: Select transaction or BAdI, for example.
Default Name: To change the name assigned by the system, remove the checkmark from the Default Name check box.
Name: Enter the name of the check step. The field is only active if you have removed the checkmark for the Default Name check box.
RFC Destination: You can enter the RFC destination of a system in which the object is used. Click on the input help next to the input field to open a list of proposals and select an entry.
Note
This RFC connection is only needed to edit the check step in the Rule Database, for example to check a test system. This RFC connection is not relevant for the analysis, as a system is defined with the Logical Component for the analysis. This is determined when assigning a check step to a check item in an analysis project.
Depending on the type of check step, enter the object details and the name of the object whose type you have specified beforehand.
To check whether the definition of the check step is valid, choose Check.
If the definition can be used and a description of the referenced object can be found, the description is displayed.
If the check uncovers problems in the definition, this can have the following causes:
The object cannot be found in the specified RFC destination.
There is already a check step in the rule database that references the specified object.
Note
Check steps are saved in the rule database even if the RFC destination is incorrect or not specified (as it is not relevant for analyses).
Choose Save to create the check step.
The check step is created.
The check step is added to the check step list of the rule database.