📎 This article includes 1 downloadable practice file ↓

Enable GUI Script Recording – SAP

This document describes how you can turn on GUI Script Recording. To use GUI Script Recording with Winshuttle Transaction, the scripting parameter must be set in RZ11 and GUI scripting must be enabled in the SAP GUI. Typically, Basis has to enable the parameter setting and users will have to enable scripting in their SAP GUI.

Enable the RZ11 parameter

1. In SAP GUI, start transaction RZ11.

2. Under Param. Name, enter sapgui/user_scripting.

   

3. Click Change Value.

   

4. In the New value box, enter TRUE, and then click the Save button.

   

   Scripting is enabled.

Enable scripting in SAP GUI

1. Click Customize Local Layout, and then click Options.

   

2. Click Accessibility & Scripting, and then click Scripting.

   

3. Check the Enable scripting box.

   

4. Click OK.

Before you start: who controls scripting

SAP GUI Scripting has two switches, and both must be on:

1. Server side — your SAP Basis team controls the profile parameter sapgui/user_scripting. If it is off, the scripting menu items stay greyed out no matter what you do on your PC. Many companies enable it only in development or quality systems, or only for certain users.
2. Client side — on your PC, in SAP Logon: Options → Accessibility & Scripting → Scripting, tick Enable scripting. The two warning boxes (“notify when a script attaches”, “notify when a script opens a connection”) are worth leaving on at first, so you always know when automation is running.

Recording your first script

1. Log in, then open Customise Local Layout (Alt+F12) → Script Recording and Playback.
2. Choose where to save the .vbs file, press the red record button, and do the task slowly — for example, open SE16N, enter a table, set a filter and export.
3. Stop recording. Open the .vbs file in Notepad: every click and field entry is now a line of code such as session.findById("wnd[0]/usr/ctxtGD-TAB").text = "MARA".

Those lines can run from Excel VBA with small changes, which is how most SAP-to-Excel automations start — see automating an SAP export into Excel.

When scripting is disabled for you

That is usually a deliberate security decision. Ask for access to a test system, or use standard exports and saved ALV layouts plus Power Query to reduce manual work without scripting.