Known issues for SAP

This section describes troubleshooting and limitations for SAP GUI and SAP Web protocols.

General SAP GUI limitations

  • VuGen does not support business processes that invoke Microsoft Office module controls, nor those that require the use of GuiXT. You can disable GuiXT from the SAP GUI for Windows client Options menu.
  • If a business process in SAP GUI includes selecting an item from a combo-list, the business process may not run properly in LoadRunner Professional.

    Workaround: Add the path of the SAP GUI installation folder to the Windows PATH environment variable.

  • When replaying a script on Windows 10 or Windows 2016, if a business process in SAP GUI (7.30, 7.40, 7.50) includes accessing a link, the business process may not run properly in LoadRunner Professional. This error is generated by SAP.


    1. Add the path of the SAP GUI installation folder (for example, C:\Program Files (x86)\SAP\FrontEnd\SAPgui) to the Windows PATH environment variable, and restart the machine.
    2. Navigate to the above SAP GUI installation folder (...\SAPgui). Copy the guirfc.dll and paste into the C:\Windows\SysWOW64 folder.
    3. Close SAP GUI and check that the SAPLogon application is not running.
  • Recording is not supported for the SAP GUI Security dialog box.
  • Recording is not supported for standard Windows dialog boxes (for example Save or Open) which are opened from the SAP GUI client.

  • If you encounter a warning during SAP GUI recording: "Sizing conflicts exist on the screen…" it may affect replay.

    Workaround: Disable the warning in the SAP GUI application:

    1. Click the right-most button on the SAP GUI toolbar (or click Alt+F2) to open the Customize Local Layout screen.
    2. Select the SAP Internal sub-menu.
    3. Clear the Enable dialog box for screen size check box.

Back to top

Recording issues

You may encounter the following known issues when recording SAP scripts.

Recording SAP GUI controls

Some SAP GUI controls are supported only in their menu or toolbar contexts. Try performing the problematic task using a different means, for example, through a menu option, context menu, or toolbar.

Recording SAP objects

Recording is not available for objects not supported by SAP GUI Scripting. See your recording log for information about those objects.

Empty list of server names in the recording options

In the Auto Logon node of the recording options, if the list of server names is empty, copy the saplogon.ini file from %APPDATA%\SAP\Common, where %APPDATA% stands for the environment variable specifying the Application Data folder located directly below the user profile folder. Paste the file to the %WINDIR% folder (C:\Windows).

In SAP GUI 7.60 or later, the saplogon.ini file is no longer automatically generated, but you can still generate the file manually, to populate the server names list. VuGen does not support XML landscapes.

Use of the search bar is not recorded in SAP GUI script

When recording an SAP GUI script, if you use the SAP search bar when you are not logged into SAP, the use of the search bar is not recorded in the script.

Workaround: Log in to SAP before using the search bar.

Back to top

Replay issues

You may encounter the following known issues when replaying SAP scripts.

Replay failure

When replaying SAP GUI and SAP Web Vuser scripts, the remote agent must be running in process mode, not service mode. To check the current mode, move your mouse over the agent's icon in the Windows task bar area, and read the description. If the description reads Load Testing Agent Service, it is running as a service.

Restart the agent in process mode. For details, see LoadRunner Agent processes in the LoadRunner Professional Help Center.

Error popup messages

Certain SAP applications store the last layout for each user (such as which frames are visible or hidden). If the stored layout was changed since the script was recorded, this may cause replay problems. For example, in the ME52N transaction, the Document overview Off/On button will change the number of visible frames.

If this occurs:

  1. Navigate the transaction to the same point as it was during recording, before starting replay. You can use the Snapshot viewer to see the layout in which it was recorded.

  2. Add statements to the script that bring the transaction to the desired layout during replay. For example, if an optional frame interferes with your replay, insert a verification function that checks if the frame is open. If it is open, click a button to close it. For verification examples, see Enhance SAP GUI scripts.

Failed logon or connection causes replay to abort

If a logon or connection in a script fails, the script replay is aborted. You can allow the script replay to continue despite a failed logon or connection by enabling the following setting in the runtime settings: SAPGUI > General > Advanced > Disable abort on logon/connection failure.

Replay fails due to SAP GUI client failure

If the SAP GUI client crashes during script replay, it can be relaunched automatically, to enable the continued replay of any remaining iterations in the script. For details, see Relaunch SAP client on crash.

Back to top

Single sign-on mechanism when running a script on a remote machine

VuGen does not support the single sign-on connection mechanism. In your SAP GUI client, open the Advanced Options and clear the Enable Secure Network Communication feature. Note that you must re-record the script after you modify the Connection preferences.

Back to top

Additional SAP resources

Refer to the SAP website, and to the SAP Notes on the website, including the following:

  • Note #480149: Profile parameter for user scripting on the front end.

  • Note #587202: Drag =; Drop is a known limitation of the SAP GUI interface.

Back to top

See also: