SAP GUI for Windows 8.00 is coming on 27th of January 2023: New Features & Lifecycle Information

[FrankKrauseGUI]

Hello Community,

the next milestone for SAP GUI for Windows 8.00 after the successful Beta Program has been reached: Our new release will become available or is already available when you read this on SAP Support Portal as of / since 27th of January 2023 with full support ("GA version"):

https://launchpad.support.sap.com/#/softwarecenter/template/products/_APP=00200682500000001943&_EVEN...

With this blog, I would like to introduce you to the new features of release 8.00 and provide an overview on the lifecycle.

Naturally, the first question is why we decided to increase the release version to 8.00 and not simply go for "7.80". The reason is that 8.00 includes a long-expected feature that marks a new milestone in the history of SAP GUI for Windows and impacts also for the delivery: The true 64bit version. And from our perspective this is a good reason to increase the major release version.

Our focus areas in release 8.00 were:

• The 64bit version


• Quartz themes: Modernization of rendering engine and some additional features


• HTML Control based on Microsoft Edge: Improvements


• Usability improvements in many components


• Improvements for SAP Logon


• Branding images per system and client

Especially with the 64bit version, the improvements for the HTML Control based on WebView2 / Edge and the usability improvements, 8.00 offers a very interesting feature set that generates benefits for many users.

This blog reflects the situation when release 8.00 is initially delivered. Similar information that will receive updates in case we change something or add a feature in a patch can be found in SAP Note 3075781.

By the way: Once more, we have not removed any SAP GUI themes from our new release, so you will find the full list of supported themes to be unchanged (overall 12 themes!). However, you can find some information on changed default settings and other changes compared to previous deliveries at the end of my blog.

Due to experience from the past, I would like to ask you for the following: Of course you can post questions and comments related to the new release here (be they good or bad) and they are very welcome, because your opinion is important to us. However this blog does not replace our regular channels for support. If you have found an issue, please report this to us via the support system.
And do not post anything here which is not related to SAP GUI for Windows 8.00 at all. Thank you!

Best regards,
Frank Krause
Product Owner SAP GUI for Windows
SAP Development

---

SAP GUI Lifecycle

