Show TOC

Procedure documentationCreating or Editing a Check Step


You want to create a check step to check whether one or more of the following object types are used:

  • Objects that are recorded by the workload statistics:

    • Transactions

    • Reports

    • Function modules (RFCs)

    • Business Add-In (BAdI)

  • Objects that are recorded by usage & procedure logging (UPL)

    • Reports

    • Function modules (RFCs)

    • Methods

  • Database tables

    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 occur in fields of a database table

    • How often certain values occur in fields of a database table

    You can also create descriptive SQL check steps. These checks do not return a value, they list the contents of the selected database table.

  • Objects covered by the E2E Diagnosis:

    • Java Web Dynpro applications

    • Java Web Dynpro components

    • Java Web services

    • Servlets

    • iViews


You have called the Solution Documentation Assistant.


  • To create a check step, do the following:

    1. Under Common Tasks choose Create Check Step.

    2. Under Rule Database choose Create.

      You branch to the Create Check Step view.

  • To change the attributes of a check step, do the following:

    1. Under Rule Database, select the check step.

    2. Choose Edit.

Defining a Check Step

Define the following attributes of the check step:

  1. Check Step Type: Select transaction or BAdI, for example.

  2. Default Name: To change the name assigned by the system, remove the checkmark from the Default Name check box.

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

  4. 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 Note

    This RFC destination is only needed to edit the check step in the Rule Database, for example to check a test system. This RFC destination 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. (For more information, see Editing Logical Components.)

    End of the note.
  5. Object details. Enter the object details, depending on the check step type, and the name of the object whose type you have specified.

  6. Additional attributes. To be able to find the check step more easily later, you can assign a product or a keyword to it under Attributes. This is particularly useful for SQL check steps which are subject to an improvement process.

Checking Definitions

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

End of the note.

Choose Create to create the check step.


The check step is added to the check step list of the rule database.