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:

Blue Crystal and Signature Comparison 2 en.jpg

  • 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.

Auswahl nwbc sapgui2.png

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.
        • 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.

Auswahl nwbc sapgui.png

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.
To report this post you need to login first.

151 Comments

You must be Logged on to comment or reply to a post.

  1. Paul Hardy

    I note that the first patch for 740 is scheduled for the middle of December i.e. about two months time. Hopefully that will fix some of the more horrible bugs.

    In regard to the obvious problem with the ABAP editor, it seems to me there are several possible reasons why the 740 GUI was shipped in such a state that this problem occurs, each reason worse than the last:-

    ℹ The problem was noticed during testing, but someone decided it did not matter, it was only the customers as in “I think about my custnmers all the time, I think about how much I hate them and want them to suffer, this will be a good way of acheieving that goal”. This is called being “customer centric” OR

    (2) Not even one developer was involved in the testing, nobody in the testing team ever so much as looked at an ABAP editor screen. They can’t have as anyone would noticed the problem straight away (it is literally highlighted in red) OR

    (3) There was no testing OR

    (4) The internal SAP system is so different from customer SAP systems that errors do not show up on the SAP internal system which would happen at a customer site. This is the worst possible scenario, as it renders SAP internal testing useless.

    I wonder which of the four it was?

    (0) 
    1. Vasil Bachvarov

      Hello, Isaac Mena,

      Please see SAP Note 2077230 for more details.

      In the files

      %AppData%\SAP\Common\SAPUILandscape.xml

      and

      %AppData%\SAP\Common\SAPUILandscapeGlobal.xml

      You have to edit all router strings (located in Router xml elements) and remove the trailing /H/ at the end.

      Best Regards,

      Vasil Bachvarov

      SAP GUI for Windows Team

      (0) 
      1. Tomas Chrastina

        Hi Vasil,

        I appreciate your effort to help, but I think ther’s need more to be done on SAP side. Also this solution won’t work for fixing system IDs and more problems with this release.

        If you (SAP) see there’s problem with release, you should release high priority fix/patch, not to force users to do manual update of files, because not everybody is able to proceed technical procedures of this kind.

        Bigger problem is, that there’s problem with configuration migration from older version(s). So even if patch will be released, it won’t solve all problems which current installer will make. So I think it’s time to think about update of installer to avoid and fix problems. Or write some install procedure or prepare tool to backup current configuration files. And then after applying of latest patch to be able to import them correctly to fixed/patched environment. It’s not possible to fix problem, when things are lost already.

        Best regards,

        Tomas.

        (0) 
      2. Samuli Kaski

        Thanks Vasil, you are doing a great job. I however feel that SAP should step up and release a hot fix right now for the most apparent discovered bugs, not let customer wait until half of December. I don’t think it can get much worse than what it is currently…

        (0) 
  2. G. Peeters

    SAP GUI 7.40:

    In SAP BW (7.30), we see no buttons in the navigation panel in the Data Warehouse Workbench (RSA1) with the Blue Crystal Theme.

    In SAP ERP (6.0 EHP7) no issues so far.

    NWBC 5.0:

    Nice to finally see the option “Stop transaction” ! However, when you try to close a tab where a transaction is running (e.g. when you made too big of a selection), the tab will be inactive and the process is impossible to terminate (except for SM50/SM66)…

    (0) 
  3. Frank Krause

    Hi all,

    thank you for all the feedback that you have provided within this blog (be it negative or positive). The issues that you have mentioned will be addressed as quickly as possible – if you have not yet received any replies from SAP for an issue mentioned by you I recommend creating a customer incident on component BC-FES-GUI so that the issue can be properly addressed and tracked.

    I will now close this blog for further comments.

    Best regards,

    Frank

    (0) 

Comments are closed.