Problem when using SAPGui.exe (rather than SAPLogon.exe)

[Former Member]

Hello all. I have been working on a program that interfaces with the SAPGui through the scripting interface for some time now. After some initial difficulties we have had success getting the information that we need through the API. However, today we have hit a problem that I fear we may not be able to overcome.

We have a need to run the SAPGui without the Logon window. So I have written a command line to connect directly to the SAPGui.exe, and turned off the SAPLogin window in the registry.

However, I have discovered that when I launch SAP via this method, the information I need in the Running Object Table (ROT) in order to establish a connection to the Scripting API is not present.

When using SAPLogon, an object named SAPGUI is present in the ROT. This object is an SapGuiAuto, and I can call GetScriptingEngine on this object and get a GuiApplication object.

When not using SAPLOgon, the object in the the ROT is named SAPFront, and it is apparently a different type of object as it does not allow me to call GetScriptingEngine.

Does anyone have any idea what type of interface/object is put into the Running Object Table when the SAPGui.exe is launched directly, rather than via SAPLogon (or SAPLgpad)?

[former_member204677]

Hello Jared,

SAP GUI scripting only works with a running saplogon.exe. sapgui.exe and scripting is unfortunately not supported.

Kind regards,

Martin