SAP GUI Automation – Limitations, Workarounds, Tips & Tricks

Issue

Solution

Drag and Drop is not recorded

This is an SAP GUI scripting limitation (see SAP Note 587202). If applicable, operate in a different way (without drag-and-drop); please use Copy and Paste instead.

Activities performed within F4 or F1 are not captured 

In SAP GUI -

Go to Help 🡪 Settings 🡪 F4 Help 🡪 select ‘Dialog (modal).’

Go to Help 🡪 Settings 🡪 F1 Help 🡪 select ‘In Modal Dialog Box.’

Automatic sections with TCODE are not created in the script

Panaya automatically creates a new section in the script only when the TCODE entered is recorded. If the recording is launched from an open session directly from within the transaction, no section will be created. You can always create the section manually in the ScriptBuilder.

ScriptBuilder does not automatically capture the SAP system message

Success messages are automatically captured into the script.

To add other system messages from the status bar, you can use the ‘Capture screen element’ command.

Issue in capturing the screen element of a GuiBarChart Object

Use the “Tabular Display” mode for the table. More information about the impact of SAP GUI visual display on automation.

Sometimes parts of nested objects cannot be captured (for example, certain rows within a Grid View)

It is possible to capture a different row and modify the row number in the instruction before playback.

The Login screen is not recorded

If you need to record the SAP login screen, go to ScriptBuilder settings > SAP settings and use the ‘Interactive mode’ to record and play the SAP login with the username and password.

Issue

Solution

Yellow outline boxes are missing in the evidence

This is a known SAP limitation when the display scaling is not set to 100%. You need to configure the Windows display scaling to 100% before running ScriptBuilder automations using the Panaya Agent against SAP GUI.
Learn more.

Some actions in the grids are missing in the screenshots

This is a known limitation. The screenshot mechanism relies on the focus event. For fields that do not trigger a server call (such as text fields and radio buttons), a screenshot is captured and later attached to the relevant instruction only when the server call occurs.

There is a limitation in grids: moving between cells within the same grid does not trigger a new focus event. As a result, when filling multiple cells consecutively, a screenshot is not captured for each cell.

The issue occurs only in a grid, not in a regular table.

Cached context menus don’t appear in screenshots.

This is an SAP limitation documented here.

Only context menus of controls of type GuiShell are supported.

Issue

Solution

Playback of password fields in SAP GUI doesn’t work (e.g., SU01 Logon data)

After recording, the value must be manually updated to the correct password.

Issue

Solution

SAP Connection failed in ScriptBuilder

Read this article.

SAP session is not recorded

Panaya records only the first session that is opened. If a new session is opened by the user (/o) or automatically by SAP, it’s not being recorded.

Connecting to SAP GUI with (SNC) SSO

If you work with ScriptBuilder to build your SAP GUI scripts, and you have an SSO connection to SAP GUI, ScriptBuilder will automatically connect to SAP GUI with SSO, even if you configure the SAP Connection instruction to use another user.

When working with a remote agent, the machine running the agent should not be configured with SSO, so the agent runs the script and connects as the user specified in the script's connection instruction.

A second SAP session opened shows “Scripting is running.”

When a new session is opened during an active recording, the new session may show “Scripting is running”. To avoid this, you must stop the recording before opening the new session.

SAP logon doesn’t close at the end of the execution

You can configure ScriptBuilder to close SAP Logon at the end of the execution by enabling this setting. This helps maintain clean SAP sessions and can improve troubleshooting by preventing unnecessary active SAP Logon instances. See here.