Enabling SAP GUI Scripting for Automation – ACCELQ

To allow ACCELQ (or any automation tool) to interact with the SAP WinGUI protocol, scripting must be enabled at both the Server-side and the Client-side. This guide outlines the mandatory configurations required to establish a successful automation connection.

1. Server-Side Configuration

Requirement: This usually requires SAP Basis authorization.

Server-side scripting must be turned on to allow the SAP application server to communicate with external automation scripts.

1.1 Mandatory Parameter

Log in to the SAP system.
Navigate to Transaction RZ11.
In the "Param. Name" field, enter: sapgui/user_scripting.
Click Display.
Click Change Value and set the "New Value" to TRUE.
Save the changes.

1.2 Complementary Security Parameters

To ensure a smooth automation experience without restrictive pop-ups or security blocks, review the following parameters in RZ11:

Parameter	Recommended Value	Description
`sapgui/user_scripting_disable_recording`	FALSE	Ensures that recording and playback actions are not blocked.
`sapgui/user_scripting_force_notification`	FALSE	Highly Recommended. Disables the SAP notification that appears every time a script attaches to the GUI.
`sapgui/user_scripting_set_readonly`	FALSE	Ensures the automation has write-access to fields (entry) rather than view-only access.

2. Client-Side Configuration

Requirement: Performed on the machine where the ACCELQ Local Agent and SAP GUI are installed.

Even if the server allows scripting, the local SAP GUI client must be configured to accept the connection.

2.1 Enable Scripting in SAP Options

Open the SAP Logon pad.
Click the icon in the top-left corner and select Options.
In the tree menu, navigate to: Accessibility & Scripting → Scripting.
Check the box: Enable scripting.

2.2 Automation-Friendly Settings

For unattended automation (where no human is present to click "Allow"), you must uncheck the following security notifications:

Uncheck: "Notify when a script attaches to SAP GUI"
Uncheck: "Notify when a script opens a connection"

Note: Failure to uncheck these will cause the automation to hang indefinitely while waiting for a manual click on the SAP security pop-up.

3. Troubleshooting the Connection

If ACCELQ still cannot detect SAP elements after these changes:

Restart SAP GUI: Changes in the Options menu require a complete restart of all open SAP windows and the Logon pad.
Check Windows Registry: In some locked-down environments, registry keys under HKEY_CURRENT_USER\Software\SAP\SAPGUI Front\SAP Frontend Server\Scripting may override the GUI settings. Ensure UserScripting is set to 1.
Authorization: Ensure your SAP User ID has the authorization object S_SCRP assigned if the system is highly secured.

4. Summary for Basis Teams

When requesting these changes from your Basis team, you can provide this concise summary:

"Please enable SAP GUI Scripting for the [Environment Name] via transaction RZ11. Set sapgui/user_scripting to TRUE and sapgui/user_scripting_force_notification to FALSE to support automated testing with ACCELQ."