Enable support for SAP GUI for Windows

This topic describes the operations you must perform before you use the SAP Solutions Add-in to test SAP GUI for Windows applications.

Make sure that SAP GUI Scripting is installed

When you install your SAP GUI for Windows application, select the SAP GUI Scripting installation option. If you did not select this option when you installed the SAP GUI for Windows application, it is essential that you reinstall it and select this option before setting the other configuration options described in this topic.

SAP provides a range of security mechanisms that enable the administrator to limit the use of SAP GUI Scripting by system, by group, by user, and by scripting functionality. To test SAP GUI for Windows applications, you must ensure that these security mechanisms are not activated. For details on the various security options, see the online SAP GUI Scripting Security Guide at the SAP Service Marketplace.

Back to top

Enable scripting on the SAP application

OpenText Functional Testing communicates directly with the SAP GUI Scripting API and records and runs steps based on the API events sent from the client to the SAP server.

Therefore, to record and run tests and business components on an SAP GUI for Windows application or on an SAP NWBC client running SAP GUI, you must enable scripting on both the server and client sides. By default, scripting is disabled.

To enable scripting on the server side:

  1. Confirm that you have the proper support package and kernel patch levels installed:

    Software Component

    Release

    Support Package

    Kernel Patch Level

    SAP_APPL

    31I

    SAPKH31I96

    Kernel 3.1I level 650

    SAP_APPL

    40B

    SAPKH40B71

    Kernel 4.0B level 903

    SAP_APPL

    45B

    SAPKH45B49

    Kernel 4.5B level 753

    SAP_BASIS

    46B

    SAPKB46B37

    Kernel 4.6D level 948

    SAP_BASIS

    46C

    SAPKB46C29

    Kernel 4.6D level 948

    SAP_BASIS

    46D

    SAPKB46D17

    Kernel 4.6D level 948

    SAP_BASIS

    610

    SAPKB61012

    Kernel 6.10 level 360

    Note: This table shows the minimum required versions and levels. You must have these versions and levels or higher.

    For details, see SAP OSS note # 480149.

  2. Enable scripting on your SAP application.

    1. Enter the Maintain Profile Parameters window of transaction rz11 with administrative permissions.

    2. Set the sapgui/user_scripting parameter to TRUE on the application server.

    3. Set the sapgui/nwbc_scripting parameter to FALSE on the application server.

    For more details, see Enable scripting on the SAP application (server-side).

    To enable scripting for all users, set the parameters on all application servers. To enable scripting for a specific group of users, set the parameters only on application servers with the appropriate access restriction settings.

    3. Note: If you connect to a server on which scripting is disabled, an error message displays when you try to record on your SAP GUI for Windows application.

To enable scripting on the client side:

  1. Make sure the SAP GUI Scripting option is installed. If this option is not installed, reinstall your SAP GUI for Windows application and be sure to select the SAP GUI Scripting checkbox.

  2. Eliminate warning messages on your SAP client.

    By default, you regularly receive two warning messages when using OpenText Functional Testing with an SAP GUI for Windows application:

    • When OpenText Functional Testing connects to the Scripting API, the following warning message is displayed: A script is trying to attach to the GUI.

    • When OpenText Functional Testing opens a new connection using the Scripting API, the following warning message is displayed: A script is opening a connection to system <system_name>.

    We recommend disabling these warning messages in the SAP GUI for Windows application when working with OpenText Functional Testing.

Back to top

Check the connection speed on the SAP server

Confirm that the Low speed connection option is NOT selected for the server to which you are connecting before recording and running GUI tests.

This is because when you log on to SAP using the Low speed connection option to communicate with the server, the SAP server does not send sufficient information for OpenText Functional Testing to properly record and run tests. (OpenText Functional Testing displays an error message if the Low speed connection option is selected.)

For details, see SAP OSS note #587202.

Back to top

Set F1 Help to use the modal dialog box mode

Confirm that the modal dialog box option is selected. This enables OpenText Functional Testing to record the display of F1 Help in your tests. (The F1 Help in your SAP GUI for Windows application can be displayed using either the Performance Assistant or as a modal dialog box.)

Back to top

Set F4 Help to use the dialog display mode

Confirm that your client is set to load F4 Help screens in Dialog mode. (The SAP GUI for Windows application cannot load F4 Help screens in Control mode when using the SAP GUI Scripting API (Enable Scripting option.)

Note: This is a per-user setting. You must set this option on each client that you want to test using the OpenText Functional Testing SAP Solutions Add-in. Alternatively, the SAP system administrator can change the system default for you.

Back to top

Disable recording on the SAP application

Note the following when you disable recording on your SAP application (by setting the sapgui/user_scripting_disable_recording parameter to TRUE):

  • OpenText Functional Testing can run your existing tests on the application.

  • The objects on the application are spied as Standard Windows objects, not SAPGUI objects.

  • If you click the Record button in OpenText Functional Testing, the Record toolbar appears but it does not work.

Back to top