Search for anything

Enabling Scripts for SAP

Last Updated June 9, 2026
Share Article Copy link to clipboard

WalkMe Products

WalkMe Digital Adoption

Brief Overview

WalkMe Desktop uses SAP scripts to access and play guidance content on the SAP environment.

These scripts need to be enabled from the client-side and from the server-side in order for WalkMe to work.

How to Check if Scripts are Enabled

  1. Hover over the SAP GUI Scripting icon
  2. If the scripts are not running, a pop-up message will appear:
  3. If the scripts are disabled, the pop-up message will say:
  4. If the scripts are disabled on the client side, the pop-up message will say:
  5. If you don't see any of the icons, click the Triangle icon to expand the icons bar

Note

Not all SAP Themes display the icons bar

Enabling Scripts on the Client Side

Scripts need to be enabled on the client-side (end user). When deploying, this can be done by the SAP admin.

To access the menu:

  1. Click the Settings icon in the top right corner
  2. Click Options...

To enable scripts:

  1. Select Scripting under the Accessibility & scripting folder
  2. Tick Enable scripting and Show native Microsoft Windows dialogs
  3. Click Apply

Learn more about enabling scripts here.

Enabling SAP GUI Scripting on the Server Side

Enable SAP GUI scripting on each SAP server instance you plan to use.

  1. Launch saplogon.exe, sign in to your SAP server using your credentials
    1. The SAP Easy Access window opens
  2. Run transaction RZ11:
  3. Specify the parameter name sapgui/user_scripting and press Enter on the keyboard or click Display

  4. In the Display Profile Parameter Attributes window, press the Change Value button on the toolbar and set the New value of sapgui/user_scripting to TRUE

  5. Save the changes

  6. Repeat Steps 3-4, with a FALSE value for the following parameters:

    1. sapgui/user_scripting_force_notification

    2. sapgui/user_scripting_set_readonly

    3. sapgui/user_scripting_disable_recording 

  7. Sign off and back on again to see the change into effect, as it does not apply to sessions that are currently running.
Note:

The status bar message “Parameter name is unknown” refers to the fact that the sapgui/user_scripting parameter cannot be changed using this transaction because a SAP server package is missing. Install the missing package, and try again.

Additional Steps for Restricted Scripting Environments

Relevant for customers using WalkMe Menu version 4.1.0 or higher

Customers who have restricted scripting privileges but still want to use SAP GUI SWT Automation need to follow these additional configuration steps. These should be applied in addition to the standard Client-side and Server-side enablement steps described earlier in this guide.

Client-Side (in addition to standard client steps)

Add the following registry key to allow SAP scripting execution per user account:

64-bit Windows (32-bit SAP GUI):

HKLM\SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Security\ScriptingPerUserAccountExecute = 1

32-bit Windows:

HKLM\SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Security\ScriptingPerUserAccountExecute = 1

Server-Side (in addition to standard server steps)

Set the following SAP profile parameters for transaction RZ11:

sapgui/user_scripting = TRUE
sapgui/user_scripting_set_readonly = TRUE
sapgui/user_scripting_per_user = TRUE

Result

  • Users with the S_SCR:16 role will have full scripting access and will be able to run SWT Automation

  • All other users will remain read-only, ensuring controlled and secure use of scripting features

Support

How to identify that scripting isn't installed

When you try to capture and get the following message a scripting support needs to be installed, contact your IT department to request installation.

Technical Notes

SAP GUI 8.00 Patches 5–10 — SAP Scripting stability notice

A known stability issue affects SAP GUI 8.00 at Patch levels 5–10 for automations that rely on SAP Scripting. While first identified at Patch 5, our validation confirms the issue persists through Patch 10.

WalkMe leverages SAP Scripting, the standard automation interface provided by SAP. The instability originates within SAP GUI's patch behavior, and is unrelated to WalkMe content or configuration.

Observed impact

Environments running these patch levels may experience:

  • Occasional system instability or freezes that affect the user experience
  • Inconsistent behavior in automations and scripting-based processes

These symptoms are consistent with known SAP Scripting behavior under the affected patch versions.

Recommendation

To ensure automation reliability and a stable user experience, we recommend upgrading to SAP GUI 8.00 Patch 14 or higher.

Reference: SAP Community discussion

Was this article helpful?

Yes No
Yes
No
Thanks for your feedback!

WalkMe Products

WalkMe Digital Adoption

Related Articles

Be part of something bigger.

Engage with peers, ask questions, share ideas

Ask the Community
×