PureBasic Forums - English

SAP session control pad is a small utility to watch, navigate and control all SAP sessions. It is programmed in PureBasic. It use the SAP GUI Scripting to communicate with a SAP system. You see all SAP sessions clearly arranged in a tree. Also you can direct execute a transaction or a script to the selected session. The available transaction codes are an easy and individual customizing in a preference file. So you can organize your favorite transaction codes and scripts in a tree as you want - one time for all application servers.
With a simple click in the session tree you can choose the SAP session you want and it is direct on top of all the open windows. If you click the right mouse button, it opens a popup menu and you can close the session or the connection, or you can resize the session window or or or ... And with a simple double click in the transaction tree you send a transaction code or a script to the selected session. With the possibilities of the toolbar you can e.g. minimze all sessions with one single click, or restore it. SAP session control pad helps you in the jungle of sessions and connections. It is free.

You find the SAP session control pad here.

Cheers
Stefan



Meet me at Xing

But is SAP GUI scripting reliable? I have set up a few scripts, or macros, to automate things, and
they fail 50% of the time due to som id not found..

Hello utopiomania,
there are different ways to execute a SAP GUI script. The first is to double click on the script file in your shell e.g. Windows Explorer, this does not work very reliably because the script is always running in application.connection(0).session(0). The second is to execute the script via drag and drop, this works very good. And the third and last method is to execute the script via the SAP GUI script recorder, this also works well. I work with the SAP session control pad since a half year in a very complex development environment with more than 50 SAP development systems and it works to my satisfaction. I use SAP GUI scripting much longer for a lot of things, especially for repititive test scenarios. Against this background, I can not confirm an unreliability.
Cheers
Stefan

And the third and last method is to execute the script via the SAP GUI script recorder, this also works well.

Not for me, it fails 50% of the time, and I regret posting a tip about this at work.. They think I'm a
geek that should have better things to do than experiment with the 'Seriously Annoying Program' interface..