Show TOC

Procedure documentationMaintaining SAP Attributes on the Attributes Tab Page Locate this document in the navigation structure


You maintain the SAP attributes of a test script or a test configuration (either eCATT or created with a third-party test tool). You edit, for example, the application component or system data container.

If you have chosen to create the test script with a third party test tool, on the Test Tool Attributes tab page you can see the corresponding test tool attributes. For more information, see Configuring Test Tool Attributes.


You create or maintain a test script or a test configuration. For more information, see


  1. Choose the Attributes tab page.

    If you have created the test script with a third party test tool, the Attributes tab page is divided into two sub-pages, SAP Attributes and Test Tool Attributes.

  2. Optional: To display the attributes of a test script created with a third party test tool, you can choose the Test Tool Attributes tab page.

    For more information about the attributes of test tools, see Configuring Test Tool Attributes.

  3. To edit SAP attributes of a test configuration or a test script, do the following:

    1. Choose the SAP Attributes tab page.

    2. If you have created a test configuration, to edit the attributes of the test configuration or of the test script, select the respective radio button. For more information, see Creating a Test Configuration in the Test Composition Environment.

    3. Specify the Application Component

      Note Note

      In case the Test Composition Environment was called from transaction SOLAR02, the value defaults to the application component derived from the executable object, if any.

      End of the note.
    4. Enter the following data describing the test script or test configuration.

      • Person Responsible: By default, the current user is proposed as the person responsible for the test case.

      • System data container: You define the system landscape in which the test script or test configuration is to be executed. In this way, you can execute the same test case in different physical systems. For more information, see Creating a System Data Container in the Test Automation Framework.

        By default the system data container corresponding to the project or solution of the SAP Solution Manager context is proposed, if any.

      • Target component: If you create an eCATT script, you assign a target component based on the selected system data container components, if any.

        This target component is accessed during script development for recording, and for execution within the eCATT script development environment.

        To check whether you can log on to the specified target system, whether a target component is available and whether an exact connection can be derived based on the system role, choose Logon.

    5. Assign the executable which corresponds to a test script.

      If the corresponding interface features are implemented by the third-party test tool, you must not specify it in the third-party test tool again. For eCATT, you have to specify it again.

      To do so, define the following:

      • Executable Type, for example Transaction. or CRM WebClient Application.

      • Executable

        • SAP GUI executable: You select an executable depending on the SAP Solution Manager Context you have defined.

          The interfaces of transactions or function modules are imported automatically from the SAP Solution Manager system landscape, if a system data container was assigned to the test case and if an SAP Solution Manager project or solution and a system role were assigned to the test case.

        • CRM Web UI executable: Specify the SAP role and logical link according to the following pattern: saprole=<ROLE>&crm-logical-link=<logical link>.

          Example Example


          End of the example.
    6. Optional: Define the eCATT test case attributes:

      • Status: The status is set to active is by default. Only active scripts are included in automatic tests. If you do not want the test script to be executed (it is not yet finished, or you are modifying it, for example), set the status to inactive.

      • Release Status: To find an eCATT test case via the F4 help, you can assign a release status. The release status is for information purposes only.

      • Time Required: Enter the time that the test configuration is supposed to take.

      • Priority: If you assign a weighting to the test status evaluation, test cases of different priority can have different weight. For example if priority High is attributed with a weight of 10 and priority Low with a weight 1, during status evaluation a high priority test case is counted as 10. If it is in error, the status evaluation displays 10 test cases with errors.