About SAP WinGUI Automation

Enabling SAP WinGUI API scripting allows you to create reliable automations for the SAP WinGUI. Studio and Robots require SAP WinGUI scripting to be enabled on the local machine as well as on the server side. Before you can create your first automation projects for SAP, you need to go over the configuration steps.

UI elements in SAP are known as controls, and you might need a particular approach or activity to detect and use them. Find out more about supported SAP elements.

The following versions of SAP WinGUI are supported for Windows 7 and Windows 10, for both architecture types (32-bit and 64-bit). SAP Logon and SAP Logon Pad are supported on all versions.

All available themes (such as Quartz, Belize, Blue Crystal, or Corbu) can be used for SAP automation.

The following activities are specifically tailored for SAP automation:

All SAP WinGUI activities above mentioned are supported and work with Object Repository.

Wildcards and Regular expressions can be used inside selectors generated for SAP WinGUI elements.

In case SAP WinGUI API scripting is not activated or not allowed in your organization, you can interact with the SAP WinGUI interface with help of Computer Vision activities.

When SAP WinGUI cannot be automated through SAP API Scripting due to misconfiguration or incomplete configuration, the below error message is displayed:

Please follow the configuration steps to verify and to correct the settings.

The Enforce hard timeout setting can be found in Project Settings > UI Automation Classic > SAP. If the setting is set to True, the Robot terminates the SAP activity execution and it throws an error after the timeout specified in the activity target. You can catch and handle the error message in a Try Catch activity. By default, the setting is set to False.

This setting is useful in cases when you might want to end a long running SAP activity, or when SAP becomes stuck or unresponsive, or network or connection issues arise.