![download sap gui 7.40 for windows download sap gui 7.40 for windows](https://www.stechies.com/userfiles/sap-gui-installation/5-sap-gui-core-760.jpg)
The key is to create your message server entries in your %APPDATA%\SAP\Common\ SAPUILandscapeGlobal.xml file. Needless to say I would say there is some sort of bug going on here, but I did find a way to get these working. The SID and message server host would disappear from the logon pad entry and if I looked at the details I'd get an error " Message server has been changed and no group/server is available" SM04, which would generate a messageĮrror parsing SAP GUI command line ' /FULLMENU SNC_PARTNERNAME="p." SNC_QOP=0 /UPDOWNLOAD_CP=0 /SplashScreeOff /Theme=corbu /FontSize=100 /AccMode=0 /Rtl=0'Īnd then odd things started happening with the associate SAP GUI logon pad entry. So i choose to setup a user defined entry, and once connected to the backend, tried to start a GUI transaction, eg. The best summary of the behavior i can give is that the newly defined system would randomly disappear from the list of systems to create a logon entry for When setting up a connection to a new system in the logon pad (New Entry -> User Defined -> Connection Type: Group/Server Selection) you'll need to include the port # now ( :) which Andreas mentions in this threadĪll was well until i tried creating NWBC logon entry. In our environment we rely on message server logon load balancing for our SAP GUI connections. Issues with Message Server Logon Load Balancing This all seemed to work great when I installed the new front end tools, but I ran into issues as soon as I started trying to setup new system connections. And if you had a previous version of SAP GUI installed, your ini files and etc/services relevant enteries were migrated to these new files the first time you launch the logon pad. These new files (in %APPDATA%\SAP\Common\) are SAPUILandscapeGlobal.xml and SAPUILandscape.xml. The new NWBC 5.0 and SAP GUI 7.40 when installed together leverage a new common set of XML files for managing connection entries. I simply wanted to check if anyone else has encountered these errors before. The latest notes have been implemented, but still no success. And it is erratic, sometimes, I can execute the script button actions after a couple of clicks, sometimes no amount of clicks can get this resolved. This error was not occurring when I tested, but now, it is occurring for every script button in the flavor. Script errors (Step "*" of executed script failed) - This is another error that has me stumped.Or if I wrap certain standard buttons in script buttons (the only script step is clicking the standard buttons), and click the script buttons, nothing happens, no script errors, nor do the actions performed by the wrapped standard buttons (such as Save, Add Item, Remove Item etc.) get executed. Screen buttons not functioning - Sometimes, screen buttons (for example, Header and Item Details Expand, Collapse buttons do not work).I have been noticing two inconsistent errors lately, We are using SAP Screen Personas 2.0 SP02. I have been working on creating a flavor on transaction ME22N. I'm probably doing something stupid but I've been at this for hours and I've turned it around every way i can think of. see screen shots for more details and the scripts in context.Īny insights much appreciated. I cannot get my personas validation script to work in this context - If I use it directly it's fine but not when it's called from a parent script. So I split the script up: SAP validation, Personas Validation & and then Main Script (to do the work) - it was already split into two anyway but now it's three. If the user didn't enter but instead just keyed info in and then [pressed the script button the SAP validation was getting missed until later in the process (too late). The SAP validation didn't kick until I 'entered' the field that I wanted to validate. I then realised that I had to cater for some standard on-screen SAP validation as well. In short I had a script that was doing some basic personas validation (is this field empty for instance) which worked fine. I've attached two screen shots that I hope explain the problem fully but if unsure please ask for a further clarification if you think you can help.