Announcing SAP GUI for Windows 7.40
On behalf of the SAP GUI team, I am delighted to announce that SAP GUI for Windows 7.40 will be released on October 8th. This release offers the following new features:
- SAP Blue Crystal Theme
SAP Blue Crystal is a new visual design theme which succeeds Corbu. It is the standard theme of Fiori applications and has been adapted to the specific needs of SAP GUI. Furthermore, it is fully compatible with the previous themes and comes with a new color palette and icons which are better scalable. The background texture has a stroke pattern in white and light blue with a gradient layer. The picture below shows the new Blue Crystal theme in comparison to the Signature theme which is still the default for SAP GUI for Windows:
- SAP NetWeaver Business Client Integration
As of SAP NetWeaver Business Client (NWBC) 5.0, which is delivered on the SAP GUI DVD, SAP GUI for Windows can be embedded into the NWBC, so that the user has one shell that unifies multiple frontends. One desktop/taskbar icon consolidates NWBC and SAP GUI sessions, tasks, frequently used links etc. in a tabbed view NWBC frame as shown in the picture below.
For the integration, you simply install SAP GUI for Windows 7.40 together with the SAP NetWeaver Business Client (NWBC) 5.0. This has the following advantages:
-
- Easier Configuration: The persisted connection and connection configuration data from SAP GUI for Windows, SAP GUI for Java and NWBC is unified in a modern and easy way:
-
- There are only two configuration files involved and they are stored in the same directory.
- Configuration files can either be stored locally or on a central server or share.
-
- Easier Configuration: The persisted connection and connection configuration data from SAP GUI for Windows, SAP GUI for Java and NWBC is unified in a modern and easy way:
-
-
-
- Deployment options “pull” and “push” are available.
- The configuration files are the same for SAP GUI for Windows, SAP GUI for Java and NWBC.
-
-
This new format is called “SAP UI Landscape”.
-
- Automatic Data Migration: If SAP GUI has been used already, the connection data will be migrated automatically into the SAP UI Landscape format.
- Embedded and Parallel Use of SAP GUI: When SAP GUI for Windows 7.40 is installed together with NWBC, by default, SAP GUI and SAP GUI Shortcuts will be launched through NWBC. However, you have also the possibility to use SAP GUI and NWBC in parallel. To do so, you merely have so select the new component Install SAP GUI Desktop Icon / Shortcuts even though NWBC is installed to install the SAP Logon (Pad) Desktop Icon and to register SAP GUI shortcuts to SAP Logon.
Note: At the moment, these new configuration features are only available when using SAP GUI together with NWBC. However, in the long run, this procedure will become the default for all SAP GUI installation and configuration scenarios.
Thus, with SAP GUI for Windows 7.40 you have the option to either run SAP GUI standalone with the old configuration files (fully compatible to SAP GUI for Windows 7.30) or run SAP GUI embedded into NWBC with the new SAP UI Landscape format.
- Installation Improvement
Registry values can now be set on installation package level, for example, for the following SAP GUI options:
-
- Accessibility
- Path to the SAP GUI branding image
- Path to the Central Configuration File (new and old format)
- SAP GUI Theme
You will find the whole list on the package configuration tab in NWSAPSetup.
- SAP Screenreader Extensions
SAP GUI Screen Reader Extensions (SRX) are now part of the SAP GUI for Windows installation, see note 1139953.
SRX enable the use of SAP GUI together with the screen reader program Jaws for Windows. The Extensions are Jaws-based scripts that make the SAP GUI accessible via the SAP GUI object model.
And finally a few remarks on the supported plattforms as well as on the support and maintenance strategy:
- Windows XP and Windows 2003 Server are not supported.
- Blue Crystal can be used as of Windows 7 (not on Vista and Windows 2008 Server).
- End of support of SAP GUI for Windows 7.30 is on October 31st, 2015 (see note 147519). As of July 15, 2015 the support will already be „limited“.
- SAP GUI for Windows 7.40 is compatible and will be maintained until January 9, 2018.
- We urgently recommend to start planning upgrades to 7.40.
...Cheers!
See u 8th Oct.
That's nice. Hope to see tabbed view not only in NWBC but also in SAP GUI in the future. Even though UI5 is a trend...
Very true, yet if you think about it, probably 99% of the SAP users are still hooked on SAPGUI. And even though UI5 is very cool and is indeed a trend, it will still not replace the classical Dynpro anytime soon. It might be high-tech and user friendly, but at the end of the day, people use SAP for business purposes.
And business users dont deserve a nice looking interface ?
When we have the very people who are meant to be pushing this tech, moving with the times, holding us back with DynPro.
All Hail the battleship grey interface, its worked for 25 years so why change it now. Just because something works doesnt mean you shouldn't try and improve it.
Like it or not the world is evolving and end users arent just your technical specialists anymore. The more people use tech in there daily lives the more those same people will expect a consumer level of interaction, design and usability, in the business applications they use everyday. With comments like yours above you are failing to move with the times and if SAP isn't careful it is completely possible that its competition will move forwards and possibly even surpass us whilst we are standing still and the tech is evolving. (case in point is the WorkDay HR app)
Coming soon - Rise of the Fiorier
I'm afraid you didn't really understand what I said. Of course a Fiori App is much nicer (both from a programming- and a user-perspective), but that's from our perspective (as SAP specialists). In order for an organization to start a big and expensive project like switching the user interface from Dynpro to UI5/Fiori, it needs a proper reason. And from my experience, the majority of end-users are not really excited to learn how to use new apps, especially if they provide the same functionality... It's a paradox 🙂
I apologise for my confusion then. I understand there needs to be a business case when upgrading from DynPro. But I certainly feel like when starting something new we can not and should not be ruling out UI5 as a trend.
I think it is certainly here to stay especially when even outside of SAP circles it is being hailed as a resiliant and useful framework.
And SAP GUI for java?! When?!?!
The delivery is planned for December 2014.
Good Info, Great...To...Hear....
SAP GUI with "Theme Of FIORI"....
Any word on the SAPGUI installation tool with version 7.40? Will there be an upgrade/improvements with that tool?
NWSAPSetup is the same for both SAP GUI for Windows 7.30 and SAP GUI for Windows 7.40. However with 7.40 we have introduced the option to customize SAP GUI configuration options more easily on Package level (see the blog under "Installation Improvement").
Cool. Any plans for tabbed GUI windows for us cavemen who still use SAPGUI and not NWBC?
There are currently no plans to offer "Tabbed Browsing" directly in SAP GUI. However I believe with the joint delivery of SAP GUI for Windows 7.40 and NWBC 5.0 there exist good reasons to try out this combination and benefit from tabbed windows inside NWBC.
The blue chrystal theme looks nice. It's always good to have a fresh look from time to time. I also hope for a tabbed view. Can it be done with NWBC using only SAPGUI tabs?
Wow! Sap Community urges for tabbed view!
Greatest... See u tomorrow!!!!
Where's the download link?
Hi All,
download from here -> SAP GUI FOR WINDOWS 7.40 CORE.
I strongly advise to backup current configuration before upgrade. Folders:
"C:\Users\<system_username>\AppData\Roaming\SAP"
"C:\Users\<system_username>\AppData\Local\SAP"
Also it's better to first install it using e.g. Sandboxie, or other similar sandboxing/virtualization software. Then there's no need to revert back using complicated uninstall/install procedure, or loose your current settings.
It looks like there's to many problems with this relase, but too litle new things. At the moment I suggest to stay at v7.30 for productive work, and if you want then try new version only on virtualized environment.
Also trying to find sime kind of strange workarounds for SAP problems with basics is in this stage only waste of time, as they might not work after SAP decide to "fix" things
I've tried new Blue Crystal Theme. But personally I really don't like new icon set. Lack colors, really hard to recognize meaning, strange shapes. It's not well designed theme from productive and practical point of view. Maybe for ocassional use it's kind of acceptable. So for now I'm sticking with Corbu Theme. But who knows,maybe I'll give it one more shot later.
Also NWBC broke my SAP Logon connections/shortcuts configurations a little bit, and was not able to determine system IDs from previous files of SAP GUI v7.30. Also SAP router is not working. So before update it's advisable to backup your current settings (what we should do on every update I think). Also language is forced to system regional settings, which I don't like much (but maybe I missed some hidden setting ?). I think it needs more work to be done before we can use it on daily basis. Once it'll be fine, tabbed use will be good benefit. Also there's problem with ini file defined as paramter in shortcut. So I think it's best NOT to install NWBC for now! It's buggy. Also I don't understand why on every start NWBC tries to access HTTP. Not reason to do so.
My custom configuration of ABAP code colors from file "C:\Users\<system_username>\AppData\Roaming\SAP\SAP GUI\ABAP Editor\abap_spec.xml" was updated, but ignored my settings
. So I manually edited and set it according to my backup file.
More work and problems with this initial release than profit. It looks like no one even bothered to test basics before release. Buggy.
Many thanks!
Dear Thomas,
for the language settings:
Best regards
Melinda
Hi Melinda,
thank you, I missed this one. Also as I'm able to change language (in sandbox installation anyway), basics still doesn't work. So we can only wait for fixed realease.
Best regards,
Tomas.
@Thomas: I totaly agree to your comments!
Thanks for your hints & tip
Installed new SAPGUI just now.... ì agree to the Tomas comment that Crystal is too lazy for the productive day - by -day work.
Direct connection works , but doen't work any logon group connection .
error :
error parsing SAPGUI command line ' /FULLMENU SANC_PARTNERNAME="" SNC_QOP=-1 /UPDOWNLOAD_CP=2'
i think is related to the particular sapgui invocation of the logon groups :
for example
/M/host.xxx.com/S/sapmsSID/G/GROUP
Stef
Bug in 7.40. It's cant read SYSTEM_ID from saplogon.ini from previous version (and password in shortcut too). And it does not save SYSTEM_ID if write one to connection manually. Waiting Patch level 1.
Counld not agree anymore!
Waiting for hotfix 1 / patch 1.
With systems of Release ECC 6.0 no EHP I and a colleague of mine experienced a bug in the ABAP editor not color highlighting anything (e.g. keywords, comments...). Also especially in these systems the GUI crushed regularly.
Other releases I have checked (EH6 & EH7 with NW 740) worked stable without issues.
Hi Melanie,
"Path to the Central Configuration File (new and old format)"
Where can I find information about the new format?
Just installed SAPGUI 7.40 and noticed that this doesn't work anymore.
Thanks,
Peter
Hi Peter,
Does this info. useful?
Path: C:\Users\your username\AppData\Roaming\SAP\Common
Hi Cind Q,
Thanks, only partially. I can check the new files SAPUILandscapeGlobal.xml and SAPUILandscape.xml, but would be good to know how the "Service uuid" is generated for example.
I also noticed that I have funny syntax highlighting in the ABAP editor, when I use the new ABAP front-end-editor setting. Even when I display SAP standard programs:
I have this error too , any idea to solve it? it's very annoying
I guess wait for patch 1 is the only option (or go back to 7.30).
Update changed file where editor settings are stored -> "C:\Users\<system_username>\AppData\Roaming\SAP\SAP GUI\ABAP Editor\abap_spec.xml". It added few lines, but completely ignored custom settings(color setting etc.). I manually compared and edited it using my backup version. I don't think there's easier solution.
Have the same bug too. We have to wait for Patch 1 or Hotfix 1 I think. Let's see if it's too annoying and I go back before to 7.30 or not.
Agree with you, Alex.
And I've back to 7.30 yet, yesterday. (Wait for Hotfix 1...)
Hello, Peter,
"I can check the new files SAPUILandscapeGlobal.xml and SAPUILandscape.xml, but would be good to know how the "Service uuid" is generated for example."
Let me first explain some background. These configuration files (with SAP UI Landscape Format) are new in SAP GUI 7.40.
The first one "SAPUILandscapeGlobal.xml" contains the migrated connection data from your GUI 7.30 configuration - sapmsg.ini, saproute.ini and the services file, as well as optionally the NWBC Admin connections. The "Global" file was created because you have not configured a server landscape file. Similarly to "ConfigFileOnServer" in SAP GUI 7.30, in the new version you can define "LandscapeFileOnServer" - an HTTP URL (simple, HTTPS is still not supported), Network Share or local Windows Path.
If on first start LandscapeFileOnServer is defined, the "SAPUILandscapeGlobal.xml" will not be created at all. It is meant as a fall-back case, as long as there is not server file.
The second file "SAPUILandscape.xml" is user-specific. It holds your own SAP GUI connections (i.e. - not the shared ones).
The GUI connections are defined via "Service" elements in the new format.
The Service uuids are generated by SAP GUI when you create the connections. Each new connection receives its own UUID, generated by SAP GUI.
Let me know if I can help more!
Best Regards,
Vasil Bachvarov
SAP GUI for Windows Team
It is not "funny" highlighting, so much as an error in syntax highlighting. It is reporting it as an error when = is used as opposed to "EQ", < instead of LT, etc. A clear bug which one is certain is impossible to miss if even minimal testing/validation before release is performed.
What's equally frustrating with 7.40:
deletes some user settings in the IDE (e.g. custom coloring schemes reverted)
cannot change install directory
This is far as I made, 5 minutes of use, before realizing it was rollback to 7.30 time ... How did 7.40 make it out of testing?
Apparently the obvious bug with the syntax editor does not appear if you have a 740 backend system. Despite claims to the contrary my gut feeling is that testing was only done on such a system which is why the error was not spotted. It is in fact the only possible explanation.
The fact that the conversion to 740 erases a whole bunch of files with no hope of recovery is just unforgivable. No-one would be able to predict that sort of behaviour as it is so unprofessional, there should have been some sort of autmoated conversion from the old format to the new format.( Prediction : SAP will say that would have been "impossible" i.e. possible but too much like effort).
However, we all know the saying "he who is without sin, let him cast the first stone". I write software all day long, and many times myself or my colleagues have released something in production and it has gone horribly wrong.
Unlike the 740 team, we do testing first, but no matter how much testing you do you can't catch everything, and no battle plan survives contact with the enemy, so things are going to go wrong.
What you have to do is realise the possibility that things might go wrong - either have a backout plan e.g. introduce new functionality in a dormant state which can then be switched on and off in production by a setting, or have people standing by, and if everything goes pear shaped, work as fast as you can to get a fix for really catastrophic bugs into production as fast as you can.
For short dumps type bugs we usually get them fixed within the hour, usually a lot faster. For really bad bugs ( akin to the problem with the errors in the ABAP ediotr in GUI 740 ) the fix goes to production generally by the end of the day, at the end of the next day at the very latest.
Never do we say, oh well, normally we release a patch every three monts, the thing we just released does not work at all, let us make the fix today and wait the normal three months before letting people have the fix.
I can still see it via SAP Gui options - SAP Logon Options - Local Configuration Files.
No Idea about new format
Some extra info. We already used the "Server configuration files" option with 7.30.
After upgrade to 7.40 my local very old files were converted, but how to convert the ones on the server?
Only option I can think of is to maintain locally the files and do the 7.40 upgrade there and use that files. Or there is an option to force the conversion for the files on the server?
Hello, Peter,
The conversion of the server files can be done by an administrator only.
The administrator can use the server files as their own SAP GUI configuration before first starting SAP GUI 7.40 (copy the server files to admin's %USERPROFILE%\SAP\Common folder with proper names - saplogon.ini, sapshcut.ini, SapLogonTree.xml). This migration is done only the first time you start SAP GUI. If you need to do it again, you will have to remove the files SAPUILandscape.xml and SAPUILandscapeGlobal.xml.
Once the Administrator has the SAPUILandscapeGlobal.xml, it can be published via HTTP, or put on a network share.
Edit: The "Global" file contains only message servers, routers and NWBC shared connections. In order to share also the SAP GUI connections on the server, the administrator needs to manually edit the SAPUILandscapeGlobal.xml and copy the services and workspaces with their contents from the SAPUILandscape.xml. Currently there are no SAP-tools to facilitate this step.
Then every user machine needs to have a registry entry "LandscapeFileOnServer", similar to the "ConfigFileOnServer" in SAP GUI 7.30, which points to the HTTP URL or network share with the server landscape file.
It is very important to always keep the UUIDs in this shared file constant - never change them.
The maintenance of the server UI Landscape needs to be done manually or the file can be generated by custom tools only at the moment.
Your assumption is correct. This is the workflow at the moment.
Unfortunately, the files on the server cannot be migrated automatically, because SAP GUI is used by normal users and they in general do not have modification privileges on the server/network share. The shared files need to be updated by an administrator.
I hope this helps.
Best Regards,
Vasil Bachvarov
SAP GUI for Windows Team
Hi Vasil,
Thanks a lot for the detailed info!
Best regards,
Peter
No issues for me so far.
I'm on Windows 7, but the Blue Crystal Design is not available??
I'm also on Win7, but it was available. Very first one on the list.
I totally uninstalled SAP, cleaned the registry and program files and then reinstalled and all is now fine. It was down to restrictions that were made using our installation server!
Saprouter string not imported from saplogon.ini and doesn't work at all when added manually.
It is very bad, that SAPLOGIN_INI_FILE environment doesn't work in 740.
Hello, Vladimir Kogan,
The SAPLOGON_INI_FILE environment variable is obsolete with SAPGUI 7.40. The saplogon.ini file is not used anymore, it has been superseded by the SAPUILandscape.xml file.
You can use the environment variable SAPLOGON_LSXML_FILE to achieve the same result in SAPGUI 7.40.
Edit: This is not the case when SAP GUI is used without NWBC. In this case the saplogon.ini file and the environment variable SAPLOGON_INI_FILE are used just like in SAP GUI 7.30.
Best Regards,
Vasil Bachvarov
SAP GUI for Windows Team
It's correct when you are installing GUI with NWBC
Without NWBC it still using SAPLOGON_INI_FILE environment variable and saplogon,ini. file,
When you are installing with NWBC it imports entries from saplogon.ini file from SAPLOGON_INIFILE location into SAPUILandscape.xml. All new entries and changes are managed in xml. In case of GUI only installation l everything is sitill like in 730.
Regards
Vladimir
Hello, Vladimir,
That's correct. Sorry for my misunderstanding of your use case.
So does the SAPLOGON_INI_FILE variable not work in the case when only SAP GUI is installed and saplogon.ini file is used?
Best Regards,
Vasil
In case when GUI only is installed - everything works like in 730. You can find more information in this guide here - at GUI installation DVD.
Hello, Vladimir,
OK then. In the case SAPGUI+NWBC the new Landscape UI format is used, therefore you must use SAPLOGON_LSXML_FILE instead of SAPLOGON_INI_FILE. This is by design so, please refer to SAP Notes 2075073 and 2075150.
Best Regards,
Vasil
You are Right. I can not believe SAP can update this big BUG to customers. And SAP GUI740 will be updated patch 1. So slow！
Any ideas how to get an administration manual...?
Sure - find all docs in DOCS folder in installation DVD 😉
It does some mess in my configuration file. I can login but after closing NWBC my message server is cleared in logon configuration. I have to open Logon Pad and re-enter it :/
I have raised an OSS for this as It stops me gaining access to my Production system using the GUI if I have NWBC open
Hello Jacek,
Can you also open a message regarding this issue on BC-FES-GUI and attach you configuration files please?
Thanks,
Martin
Hi Jacek, there is incident message for this problem. I am working on it with highest priority. The solution would be oficially the part of next patch level. Andriy
It is a very buggy release.
I use software in the enterprise to track application installation and versioning across the company. My complaint with this SAP GUI install is that it doesn't reset the patch level in Programs and Features in Windows (Windows 7, specifically).
In this screenshot, I had come from SAP GUI for Win 7.30 Patch level 10. On another machine, I came from Patch level 8, and that is reflected in the Programs and Features of that machine.
I also checked, but surprisingly I don't have this issue.
However I cannot uninstall SAP NWBC 4.0. When I click on uninstall it starts the Uninstaller for version 5.0, which currently I don't want to uninstall.
Hello William,
this can also happen when you "patch" SAPGUI 740 with SAPGUI 730 PL10.
Regards
Michael
I, like many people on this page, am a glutton for punishment, and so naturally I installed the 740 GUI the instant it was released.
The question is, am I so curious about new things that I would install something that obviously was going to be crawling with bugs and would fall over all the time, just to see what it was like. Was I willing to endure three months of agony until the first patch came out to fix the more obvious problems and another three months until the GUi was realatively stable?
Well, yes I am, I am prepared to go through this, so I downloaded the new GUI and switched the theme to "blue crystal".
As mentioned above, if your SAP system details are stored on a server then they vanish on the logon pad, so that is not a good start. I had to beg the system details off my poor old technologically backwards colleagues with their archaic 720 GUIS before I could even log into my shiny new SAP system.
It was clear to me that whoever designed the ICONS and the look and feel of the "blue crystal" theme had been taking an awful lot of LSD. I did some background checking and found that the head designer was in fact Dylan the Rabbit from "The Magic Roundabout". He said to me "wow man, that blue crystal is so hip, all those groovy colours, the colours in my head, the music in my mind that no-one else can hear, the magic mushrooms that I eat, they all inspired my design". So that clears that up.
As someone else noted the syntax check in the ABAP editor has colours all over the place. It has not yet crashed, but I have only been programming for a few minutes, so I imagine it will before the day is out, all previous beta versionof SAP GUIs like this I have installed as soon as they came out crashed a lot.
As the ICONS are just different enoiugh to throw someone totally, I am now looking forward to someone coming over to me and trying to demonstrate something to me on my machine, and watching them flounder when they are unable to work out what button to press.
Still as I said at the start I cannot complain - I have entered this House of Dracula of my own free will by downloading the 740 GUI, thus implicitlly volunteering as a beta tester. I, like everyone else on this page, will keep reporting any other bugs I find, so that in about six months time when the 740 GUI gets to about patch level 3 it will be fit for productive use.
Cheersy Cheers
Paul
"It was clear to me that whoever designed the ICONS and the look and feel of the "blue crystal" theme had been taking an awful lot of LSD."
😆 😆 😆 You made my day.
I found also very strange, that the new theme is available for SAPGUI, but NWBC has still the Corbu by default.
I have to say, I don't mind the Blue Crystal theme found in UI5/Fiori. For the most part, Blue Crystal 'inspired' applications look pretty good (Lumira, Fiori Launchpad, Design Studio Apps) however I had the same reaction as you with the SAPGUI implementation. They took a good looking theme and ran with it for what I think were the wrong reasons. You don't just start making new Icons that are solid blue and call it Blue Crystal or SAP-Icon, but here we have it. But it Is SAP GUI after all and I don't expect an Apple Experience for backoffice DynPro screens so I'm not upset (nor do I think any of us are losing sleep over it) but I love your commentary!
I tried it but I no longer recognized any of the familiar icons and had to switch back for productivity sake.
I quite like it, and will use it. However when we do release it to the user base when it is a bit more stable we won't be using the blue crystal theme as it's far too different and I can imagine the amount of complaints we would get!
I tried the NWBC 5.0 last night.
Firrst of all on a positive note - connecting NWBC 4.0 to one of my SAP systems was really hard work, with 5.0 the list from my logon pad pops up, just as if I had pressed the real SAP Logon Pad ICON so that is good.
We have single sign-on in my company and NWBC 4.0 used to ask for my user name and password twice - when logging on, and every time I chose a transaction code. with NWBC I no longer get asked for this when logging on, and the first time I choose a transaction code I get the SSO screen (if there are multiple clinets) no user name, no password required, so that is an improvement. I still get asked for a password when trying to open a Web Dynpro application though.
After that point it is just like working in the SAP GUI with one eye closed and one hand tied behind your back( I concur with the earlier post that having the menu as a button in the application toolbar renders the thing unusable).
There must be something good about this, something that would make using the NWBC better than the SAP GUI, and one day I will find out what it is. The fact it is not obvious says a lot.
Cheersy Cheers
Paul
NWBC copies my entry used for logging in - now I have about 15 copies of my connection in configuration file.
I have this issue I found that deleting the old NWBC configuration from your AppData directory and deleting the SAPUILandscape.xml and starting from scratch resolves this issue.
It is supposed to migrate it but it doesn't work very well, I have found there seems to be a total lack of documentation in relation to the new Unified SAP Landscape so I have just about got my head around the new XMLs and how they have replaced the NWBC config, SAP GUI logon ini and the services files. The "Workspaces" and now used on both the GUI and NWBC.
Many thanks Michael, this trick is working 🙂 🙂 🙂
Dear Jacek, my name is Andriy, I am from NWBC development team. Is it possible for you to create incident for this issue? The issue which you've described appears only sporadical and often depends on particular user environment. That is why it would help to analyse the issue if you create an incident. Best regards, Andriy
Hi Andriy, i am Karl, i used 5.0 the whole day, duplication of the systems occured also.
i delete all the entries and started from scratch.
As soon as i use Logon from inside the running NWBC, it duplicates all the entries, and then .....
i enjoyed 5.0, but this topic has to be solved extraordinarily soon, otherwise i cannot use it.
Karl
Hi Karl, ist it possible for you to create incident? Please do it ...
HI All,
When i am trying to press back button after testing RFC in SM59 GUi hangs.
I tried by pressing back button as well as by shortcut F3.
Anyone else is facing similar issue?
Thanks
SG
It's a bit disappointing to see that SAP GUI 7.40 still doesn't handle High Resolution/High DPI screens correctly 🙁 ... unless I am missing something (very possible), it seems to do just as bad a job as 7.30. Can anyone confirm?
We've tried it on a hi-def windows 8 laptop and on a 4K screen and found that 7.40 / NWBC 5 worked absolutely fine.
Thanks for responding Michael, in that case I have probably missed something. Running it on a MBP with retina display isn't working well for me, I just can't seem to get it to scale correctly.
Simon, you aren't missing anything. On the contrary, I'm afraid, Michael is missing problems and bugs in SAP GUI with support for high-dpi screens. I have 15" MBP w/Retina with 2880x1800 native resolution and work with Windows 7 (and now also testing Windows 10) through Parallels. To reproduce high-dpi experience of Mac OS I'm using 200% scaling when running Windows. This makes fonts crisp and clear while not making OS elements tiny and unusable. With such config Windows OS itself, MS Office 2013, IE, Firefox and some other application work just fine. Maybe not 100%, but they are close to that.
Not SAP GUI. There are scaling problems here and there: fonts are rendered Ok, but they are overflowing rows and placeholders, often making labels unreadable. This even affects Options settings screen, where fonts are selected themselves. Here are some examples:
OK I have really tried to use NWBC but I gave up.
1. Mess with my configuration entries: NWBC deletes my Message Server from a Group entry type in SAP Logon, also copies entries (NWBC connections) - today I have already 18 entries of my NWBC connection. Clean install (deleted registry entries&app data) does not help.
2. With option "Use SAP Menu" I have messages about invalid nodes, refreshing etc.
3. Sometimes it just does not login when I'm using SAP Logon connection.
4. Crashes i.e. when I am connected to NWBC connection and I'm trying to switch to SAP Logon connection
5. Sometimes index page does not show frequently used transactions, last opened etc.
1. Message server is an issue, did you delete the SAPUILandscape.xml as well as the NWBC folder? I found that had to be done to resolve my duplication issues, I also renamed by saplogon.ini.
I haven't experienced issues 3 or 4 and have used it fairly frequently.
Can't comment on 2 or 5 though
Yes, tried that, no luck.
Hi Jacek,
As you can see above, this is an issue that we will have to test. Andriy Sobol from development has suggested that you (and Karl) open an OSS.
Sorry, but there is no alternative.
Best wishes,
Julie R Plummer.
up to now, it works fine for me
After installing 7.40 w/o NWBC we had an issue with SSO. Secure Login Client wasn't any longer able to identify the user's SNC names. Didn't find a solution. Back to 7.30 and all works fine 🙁 Any ideas?
I bet you clicked the SNC options during the installation which is a big no no!! don't tick it and it leaves the Secure Login Client configuration in place. I had absolutely no issues.
U r right. Did it so. But did the same with 7.30. Different behavior?
Must do something different in the installation, I did a lot of tinkering (trying to get blue crystal to work) so ended up removing everything and starting from scratch so installed the SLC afterwards. But during my many different ways of installing SSO always worked.
Although the installation process ran smoothly, the usage itself has been very poor:
Personal experience recommendation: don't upgrade right now!
Anxiously waiting for patch 1 or at least a way to correct the connection problems...
Isn't it a rule of a thumb to do not install anything until the first service pack comes out? 🙂
But if everyone does that we'll never find the bugs! We need a few people foolish brave to try release 0, preferably on non-critical machines 🙂 . I was feeling brave this afternoon...
Steve.
There's no need to wait for service pack/patch, if software is properly tested before release. In this (so called) "release" basic functions are not working - connecting to system, configuration, ... I can understand, that there are few glitches in new release in some specific conditions. But this? Almost everybody is havning problems. So I'm curious how (if even) was this release tested? Because it only needs first start and problems appeared. Let's say that we release something like this to our customers. Something that can't fulfill basic functionality. It would be disaster and lost of credibility, that would take time to get back. But as we can see, somebody cares, somebody doesn't...
I've had many of the problems listed here (server groups unusable, NWBC connections in the systems list duplicating wildly, etc.) But I have run across one that does not seem to have been mentioned yet:
GUI crashes when upon executing PFCG. But this only seems to happen if I run it from the command field. If I double click a role in SU01, opens just fine.
Have to concur with others this is not a release for the faint of heart.
Hi Brian,
it might help to delete the following folders if your OS is Win7:
C:\Users\<Username>\AppData\Roaming\SAP\SAP GUI\Docking
C:\Users\<Username>\AppData\Roaming\SAP\SAP GUI\History
C:\Users\<Username>\AppData\Roaming\SAP\SAP GUI\LocalTabOrder
But switching between Logon and NWBC seems to break it again.
SAP GUI 7.40 crashes
Regards
Björn
Thanks for the reply. I'm on Win 8.1.
I had emptied the \AppData\Roaming\SAP\SAP GUI\ folder as well as completely uninstalling GUI 7.3 before this latest install of 7.4.
My first install (over top of an existing 7.3 installation) indicated that it wasn't very good to have the old version's files around.
The PFCG crash issue is linked to the Blue Crystal theme. It worked fine after I switched back to the Enjoy theme.
I will have to uninstall and put on a test pc.
Switching to a different theme (I tested Corbu) resolved the PFCG crash for me as well. Nice catch.
No issues here with PFCG. I haven't had any problems with 7.4 (blue crystal theme) except for having to concentrate and figure out what icon I am trying to find, for infrequently used icons.
What about promised 64-bit version, that will work with 64-bit MS Office?
The 64-bit version was ruled out for the time being in another discussion thread, because of the benefit being "negligible".
Russian text in the header of the table in search of a means of
I think that is not GUI related issue. Maybe Unicode checkbox?
Where can i download the gui 7.4 if i have not SAP Service Marketplace id ? please
I have been thinking about the new release of the SAP GUI and NWBC 5.0 which myself and many others have been trying out.
Traditionally there have been two schools of thought about software.
The first, which a lot of my German colleagues subsrcibe to, is to document everything really well up front, be sure of your requirements, do not change those requrements, and then work through each one methodically until every one works, no matter how long it takes. Then the software is more or less provably correct, and you release it. This can mean a very long time between the initial request and the final product but you can be very sure it will work. It might not actually be what is required though as what people ask for, and what they want, are two different things.
The second, which is common in Australia, is to just get a very vague requirement which you know is going to change, whip up something as fast as you can, bang it into production, you know it won't work and is not what people really want, but when people see it they will point out the bugs and say "what I actually wanted was this". Then you try to implement the changes and fixes as fast as you can and wham that into production and see what happens, and the cycle repeats. This is a very fast process but it involves constantly giving people things that don't work, and can make you look like an unprofessional fool who takes no pride in what they make and generally doesn't know what they are doing, even if the end result works perfectly and gets there much faster than the first method (people remember things that do not work, they take things that work for granted).
With SAP being a German company you would have thought they would favour the first approch, but as this release of SAP GUI 740 has shown, they have gone for the second one big time. They got a load of feedback about all the bugs the very first day, now they will be judged on how fast the first service pack fixing the more glaring bugs comes out.
This is rather like the "Peter Principle" which says that in big organisations people get promoted if they do a certain job really well, until they get promoted into a job they cannot do. They don't get demoted again, as that would mean the person who promoted them admitting a mistake, so after a while every single person in the organisation is in a job they cannot do properly. I am sure that is an exaggeration, but it would explain a lot of things.
In the same way, if we assume that SAP is forced to release SAP GUI versions before they are anywhere near ready (as is obviously the case with 740) and let us pick a number at random based loosely on historical evidence and say at one support pack every three months, it takes 12 support packs (three years) before a SAP GUI version becomes stable (by which I mean not crashing all the time for no apparent reason with the "error in parser thread" message). SAP GUI 720 is stable as far as I can see even though it is out of support, 730 was still crashing about once a month as of last month, and I always keep up to date with the latest patch level.
Because of market pressure the life cycle of things like the SAP GUI gets shorter and shorter, and cerainly seems to be less than 3 years now. The blog above says four years for 740, but I wonder.
The point is, give that companies seem to be forced to release software after the most cursory testing, that when the life cycle of any given software product that it goes out of support before it has even reached stability then this will move us to a situation that every single piecce of software on the market does not work properly.
What is more, people are clearly prepared to accept that, which is why myself and many others downloaded the SAP GUI 740 the first day, knowing full well what would happen.
I would like to ask if anyone at SAP is embarassed at having to release such a poor quality product, on point of principle, even if the user base comprised of people like me don;t really mind how bad it is?
Cheersy Cheers
Paul
The second approach, which we all formerly knew as "making it up as you go along" is now called agile.
Hello Paul,
Just to clarify, the GUI lifetime is based on the Microsoft Visual Studio on which it is built.
This alone, determines the lifecycle,as when Microsoft stop providing fixes for a Visual Studio version,then it does not get used anymore.
Hope this clarifies.
Hello,
Thanks for that information - if the life cycle of the SAP GUi is tied to the life cycle of Microsoft Visual studio, then that does not really change my central point, as Microsoft are not immune to the market pressures which are forcing software companies to release new versions of products more and more frequently.
When Microsoft had 95% market share they could probably dictate how often they could release new versions of things, but I gather in recent years they have been feeling the heat a bit....
Cheersy Cheers
Paul
Glad to clarify Paul,It's hard to escape though, the JavaGUI also is limited with the Java Runtime.(hopefully released before the end of the year).
Thank you very much !
Hi...
GUI 7.4 is not available in Service Market Place. Can you please provide the link.
Software Downloads > A to Z > G > SAP GUI for Windows > SAP GUI 7.40 Core
Hi,
Currently, the new SAP GUI doesn't use saplogon.ini anymore.
Will this be fixed in the future? or is the new SAP GUI only using the SAPUILandscape.xml file?
What about using Eclipse? As eclipse is still working with the saplogon.ini file for connecting to the backend system.
Thx!
Regards,
Hans
Hi Hans,
if you install NWBC 5.0 and SAP GUI 7.40 you need to use SAP UI Landscape along with the XMLs. This is because SAP UI Landscape is the common format of SAP GUI and NWBC and we will continue to invest into this. saplogon.ini is still supported, but only as long as you are not installing NWBC 5.0 together with SAP GUI.
If you continue to use SAP GUI for Windows without NWBC you can proceed with saplogon.ini for now, but it is SAP's intention to stop support for this with the next SAP GUI release.
ABAP in Eclipse is for now still working with saplogon.ini, but the development team is aware of SAP UI Landscape and they are working on that.
Regards,
Frank
Hi,
another "feature" i discovered is that the shortcut CTRL + X doesn't work anymore.
Does anyone else have the same problem?
Regards Christian
I have been programming in 740 for several days now, waiting for the ABAP editor to crash unexepectedly, but it has not happened yet, fingers crossed.
What does happen though is that twice today I did something fairly normal
- I executed SE16 to have a look at the contenst of a DDIC table
- I traced a program using ST05 and then pressed the button to have a look at the trace file
In both cases the hourglass popped up and kept going forever. SM66 showed a database read on a table which had nothing to do with either transaction.
The "stop transaction" did not work, nor did going into SM04 and truing to kill my own session, nor did going into SM66 and trying to cancel the work process.
/NEX does not work as the hourglass is still going on one session, the way around this is to shut down totally. Then when you log in again you are asked if you want to canacel your existing logons and when you say yes the rogue process is indeed cancelled.
That is pretty bad as bugs go. I am probably going to be told it is just a co-incedence but it never happend before and suddenly started just after I installed GUI 740. Amazing co-incedence really.
Cheersy Cheers
Paul
In such cases right click on the SAPGUI icon on the tray and "Close Sessions ...." usually helps. You might check it.
ABAP editor didn't crash for me either, but syntax highlighting is really annoying.
Peter
Anyone has experienced a crazy colour style on the ABAP editor?
I'm not against the new Barça style editor, but it's a little weird 😀
Cheers!
Luis
Hi Luís,
I have noticed this right after upgrading from 730 to 740.
Oddly enough, if you change the syntax, the coloring changes back to blue, as it was now correct:
Found no way to revert or get around this through the settings.
Cheers,
Alexandre
Hi Alexandre et al,
the syntax highlighting issues are also fixed now in the upcoming Patch 1 (see notes 2081078 & 2081798).
By the way: the issue does only occur when logging in to older releases when using SAP GUI 7.40 the first time. Using the ABAP editor the first timne in an 7.4x system it is always fine. That's why maybe not all users experiencing this issue...
Cheers,
Martin
If the ABAP editor bug only appears in releases below 740 that may explain why no-one at SAP spotted it - probably all the testing is done on a 740 system, in the presumption that all customers are running 740.
However 740 has been out a year and a half and how many customers are actually running it? Upgrading to the latest version of SAP is no small undertaking (enhancement packs are upgrades as far as the effort is concerned) and adoption is not a straight line - more of a bell curve - but on average it is about 1% of customers a month, so it takes 8 to 10 years between a version coming out and te vast majority being on thet version as a minimum.
So after fifteen months what percentage of SAP custsomers are on 740? 10%? 15%?
What about the other 90% of customers? Don't they count?
I recall back around 1999 reading an article in an SAP magazine that said "do you remember when you used to use fucntion modules instead of methods? Come on, it wasn't THAT long ago".
Indeed it was not - at the time the article was written version 4.6 was only on "ramp up" (if they called it ramp up then) and that was the first version that supported ABAP Objects, so the guy from SAP was talking about function modules as ancient history when in actual fact only about 5 SAP customers worldwide actually had access to a system which could use global methods.
Right, and I wish there was a way to upgrade only the Netweaver foundation of ECC system to 7.4, without having to take the new version (EHP) of "Business suite" ...
Hello Paul,
no, sorry you understood me wrong. The issue with the syntax highlighting does not occur if the first logon was made to a 7.40 system. After that it's always fine and doesn't play y role which system you connect. Of course we are also testing on older releases which are more common at customers...
Hi Martin,
Thank you for the feedback.
Of course nobody likes when something like this happens, as the final product doesn't look so "final" after all, we as customers feel let down, etc. Here I am hoping that this is better handled for the next releases (if you guys need backward compatibility testers for the GUI, feel free to drop me a message).
Anyhow, where can the patch be found to be downloaded, could you shine a light on that?
The page "https://websmp201.sap-ag.de/~sapidb/012002523100015565132014" (from Support Portal), has a link that leads us to yet another page with nothing to download:
Cheers!
Thank you for shared this updated info.
BR
Venkat...
Excellent ....soppper ......marvellous
This is the fifth day of using SAP GUI 740 and I honestly don't think I can take it any more.
The problem with transactions hanging for no reason seems to get worse all the time.
I have a transaction (looking at a transport request) houglassing right now, if I go to the top left ahdn corner, right click on do "stop transaction" nothing happens, same with cancelling via SM04 or SM66. It turns out I had a work process running all through the night, it did not termiante even when I logged off, it only got killed when i logged back on this morning.
I also wish I had known installing SAP GUI 740 would stuff up the ability to log onto SAP, and I don;t think much of the code completion in the ABAP editor not working propelry any more.
I would have to concur with the others in this thread who advocate the following:-
"whatever you do, do NOT install SAP GUI 740. It doesn't work. At all."
I recall once in "Fawlty Towers" when a customer told Basil Fawlty that his hotel was the worst hotel in the world, and the Major pipes up "I just won't have that! There was this other place I stayed in once...."
Great!
Is anybody aware of what is the correct syntax\format for the XML configuration file.
I have both NWBC 5.0 & SAPGUI 7.40 installed -- Now my NWBC 5.0 is not loading and my SAPGUI logon pad takes 15++ minutes to load. After the SAPGUI load, I clicked on the option "Check SAP GUI installaion" - But found NO errors
For what's worth, this is what I found in the NWBC trace file (I presume SAPGUI is also reading the files, hence issue should be similar):
08:50:57.437 [main] * NwbcConfiguration.Initialize {
08:50:57.447 [main] * LandscapeAccessor.InitializeBase {
09:01:08.887 [main] * } // LandscapeAccessor.InitializeBase [ /u 10:02min /k 187.2ms /e 10:11min ]
09:01:08.897 [main] * Load landscape file from: C:\Users\<USERID>\AppData\Roaming\SAP\Common\SAPUILandscape.xml {
09:01:09.082 [main] * LandscapeParser.ParseLandscape {
09:01:09.087 [main] * Validation of xml file: The 'version' attribute is invalid - The value '1.0' is invalid according to its datatype 'http://www.w3.org/2001/XMLSchema:integer' - The string '1.0' is not a valid Integer value.
09:01:09.088 [main] * Validation of xml file: The 'encoding' attribute is not declared.
09:01:09.088 [main] * Validation of xml file: The 'timestamp' attribute is not declared.
09:01:09.088 [main] * Validation of xml file: The required attribute 'localization' is missing.
09:01:09.088 [main] * Validation of xml file: The required attribute 'origin' is missing.
09:01:09.088 [main] * Validation of xml file: The required attribute 'updated' is missing.
09:01:09.235 [main] * Validation of xml file: The 'slc' attribute is invalid - The value 'false' is invalid according to its datatype 'BOOL' - The
Hello, Damean-BF Chen,
1. Could you please check the size of your SAPUILandscape.xml file?
You can find it in this directory: %AppData%\SAP\Common
A common size would be in the order of 1k-100k. If it is much larger, this might be the reason for the large delays.
2. Furthermore - can you please check how large the file SAPUILandscapeGlobal.xml is (if available)?
3. Do you have a setting SAP Logon Options / Server Configuration Files / XML Configuration File on Server? It might be that your server configuration file is located on the network and there is a network problem in reading it.
It is advisable to create a customer support ticket with SAP if the mentioned steps cannot solve your problem.
Best Regards,
Vasil Bachvarov
SAP GUI for Windows Team
Vasil
Thanks for the addressing my questions. My answer as below:
1) File size SAPUILandscape.xml -> 7,723 KB (i.e. about 7++ MB!!!)
-Any suggestions on how to reduce the file size? Our original SAPGUI logon pad has about 28 entries.
2) File size SAPUILandscapeGlobal.xml -> 10 KB
3) Do you have a setting SAP Logon Options / Server Configuration Files / XML Configuration File on Server? Answer: NOPE. All our configuration files are local (i.e. C: drive)
Regards
Damean
Hello, Damean,
1) File size for SAPUILandscape.xml of 7 MB is abnormally high. It does not depend only on your connection entries, but also on message servers and routers, which were previously defined in sapmsg.ini and saproute.ini. Those files could get large depending on the size of your message server landscape.
Can you for reference tell me how large is your C:\windows\sapmsg.ini file? If it is also very large, this might be the source of the problem.
It is advisable to open a support ticket with SAP and send the specimen for analysis along with traces. It would not be a good idea to discuss concrete configuration of your network in public.
We have to identify the source that generated the large file. It might come from a couple of sources as SAP GUI is not the only product using the configuration file.
With SAP GUI 7.40 and NWBC 5.0 the configuration is shared among those (and a couple of other products) in a unified format. This is a new feature to simplify the maintenance of various SAP front end products.
2) The "Global" file is much smaller. This would mean that you have relatively few message servers. More details would be possible within an SAP support ticket, where we could dive into the concrete values.
3) This is OK - then the "Global" file should be used to access your message server information and the SAPUILandscape.xml - for the connection entries.
Best Regards,
Vasil
Vasil
Many thanks for the suggestion Vasil Bachvarov ... I open up the SAPUILandscape.xml and did notice that it actually has 98 pages in length!!! Even the NwbcOptions.xml file has increased to that size too. Drilling further, I notice that only 10 blocks of the Connections are original; the other 99% of the blocks of Connections are just copies of this 10 blocks.
My 2 cents ... For the next release, it will be good to have the SAPUILandscape.xml creation\conversion program to perform a duplicate check and eliminate redundant copies of the connection. That would probably resolve this type of issue.
I'm a little occupy for the next few days, so I do another test the following week. My plan is to manually edit the file and see how far I could go. Then I will analyse the R/3 config files you mention and re-install; again many thanks for the Hint!
Cheers
Hi Damean-BF Chen,
you can ignore this trace of landscape validation. These validation messages are not dangerous.
7++ MB is very big file, means migration does not work properly. Could you create incident message for that or just call me?
SAPLogon 7.4 erased all the SID and saprouter strings from all my connections
When I try to login I get this (despite I fixed the entries)
Hi Juan Carlos Jacinto,
do you use also NWBC 5.0? If yes, it might be the issue of NWBC 5.0. We have an incident message for very similar issue and I am working on solution for that with highest priority.
Hi Andriy Sobol,
Well, what a good news!
Guys will glad to hear that. And thanks for your works.
Did you check note http://service.sap.com/sap/support/notes/2077230 Gabriele
Hello, Juan Carlos Jacinto,
This bug has already been identified.
The workaround is to open the following files with an XML editor (capable of formatting XML):
%AppData%\SAP\Common\SAPUILandscapeGlobal.xml
and
%AppData%\SAP\Common\SAPUILandscape.xml
then find the <Routers> element - there must be several <Router> entries inside it.
Edit the "router" attribute and remove from all of them the last three characters: "/H/".
E.g. if you have:
router="/H/host/S/1234/H/"
you have to change it to:
router="/H/host/S/1234"
This should solve it.
See SAP Note 2077230 for more details.
Best Regards,
Vasil
Hi everybody,
I just tried both sapGUI 7.40 with NWBC 5.0; no issues so far. I enjoyed the possibility offered by the integration between the two solutions, since I usually work on different systems at time and the tabbed modes within a single nwbc session per system is quite useful.
A question; if I log in into an SRM system via NWBC 5.0, I'd expect that a launch on the NWBC transaction should open a new tab in the NWBC client itself; that's not the case however, when I launch NWBC an IE window pops up (so, it seems NWBC for HTML is triggered). Is there a way to configure the client so that the NWBC 5.0 client is used when /nnwbc is triggered? Thanks in advance.
/nnbwc will always open the NWBC Html client,there is no way to change that.
To start NWBC for Desktop, use the Desktop Icon.
Jude
Hi, slightly off-topic but does anyone know whether we can use Java 8 JRE's with SAP GUI? Which version (7.30 or 7.40) supports it?
Also, do we have to install 32 bit Java? Nearly all clients have 64 bit Windows 7 installed, so I prefer installing and using 64 bit JRE if there's no problem with it.