SAP GUI for Windows 7.70 was created with Microsoft Visual Studio 2019 which is in mainstream support by Microsoft until 9^th of April 2024 (see also https://learn.microsoft.com/de-de/lifecycle/products/visual-studio-2019). Therefore, SAP GUI for Windows 7.70 is still supported until 9^th of April 2024.

This also means a successor to 7.70 is required at least one year before the end of support and here it is: SAP GUI for Windows 8.00. For the new release we were able to use the latest version of Visual Studio (Visual Studio 2022) which is supported until 12th of January 2027 (see also https://learn.microsoft.com/de-de/lifecycle/products/visual-studio-2022). This results in an unusually long maintenance period of almost 4 years.

The chart below shows the current (27th of January 2023) lifecycle information of SAP GUI for Windows releases 7.60 up to 8.00. For the latest information always refer to SAP Note 147519.

---

New Features in Release 8.00

True 64bit version of SAP GUI for Windows

So far SAP GUI for Windows was only available as a 32bit version with the exception being the 64bit versions of the automation controls (Logon Control, Table Factory Control, BAPI Control and Function Control). The 32bit version works well on 64bit operating systems, but it has a couple of drawbacks when it comes to memory utilization and integration with other 64bit processes.

Due to this, we kept getting requests for providing full 64bit support in SAP GUI for Windows and thus decided to implement, deliver, and support such a version. As of SAP GUI for Windows 8.00, the SAP GUI delivery includes both a 32bit version and a 64bit version. You can decide which version to use (parallel usage of both versions on the same client PC is not possible). On the installation media you find both versions and there will be individual patches for 32bit and 64bit (with the same schedule and the same corrections).

The 64bit version offers an almost complete feature set with some minor differences to the 32bit version which are documented in SAP Note 3218166. The most prominent differences are:

• No support for systems older than SAP_BASIS 7.00

The 64bit version does not support SAP systems on SAP_BASIS versions older than 7.00. Even though all these SAP products are already out of support, some landscapes still contain legacy components. If this applies to you, keep using the 32bit version of SAP GUI for Windows (the 32bit version will certainly remain available for some time). When trying to log on to a system with a 64bit version, an information popup is displayed and the logon attempt is refused.

It is our intention to keep the 64bit version open for future innovations that would not be possible if we had to support older SAP system releases.

• Usage of saprotwr.dll (Running Objects Table Wrapper - see also documentation)

Some products make use of the library saprotwr.dll to access SAP GUI Scripting via COM. Since saprotwr.dll naturally is a 64bit file when installed with a 64bit version of SAP GUI, only 64bit processes can access it. Therefore, if you are using saprotwr.dll, you need to make sure that the process from which this is called is a 64bit process if the 64bit version of SAP GUI for Windows is used.

• External components

SAP is not responsible for components which are added to the SAP GUI for Windows installation by external vendors. Please contact the respective vendors if the interaction of such a product with a 64bit version of SAP GUI for Windows fails while it works fine with a 32bit version.

• Performance / memory utilization

The 64bit version:

• 
  
  
  
  • consumes about 20% more memory compared to the 32bit version. Therefore, you should size your machines accordingly. The increase in memory consumption is due to different sizes of data structures and cannot be avoided.
  
  
  • requires about 10% more disk space on the client PC, because the 64bit modules are larger than the respective 32bit modules.
  
  
  • shows a substantially reduced CPU utilization compared to the 32bit version (between 5 and 20% depending on the scenario used). This also results in faster runtimes and perceived performance
  
  
  
  

See also SAP Note 26417.

Improvements for Quartz Themes

• Modernized rendering in Quartz Themes

The Quartz rendering engine has been completely reworked which leads to a more harmonized appearance (for example rounded corners and texts look much better). Furthermore, we have invested into some additional features. The OKCode (“command”) field has now offers buttons for deleting entries in its history via mouse and the visualization of the dotted focus has been improved. It is now much more prominent than before. We are intending to make the dotted focus the default focus visualization in one of the next SAP GUI releases after 8.00.

 

As an outlook I can mention that we are working on an additional feature for the OKCode field: An enhanced search for transaction codes as already available in SAP GUI for HTML and SAP GUI for Java. The release of this feature will likely come within one of the first patches.

• Displaying editing mode ("INS" / "OVR") in Belize and Quartz themes

As opposed to older themes, the Belize and Quartz themes by design did not show the indicator for the editing mode in the system information area. Based on user feedback we are re-introducing this feature on an optional basis. The feature can be activated in SAP GUI for Windows options dialog (page "Theme Settings") and it looks like this:

• SAP GUI Scripting: Correct handling of visibility properties for themes as of Belize

Starting with the Belize theme, the objects in the SAP GUI window have been re-arranged. For example, the GUI Toolbar (also "System Toolbar") and the Application Toolbar have been merged into the so-called "Header Toolbar". This had an impact on the SAP GUI Scripting properties which allow hiding parts of the SAP GUI main window. These properties have been revised in SAP GUI for Windows 8.00 and can be used in a meaningful way again.

HTML Control based on Microsoft Edge / WebView 2: Enhancements

• Full Browser Window when detaching URLs

The HTML Control based on WebView2 is still a relatively new control based on a new Microsoft component with some restrictions (as per SAP Note 2901278). Release 8.00 solved one of the most important issues: When SAP GUI opens an external browser window through the HTML Control only a browser tab appears (missing navigation, menu, and the options for grouping tabs). Thanks to a new browser extension for Microsoft Edge this limitation no longer applies and the HTML Control based on Edge can open a fully working Edge browser window like the HTML Control based on Internet Explorer already could.

In addition to SAP GUI for Windows 8.00 you need to install a browser extension called "SAP GUI Connector for Microsoft Edge" from the Microsoft Edge Add-Ons page (https://microsoftedge.microsoft.com/addons/detail/sap-gui-connector-for-mic/mhpigfckgphoiifbehgajfbk...). See also SAP Note 3258944.

• Embedded HTML documents can use ActiveX objects

Another restriction of the HTML Control based on WebView2 is that embedded HTML documents cannot interact with ActiveX Controls installed on the client PC. This is due to an intended restriction in Microsoft WebView2.

Now, with the ABAP extensions delivered in SAP Note 3260025 and SAP GUI for Windows 8.00 (or 7.70 as of patchlevel 11), it is possible to supply an ActiveX object to an HTML document and allow the interaction between these objects. The respective ABAP application needs to supply information on the object to be invoked to SAP GUI.

Usability Improvements

• Combobox Control: Showing keys and sorting by keys

The ActiveX control version of the UI element combobox (used in a growing number of transactions, like SE80) so far could not display the keys of the entries or sort the entries by those keys. These options contribute a lot to the usability and the efficiency of use of a combobox. With SAP GUI for Windows 8.00 these feature are available and can be controlled by the same settings that are also relevant for the "normal" combobox (SAP GUI Options Dialog -> Interaction Design -> Visualization 1):

• 
  
  
  
  • Show keys within dropdown lists
  
  
  • Sort by keys within dropdown lists for most efficient keyboard input
  
  
  
  

With both options activated, a combobox control shows not only the value, but also the key of the entries in a table-like format. When typing in a combobox showing keys, the selection of items is done based on the keys and not on the values.

• Tree Control: Scrolling indicator

Tree controls now show a so-called "scrolling indicator" when the user scrolls vertically in the tree via mouse or keyboard. This indicator helps the user to easily recognize the position of the currently displayed block of data within the tree and supports a more precise drag and drop of the scroll bar button (thumb).

This feature is available for all themes except for "Classic Theme".

• Table Control: Improved keyboard navigation

Table controls now support additional and refined keyboard shortcuts for improved navigation and more consistency:

• 
  
  
  
  • CTRL + UP / CTRL + DOWN: Scrolls to the very top or bottom and moves the focus into the first cell / last cell that contains data of the same column.
  
  
  • CTRL + HOME / CTRL + END: Scrolls to the very top or bottom and moves the focus into the first cell of the first row / last cell that contains data of the last column.
  
  
  • CTRL + PAGE UP / CTRL + PAGE DOWN (if supported by the application): Scrolls to the very top or bottom and keeps the focus in the current cell if possible.
  
  
  • The "Select All" button (if present) is now part of the tabchain and can be triggered like any other button in SAP GUI for Windows (SPACE / ENTER)
  
  
  
  

• Dialogbox Container: Improved keyboard navigation

Dialogbox containers (most prominent examples are the Performance Assistant and the GOS Container window) are amodal windows which have not been well-integrated into the tabchain of SAP GUI for Windows until now. It was not possible in a reliable way to move the focus from or to a dialogbox container via keyboard. With release 8.00, dialogbox containers are added to the regular tab chain of SAP GUI and can be reached via TAB / SHIFT + TAB / CTRL + TAB / CTRL + SHIFT + TAB.

• Checkboxes and radiobutton groups: Improved keyboard navigation

Just like for regular buttons the selection of checkboxes and radiobuttons can now be aborted by pressing SHIFT while still holding down SPACE. This is needed, because there are checkboxes and radiobuttons which automatically trigger an event when being selected. Just like before the focus can be set to radiobuttons without selecting them via CTRL + CURSOR.

Additionally, HOME and END keys can now be used to navigate to the first and last active radiobutton in a radiobutton group.

• ALV Grid Control: Copy & Paste with gaps

Clipboard content, especially when taken from applications like Microsoft Excel, may contain empty cells, columns or rows like in this example:

So far, the ALV Grid Control used to overwrite the content of all cells when a block as depicted above was pasted. If one pasted the above data into the top left cell of an ALV Grid Control looking like this:

the result would have been:

However, this result may be unexpected, and it was not consistent with the handling in SAP GUI for Java and SAP GUI for HTML. Therefore, we changed the default behavior for pasting data into an ALV Grid Control, so that empty values do not overwrite cell content when being pasted.

In the example above, the result with the new feature is:

Of course, there is a switch to restore the old behavior if needed.

• ALV Grid Control: Special control characters are no longer inserted when pasting from other programs like Microsoft Excel

According to SAP Note 1825127 ALV does not support non-printable control characters. So far such characters could be entered via SAP GUI for Windows for example by copying cell content from Microsoft Excel into an editable ALV Grid Control. The copied characters where either displayed as “#” or other symbols and could cause functional issues in some applications. Since ALV does not support these characters anyway, we are now preventing the pasting of such characters to avoid errors and remove those characters from pasted text.

• ALV Grid Control: Improved keyboard navigation for comboboxes

Keyboard support for comboboxes embedded into an ALV Grid Control has been extended and is now equivalent to the keyboard support for other comboboxes outside the ALV Grid Control. Specifically, this also means that values are no longer taken over into the cell automatically, but only when the user confirms the selection actively (ENTER) or implicitly (by navigating away after changing the selection). This also enables users to abort a selection via ESC. Furthermore, the selection by typing the leading characters of hits in the dropdown list has been improved and the dropdown can be opened / closed also via F4.

SAP Logon 

• Secure Network Connection without Single Sign-On as configurable default

So far, the checkbox "Activate Secure Network Communication" in the Secure Network Settings page of the SAP Logon dialogs for creating a new connection or performing a variable logon was automatically selected if the SAP system supports SNC and an SNC product is installed on the client PC. At the same time the second checkbox "SNC logon with user / password (no Single Sign-On)" was not selected. This assumes that the installed SNC product also supports Single Sign On (SSO). Obviously, this does not take the situation into account when the server can do SNC, but the client SNC product does not support SSO. In this case a user may unintentionally create a connection with activated SSO that will not be working.

Therefore, release 8.00 introduces a registry setting that allows changing the default state of "Activate Secure Network Communication" / "SNC logon with user / password (no Single Sign-On)". See also SAP Note 3074756.

• Improvements for sorting and ordering columns

As of release 8.00, SAP Logon (Pad) remembers the sort order applied by the user as well as the sequence of the columns and the column widths. An administrator can roll-out default values for these settings. See SAP Note 3099771 for more information.

Furthermore, columns relevant for SAP Shortcuts and Favorites have been added in the Workspace View and List View so that all relevant data can be displayed in these views as well. The available function for hiding columns was extended letting an administrator decide which columns are needed. This is explained in SAP Note 3100231.

• Checking operating system prerequisites on language selection

SAP GUI for Windows is a non-Unicode program. Therefore, SAP GUI can only be correctly displayed in the language of your choice if the system locale defined under Windows matches your language selection. For example, if you would like to display SAP GUI for Windows in Japanese without any visual issues like garbled characters, you need to use the Japanese system locale.

Now, the SAP GUI options dialog checks whether a correct display of SAP GUI for Windows will be possible with the language you selected. If not, SAP GUI for Windows displays a warning and falls back to using English language to guarantee a correct display of all contents. Previously, SAP GUI for Windows simply accepted any selection which could lead to display issues almost impossible to anticipate for the user.

• Backup for user defined SAP UI Landscape files

It happens that a local SAP UI Landscape file containing all the connections / shortcuts / favorites as user created is overwritten by another process or gets lost somehow. This is very annoying for users, because creating such a file over the course of years takes make have taken some effort. Therefore, SAP Logon now creates backups of the local SAP UI Landscape file. When a file is accidentally overwritten, the user can retrieve one of the backups and continue working. The user is actively informed, when the local file is broken and a backup is available. See SAP Note 3263097.

Branding Image: Images can be configured per SAP system and client

Until now only a single branding image could be configured regardless of which SAP system SAP GUI is connected to or to which client in this system you are logged on to. Since there are cases in which different images per system are desired (for example if systems are hosted for different customers of if you would like to better distinguish systems), you can now define and select branding images per SAP system and client.

More information how to use this feature can be found in the SAP GUI for Windows Administration Guide. The images to be used as branding images need to be present on the client PC in a specific file structure that you can for example create via NWSAPSetup.

Revised font settings dialog and persistence of font settings per character set

As a general recommendation changing the font size in SAP GUI for Windows should only be considered if working with the scaling provided by Windows is not sufficient. However, if you really need to adjust the fonts, the options dialog offers a page for doing so for the monospaced font (used by ABAP lists and some other elements) and the proportional font.
In the past the dialog showed the font size in points which lead to a lot of misunderstandings, because internally SAP GUI cannot work with points, but with a scaling factor in percent. The transition from points to percent could lead to unexpected results. Therefore, the font settings dialog has been revised and the selection of the font size is done directly via a scaling factor in percent.

Since in most cases users only want to change the font size, the dialog is displayed in a basic mode unless an "expert mode" is activated.

Furthermore, it is now possible to maintain and store different font settings including the font size per character set used. This means if you are working with multiple languages using different character sets (for example English and Japanese), SAP GUI for Windows is displayed correctly in both cases. So far, only the font names where remembered which could lead to display issues.

---

Changed features in patchlevel 0

• HTML Control: Edge based on Chromium (WebView2 Control) is now the default browser control

The default setting for the browser control used to host HTML content inside SAP GUI for Windows is no longer the Internet Explorer control, but Edge based on Chromium (WebView2 Control). Due to the de-support of Internet Explorer as a standalone application by Microsoft (see also SAP Note 3058309) and the strong desire to move to a more modern browsing experience, this is a change which just reflects the expectation of most SAP GUI users. See SAP Note 2913405 for more information on browser controls in SAP GUI for Windows.

• UAC Virtualization is no longer turned on

Up to and including release 7.70, SAP GUI for Windows uses the UAC virtualization for the executables saplogon.exe, saplgpad.exe and sapgui.exe (you can see this in Windows Task Manager in column "UAC virtualization"). The idea of UAC virtualization is to redirect write access to protected resources in the file system (c:\Windows* \ C:\Program Files*) and in the registry (HKLM) to mirror locations ("VirtualStore"). However, this also means that read access to the same resources can be routed to the mirror locations which makes the analysis and resolution of issues related to this very difficult. Therefore, as of SAP GUI for Windows 8.00 the UAC virtualization is no longer activated. SAP Note 3064276 explains the background and impact on ABAP applications which try to access protected operating system resources.

• SAP UI Landscape: Handling for loading server configuration files in case of certificate errors

To achieve a more secure default configuration, web-server-based SAP UI landscape files are not loaded anymore by SAP Logon in case certificate errors occur. This behavior can be customized according to the settings explained in SAP Note 2892419, but we generally strongly recommend using valid certificates.

---

No longer supported / available

• KW Add-On for SAP GUI no longer contains HTML editing component

The subcomponent "KW HTML Editor" of the KW Add-On is no longer available as of SAP GUI for Windows 8.00. See SAP Note 3147887 for further information.

 

[naim_tezel]

Too many crashes and bugs. For example kanban board is not displayed properly.

[henning_abel]

Hi Frank,

same question from my side. We cannot find BEx in 8.00 64 bit.

 

Thanks and best regards,

Henning

[former_member204677]

Regarding BEX please see notes:

https://launchpad.support.sap.com/#/notes/3218166
and
https://launchpad.support.sap.com/#/notes/3213997

Kind regards,
Martin

[andrey_ryzhkov]

Hi Martin,

If it doesn't make it difficult, can you briefly write the essence? Will there be BEx in the 32bit version? No access to notes, unfortunately.

UPD:

3218166 – SAP GUI for Windows: Functional differences of the 64bit version compared to the 32bit version

SAP Business Explorer

This component will not be supplied as a 64bit version. However, the 32bit version can be combined with a 64bit version of SAP GUI for Windows as long as a 32bit version of Microsoft Office is used. See also SAP Note 3213997. The 64bit installation of SAP GUI for Windows does not contain the 32bit component, you need to get this from a 32bit installation media or from another location. For more information please refer to support component BW-SYS-GUI.

[abo]

"SAP Note/KBA 3213997 is being created." 🙂

[former_member204677]

Hello Naim,

could you kindly open an incident with an example how to recreate?

Thanks,
Martin

[ChristianGünter]

SAPGUI 8.0 crashed and I got an option to send a mail with the error information. E-Mail address looks a bit special though

Email

[FrankKrauseGUI]

Hello Xavier,

but of course, you can use a WTS or Virtualization software to run multiple different versions on your device (as you suspected). The point is that in these scenarios, SAP GUI is not running in parallel on your machine, but one is running on the server and one on your local PC. However, the server can of course again have only a single version of SAP GUI installed.

Best regards,
Frank

[henning_abel]

Dear Mr. Runz,

note 3213997 seems not to be available.

Thank you.

BR,

Henning

[naim_tezel]

Sorry i removed it and downgraded to 7.70 so i can't give any more information. But i had a screenshot from kanban board.

 

[sjforster]

SAPGUI 8.00 x64 - Missing text in Quartz themes in SPRO, displays correctly in Blue Crystal and Classic themes

 

SPRO - SAP Reference IMG - Quality Management - Quality Notifications - Notification Creation - Notification Type - Define Screen Templates - Field Selection: Partner Screens

 

 

 

 

[FrankKrauseGUI]

Hello Andrey,

neither Martin, nor I, nor the SAP GUI team are responsible for Business Explorer or the BI Addon and therefore, we won't comment on those components.
Please direct all questions related to this (including questions on the release strategy) to the appropriate support channel (component BW-SYS-GUI).

Best regards,
Frank

P.S.: This applies also to SAP Notes created on that component (like 3213997 mentioned above and below).

[FrankKrauseGUI]

Hello Scott,

thank you for this information. I could reproduce this issue and we will certainly fix it in patchlevel 1.
However, in general, I would like to ask everybody contributing here to please report obvious product issues via our standard support channel. A handling and tracking is almost always impossible without what we call "incident".

Thank you for your understanding and best regards,
Frank

[former_member204677]

Hello Willem,

finally this new created note solves the issue:
https://launchpad.support.sap.com/#/notes/3300460

Kind regards,

Martin

[WillvT]

Hello Martin

Thank you for the update!

Much appreciated.

Cheers

W

 

[tamasbeckerfujitsu]

Hi,

 

does anyone know if it works properly with Adobe Livecycle 11?

 

Thanks,

Tamás

[lruhnau]

Hi,

 

in the ABAP debugger I'm missing the function of quick view of variable content in the editor part when you hover with the mouse over a variable. Is this only in my installation?

 

Best

Lars

[ChristianGünter]

Same here

[yatinbhatt]

I am using the SAPGUI 8.0 64-bit version. there are 2 issues that I've observed so far.

1. When we have couple of windows open for a system, and try to choose LogonPad to connect to a new system, it takes a long wait before it shows up.


2. Once logged in to a system and let's say open /n/ui2/flp , it opens microsoft edge browser window with about:blank , and after few seconds, it opens Microsoft Edge WebView2 in a separate window.

 

[Berry]

I'm having problems when creating an interface in SFP;

The typing input help isn't working for me, couldn't create the interface with the 880 gui. I had to reinstall the 770 gui

[tamasbeckerfujitsu]

Probably when you tried to add variables, you cant select TYPE.

When I copied, and pasted an entry, it worked.

[dyaryura]

Hi Yatin

I'm having same issue mentioned in #2. Have you found a solution for this?

[manuf]

Hello,

Be careful with Patch level 1, I installed it and cannot open it on Win 11.

SAP released a note about it, providing temporarily some registry fix.

https://launchpad.support.sap.com/#/notes/3320385

________________

After installing patch level 1 of SAP GUI for Windows 8.00, SAP Logon does not start anymore on some devices.

The cause of the issue is a conflict between a security feature in SAP GUI for Windows and the used security product.

SAP is currently working on a solution to this issue with highest priority.

This KBA will be updated as soon as further information can be provided.

Workaround:

You can deactivate the SAP GUI function which causes the conflict to the external security products by setting the following registry value on affected clients:

For a 32bit version of SAP GUI for Windows:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SAP\SAPGUI Front\SAP Frontend Server\Security

"UseComHjkngWA" = "0"    (DWORD 32-bit)

For a 64bit version of SAP GUI for Windows or a 32bit version on a 32bit operating system:

HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPGUI Front\SAP Frontend Server\Security

"UseComHjkngWA" = "0"    (DWORD 32-bit)

If you deactivate this feature, the issue is resolved.

When doing so, SAP GUI for Windows will theoretically be vulnerable to a specific and generic type of attack which can be avoided if write access to  HKEY_CURRENT_USER\SOFTWARE\Classes\CLSID\ is restricted. Such a restriction would prevent attacks of this kind not only against SAP GUI for Windows, but also other programs. However, it needs to be checked on an individual basis whether this has any side-effects on other programs which may need write access to this branch.

Therefore, we recommend to only use the registry value mentioned above if absolutely required and to remove the value as quickly as possible again after a patch which solves the general problem has been delivered.

Important: Should you receive a test version of a patch containing the correction from SAP, please keep in mind that testing the patch only makes sense if the registry value mentioned above is NOT set.

[FrankKrauseGUI]

Hello Emanuel,

yes, it is true that patchlevel 1 is not starting on some devices.
It fully depends on which security products are installed and interact (=hook into) with the SAP GUI process.

We are presently working on releasing a new patch and will do so as quickly as possible.

Best regards,
Frank

[Badar_MD]

Hello manuf,

I am Using SAP GUI 800 Patch 1 on Windows 11 Enterprise 22H2 and It is working Fine.

[dennis_crampton]

Greetings, I installed the 64 bit SAPGUI 8.0 PL1 version and in testing i cannot seem to be able to create icons to call specific commands to call different SAPUILandscape.xml files. The all default to the generic file.

 

we have several different icons depending on the user role that we drop to the desktops. For some users they get just specific production systems, others get a training systems, and other get all development and quality systems for development and support roles. for example. I have the files all stored in C:\ProgramData\SAPINI\ as before
From what i can see the process has not changed... Any clues or suggestions on what must be done?

SAPGUI 8
Icon Target:  "C:\Program Files\SAP\FrontEnd\SAPGUI\saplogon.exe" /LSXML_FILE C:\ProgramData\SAPINI\SAPUILandscape_ALL.xml

 

When I check the icon properties: The loaded file shows:

Type                                  Path
Local File                C:Pogram Data\SAPINI\SAPUILandscape.xml
General File            C:\ProgramData\SAPUI\SAPUILandscape.xml

 

Any clues or suggestions?

 

[tor_ervland]

In PL 1 it also looks like the Full Browser Window (Edge) is not working as intended.

It looks to be back to the GUI 7.70 functionality, where it opens a chromium browser with no navigation bar, no menu or browser tab.

It worked perfectly in PL0, where it opened in a fully usable Microsoft Edge window.

[FrankKrauseGUI]

Hello Tor,

I cannot reproduce this behavior (and we did not change this in PL1).
Are you sure, the browser extension is still installed?
If so, can you post a screenshot showing the details of our browser extension (and maybe also the browser window showing the opened application)?

Best regards,
Frank

[tor_ervland]

Hi Frank,

Yes the browser extention is installed.

With PL0, when I opened e.g the SM_WORKCENTER. It would open as a new tab in Edge.

With PL1, I'm back to the old way of it opening as blank page in Edge, which then opens the page in seperate Edge webview2.

I have attached a screenshot

Regards

Tor

 

[FrankKrauseGUI]

Hello Tor,

that is quite strange (unless you have turned off the feature via registry value UseBrowserNoSSO as per SAP Note 3258944).

I recommend that you open an incident on component BC-FES-CTL for this.

Best regards,
Frank

[FrankKrauseGUI]

Hello Dennis,

your command line is wrong.

Correct would be
C:\Program Files\SAP\FrontEnd\SAPGUI\saplogon.exe" /LSXML_FILE=C:\ProgramData\SAPINI\SAPUILandscape_ALL.xml

The "=" character is missing between the parameter name and the value.

Best regards,
Frank

[nanda87]

Hi frank.krause - thanks for the blog!

Can you please share timeline for horizon theme on SAP GUI (assuming it is on the roadmap) ?

 

thanks

Nanda

[FrankKrauseGUI]

Hello Nanda,

Horizon presently undergoes a design update. I cannot share much about this, but one of the reasons is that in SAP GUI for Windows we decided not to implement Horizon in the present state due to the change of a very important paradigm: Disabled elements have always had a grey background color ("greyed out"). But in the present Horizon version this is the other way round: Enabled elements have a grey background color. This would completely confuse almost all SAP GUI users in my opinion.

Once the specification has been updated, we will start working on an implementation of Horizon in SAP GUI for Windows. However, since implementing Horizon is a big undertaking and requires close cooperation between several teams, Horizon will have to be delivered in a new SAP GUI for Windows release: SAP GUI for Windows 8.10. And at the moment we have not even defined the exact shipment date for this release, yet. I expect 8.10 to be shipped in late 2025.

Best regards,
Frank

 

[manuf]

frank.krause

Hi Frank,

I installed today PL 2 after it got in available. With the workaround active ( "UseComHjkngWA" = "0" ) I can open SAP Logon 64 and see in the About... section that indeed I have installed PL 2.

But if I deactivate the workaround ( "UseComHjkngWA" = "1" ) I cannot load SAP Logon anymore.  So don't think the fix is working for all cases.

Windows 11 Enterprise / Version 21H2 / OS build 22000.1817

regards,

Manu

[FrankKrauseGUI]

Hello Manu,

fortunately, your interpretation is wrong.

First a general statement: The registry value UseComHjkngWA should not be used anymore at all, because there is no need for it.

In patchlevel 2 we changed the semantics of this registry value:
0 (or not available) - new protection mode active
1 - protection mode from patchlevel 1 active
2 - protection mode from patchlevel 0 active
3 - no protection

So, setting this to 1 will not turn it off, but instead turn on the old mode which is known to have issues with other security products.

Just delete the value completely and you should be fine.

Best regards,
Frank

[manuf]

Thanks, Frank! all good now. I see Note 3320385 was updated to not include the workaround part.

[former_member675015]

Dear SAP expert

My SAP GUI version is 8.00 32-bit latest patch.

The operating system is Win11

My computer is a laptop with an additional external monitor and a resolution of 4K.

When I connect the monitor, open the SAP GUI, run SM37, and check the error log, everything is normal!
But when I disconnect the monitor and only use the laptop screen, create a new SAP GUI window, run SM37 on it to view the error job log, and there will be an exception. The system will be stuck and unable to operate normally. Only by closing the pop-up box or pressing ESC will it return to normal!

But once I reconnect the monitor, the previous error will not reappear!

In fact, not only 32-bit GUIs, but also 64-bit GUIs have this situation, and this situation only occurs in GUI800, GUI770 does not.

The transaction code with exceptions is not just SM37, such as running STMS and executing transmission requests!
Please see the attachment for the video I recorded

Regards，
Leon.Scot.Kennedy

[FrankKrauseGUI]

Hello Leon,

this is not the right place to analyze product issues.
If the issue is reproducible, please report an incident in the SAP support system on component BC-FES-GUI.

Best regards,
Frank

[former_member675015]

YES，I  have report and incident!

333803 / 2023 SAP GUI 800 has issues with multiple monitors

[josueoteiza]

Hi guys, In SAP GUI 8.00 64 bits, patch 2, running over windows 10, when i try to check a join in SQ02 transaction, it crashes, and it shows CNTL_ERROR dump in ST22

[FrankKrauseGUI]

Hello Josue,

this is likely solved by application note
3300460 - SQVI/SQ02: Dump RAISE_EXCEPTION, CNTL_ERROR mit SAP GUI 8.00

Best regards,
Frank

[donald_guo]

Just FYI Georgios,

64bit Crystal Reports ALV adapter is now available, see:

1. https://launchpad.support.sap.com/#/softwarecenter/search/CRBSAPPS10


2. SAP Note 1353044 - Installation Guide CR Viewer for SAP Business Suite Apps

 

[former_member839384]

Thank you very much for the information!

We will download and test it.

[yatinbhatt]

Hi Diego

Sorry but I have not found any solution here. There was a new patch 2 released after this , but behavior is still the same.

I am also observing lot of crashes randomly.

Sometimes if you have 2-3 windows for the same system, and you are in , e.g. SM66 clicking refresh , suddenly the window changes to one of the other screen. So random rendering issues as well.

I hope that SAP resolves some of these issues soon. It is no where close to roll out for everyone in the company.

Thanks
Yatin

[ChristianGünter]

Hello frank.krause,

Note 3099670 describes how to enable remote debugging features for Chromium based Edge Control. Unfortunately I failed to do that. How is that supposed to work? Can we find more information about that somewhere?

Are there other means to analyze problems in HTML applications running inside SAPGUI using the new chromium based edge control? E.g. problems like this in abapGit.

Best regards,

Christian

[FrankKrauseGUI]

Hello Christian,

I just tried to use the remote debugging feature, but for some reason I cannot get it working either.
However, I am not the expert in this area and have therefore asked a colleague to check what is going on.

As soon as there is an update, I will let you know.

Best regards,
Frank

[former_member496242]

Hi Christian,

Update the registry as per note 3099670(added screenshot for reference) and follow below steps to verify remote debugging feature.

Activating the Edge Control in SAP GUI

• Start SAP Logon and start the options dialog. In options dialog navigate to the page "Interaction Design" -> "Control Settings".


• You see a page with some group boxes including a box "HTML Control" which contains a combo box called "Browser Control".


• Via the combo box control select the value "Edge (based on Chromium)”. Click "OK".

Testing remote debugging feature

• In SAP GUI, run any transaction which uses HTML control.


• To test whether the remote debugging option is enabled or not open command prompt and check if the port is in listening mode by giving the command (I am using port 8081)
  netstat -na | find "8081".


• Now open Edge standalone browser on the same machine and enter the URL:
  edge://inspect/


• Once the URL is executed, the displayed page contains some options including a checkbox "Discover network targets".


• Click the button "Configure" next to the "Discover network targets" checkbox.


• A popup is displayed, on the popup enter "localhost:<PORT>" like localhost:8081 if you did not change the port and click the "Done" button.


• The popup is closed, after a while a list of URLs which belongs to edge control embedded inside SAP GUI is shown in the "Remote Target" section.


• Click the "inspect" link below the respective URL belonging to the page displayed in the SAP GUI window.


• The mirror image of the page displayed in edge control is seen inside a new Edge popup.

[ChristianGünter]

Thanks a lot Raghavendra J!

I'm now able to do remote debugging. My problem was that I accidentially maintained Port 8081 as hexadecimal instead of decimal.

[ChristianGünter]

Hello frank.krause,

even with latest patch level 3 for SAPGUI 8.0 we still face severe problems with new chromium based browser control within abapGit which relies heavily on HTML control.

It's documented in this issue.

What is the best way to draw SAPs attention to that? Note as almost all abapGit development is done by voluntaries on their own systems, therefore open a case is not easily if at all possible.

Best regards,

Christian

[FrankKrauseGUI]

Hello Christian,

as you know, it is typically impossible to analyze a complex issue if you cannot reproduce it.
Therefore, in any case, it would be best if an incident could be reported.
If this is not possible, then it is a bit of guessing and hoping.

In patchlevel 3 we consumed a new API from Microsoft for fixing the issues with custom URIs (sapevent). Unfortunately, there is a issue with this API and there are also issues in the way we implemented it.

1. The new API is not compatible to what IE did. The schema "sapevent" is not transmitted to us as it is in the page, but it comes as lower case (and we convert then to upper case). This is overall a big issue, but we are in contact with Microsoft regarding this. The problem in the end is of course that often ABAP applications match this pattern in a case-sensitive way.


2. We remove "/" from URLs provided as parameter values in sapevent. This is an error that we already know about and that we are currently fixing in our implementation.


3. Another issue is that parameter values are also converted to upper case by us. This causes further issues with applications which expect a certain case. We are also working on this.

If the impact on your work is too big, there is a registry value to restore the behavior from patchlevel 2 and older versions, but then again the old issues will occur. We are also thinking about creating a hotfix for patchlevel 3 as soon as at least the issues on SAP side have been fixed.

Best regards,
Frank