Troubleshooting and Limitations for SAP

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

General SAP GUI limitations

  • For LoadRunner users: If a business process in SAP GUI includes selecting an item from a Combo-list, the business process may not run properly in LoadRunner.

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

  • For LoadRunner users: 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 versions 12.55 and higher. This error is generated by SAP.

    Workaround:

    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

I was able to record a script, but why does replay fail?

In LoadRunner, make sure that the LoadRunner Remote Agent is running in Process mode. Service mode is not supported. For more information, see Run SAP GUI Scripts from the Controller.

Back to top

Why were certain SAP GUI controls not recorded?

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

Back to top

What is the meaning of the error popup messages that are issued when I try to run the script?

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.

Back to top

Can I use the single sign-on mechanism when running a script on a remote machine?

No, 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

Can VuGen record all SAP objects?

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

Back to top

Are all business processes supported?

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.

Back to top

When I go to the Auto Logon node of the Recording Options, why is the list of server names empty?

If this error occurs, 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).

Back to top

See also: