SAP Automation – Unable to Spy SAP Elements (Server Scripting / Runtime Attachment Issue)

Help Studio
,
1

Hi,

I am setting up SAP automation using UiPath Studio 2025 and facing an issue where UiPath is unable to identify individual SAP UI elements. Only the main SAP window is detected, and spying on fields/buttons is not possible.

Below are the checks I have already completed:

:white_check_mark: SAP Client Side

  • SAP GUI scripting is enabled locally
    (SAP GUI → Alt+F12 → Options → Accessibility & Scripting → Scripting → Enable scripting)

:cross_mark: SAP Server Side

  • When executing transaction /nSCDO, I receive:
    “You are not authorized to use transaction SCDO”
    which indicates SAP server-side scripting is not authorized for the Bot user ID.

:cross_mark: UiPath Runtime Behavior

  • UiPath cannot attach to the SAP GUI runtime.
  • Only the SAP application window is detected; internal controls are not identifiable.

:white_check_mark: UiPath Studio Side

  • SAP activities are visible in Studio.
  • UiPath Studio version: 2025

:red_question_mark: Questions

  1. Is the /nSCDO authorization mandatory for UiPath SAP automation to function?
  2. Are there any additional SAP-side settings required beyond server-side scripting and SCDO authorization?
  3. Once SAP server scripting is enabled, should SAP appear under UiPath → Tools → UiPath Extensions for runtime attachment?

Any guidance from the community would be greatly appreciated.

Thanks in advance.

2

/nSCDO authorization is not necessary, but make sure scripting is enabled at both server and client side.

No sap will not appear in UiPath extensions.

Refer to these links for more info
Enabling SAP GUI Scripting

Activities - Configuration Steps

3

Hi @arivazhagan_mathivan

Welcome to the Community

SAP GUI scripting must be enabled on both client and server side for UiPath SAP automation.
Local SAP GUI settings alone are not sufficient.
The /nSCDO transaction itself is not mandatory, but lack of access indicates server-side scripting is not enabled or the user lacks authorization.
Once SAP Basis enables parameter sapgui/user_scripting = TRUE and assigns scripting permissions to the bot user, UiPath will be able to attach to SAP runtime and identify individual UI elements.
SAP does not appear under UiPath Extensions, as it is a native integration.

Hope it’s helps

Cheers

4

Hi @arivazhagan_mathivan

  • Yes, SCDO (server-side SAP GUI scripting) is required.
    If your bot user can’t access /nSCDO, SAP GUI scripting is not enabled for that user, and UiPath will only detect the main SAP window.
  • Local SAP scripting alone is not sufficient.
    The SAP Basis team must enable SAP GUI scripting on the server and allow it for the bot user.
  • There are no extra UiPath extensions for SAP.
    SAP will not appear under UiPath → Extensions. That’s normal.

Once server-side scripting is enabled and the user is allowed, UiPath will immediately be able to spy SAP fields and buttons.