FeatureImpact when Fiori Features are not activeAutomatic wide rendering of UI elementsNo element is automatically enlarged. Screens are displayed just like in older SAP GUI themes.Bigger screen metricsThe screen metric (line height) is smaller than in standard Belize to show a good amount of data on the screen also in applications which have not been adjusted to Belize. However, it is larger than in themes like Blue Crystal.View SwitchThe View Switch is not available. Items in a View Switch are displayed as buttons in the header toolbar.Displaying buttons with textAll buttons in the header of the main window and in the footer of popups are displayed as specified by the application.
![](/uploads/1/2/8/1/128177421/666180011.jpg)
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight. This guide is written with an intention to help those who are looking and trying to Install SAP GUI 7.20 in Mac OS X 10.9 Mavericks platform and ended up with installing Windows OS in Mac machines due to limited or lesser information availability related to ‘Mavericks’ OS X & Java configuration steps.
Hello Frank,thanks for the response! I guess for web based applications it makes sense not having a menu and having new applications provide their main functionality in the toolbars is a good idea.
However, with Belize now being available for “older” non-S/4 ERP systems there’s still lots of transactions that heavily rely on the menu (and I assume in S/4 as well). So I would have liked it being included, possibly not enabled by default. (Looking at the screenshots the space seems to be empty anyways). Hello Sven,I am not responsible for SAP GUI for HTML and therefore my answer is not worth much, but as far as I can tell this will not come for any older SAP products in SAP GUI for HTML.At least one thing is certain: This cannot come in any older SAP Kernel release, because Belize was a massive development that would definitely cause a lot of problems in older SAP Kernel releases if it was downported.For SAP GUI for Windows the situation is different, because you are using the same SAP GUI version for all your connections. Therefore, we “only” had to take the existing Belize theme and make it compatible and look good for all products.Best regards,Frank.
Hello Sven,right, theoretically such a development would be possible in SAP GUI for HTML, too (for those SAP Kernels which already contain the Belize theme). However, you would still have to consider that some development effort would be required (new metrics for example) and that this would not be suitable for delivered releases. In SAP GUI for Windows we are doing all of this in a new release only and I believe this is the only feasible approach.But again: I cannot comment on the strategy for SAP GUI for HTML.Best regards,Frank. Hello Emmanuel,yes, multi-monitor DPI awareness is not contained in 7.60, but we have started working on this topic. Since there are a lot of places to be fixed, I doubt that we can downport such a feature into a delivered release, but we shall see.I’m talking especially about the last paragraph (titled “important update”) of note 2541592As mentioned in SAP Note 2541592 this feature is contained in SAP GUI for Windows 7.60.However, this has nothing to do with icons. This is just about the line height.The SAP GUI icons are displayed via an icon font since Blue Crystal theme and they are of course scaled. Even the old bitmaps in older themes are scaled – despite the fact that this is looking very ugly when using relatively high DPI settings.
And this is one of the main reasons why I strongly recommend Blue Crystal or Belize Themes when using DPI 100%.(Also, I never understood why the branding feature was never improved to be system-dependent)Because nobody asked for it. So far the branding feature was used to apply a brand image and this is typically not different per system.What is your concrete idea behind this question?Best regards,Frank. Hello Barbara,that is a more complex question than it seems, because the SAP GUI DVD includes multiple components which support Office.
Since I am only responsible for the core part of SAP GUI, I will only tell you about the SAP Desktop Office Integration (“DOI”) which indeed supports Office 2019 (however, the DOI also supports this in SAP GUI for Windows 7.50). See SAP Note 722513 for more information.We also have a document on the DVD (in folder “DOCU”) which lists all the dependencies to Office. I recommend that you check this document (“Microsoft Office Dependencies of SAP GUI 7.60 Components.pdf”) as soon as the DVD is available next Monday.Best regards,Frank.
Hello John,you will get this on the installation server (after importing the patch) or when installing on a PC which does not have SAP GUI installed, yet. The logic of NWSAPSetup is such that when you apply a patch it updates the installed components. The PDFPrint component did not exist in previous versions.We are presently discussing whether we could change the functionality so that when you lauch a patch on a workstation where the patch is already installed the component selection dialog is displayed. Then you could select additional components.Best regards,Frank. Hello Pragnya,I guess you are referring to the “Direct Selection” group box.If this is true: This is an application issue.The issue is more obvious in Belize theme due to the changed metrics, but even in Blue Crystal you can see that it looks somewhat “compressed”.
The Dynpro size check (SAP Note 570861) shows a sizing conflict on the screen that needs to be analyzed and fixed within the application.Regarding CTRL + A: We are not aware of this and I cannot reproduce this for example in input fields. Please report an incident in the SAP support system if you can reproduce the issue and explain in detail how to reproduce this. Before doing this, you may check whether CTRL + A is working in other tools, because in some cases other tools installed on the client are “stealing” certain keyboard shortcuts.Best regards,Frank. I have tried out SAP Gui 7.6 + NWBC 7.0 and i have encountered 2 issues. NWBC 7.0 crashes if the browser control is set to chromium.
BEX tools bundled with GUI 7.6 do not work. Hello Mahesh,in Belize theme you can show either the SID or the application server name, but not both.We have added the application server name to the entries in the dropdown in the system information area so that a user who realy wants this information can still get it. You could use the option “Show system name in taskbar button”, but that will only help you for inactive SAP GUI windows (because for inactive windows we display the title in the caption area as of 7.60 PL1 and the option adds the SID to the title).So for an activate SAP GUI window there is no way to display both SID and application server in parallel. The reason is that almost nobody needs to see both in parallel and permanently.Best regards,Frank. Hello Antonio,“System Dependent” is a theme based on Enjoy (family of enjoy, streamline and tradeshow themes). The theme is very old (1998) and it has severe technical limitations for example when working with high DPI (try it out – it is ugly). There are more than enough alternatives which are from my perspective looking much better, but that is of course a matter of taste, too.Additionally adding more and more themes to SAP GUI also comes at a price: More complexity and reduced performance as well as reduced maintainability.
If we add something new we also need to remove something old from time to time.Best regards,Frank. Hello Sven.thank you for the feedback.In “Belize without Fiori Features” no buttons are displayed in the footer at all, because we decided to keep the positions of all buttons at the top (to be as compatible as possible). I do not think we should move buttons into the footer when not running Fiori mode, because often the most important buttons would not be displayed in the footer (since the “old” applications do not specify which buttons to move into the footer) and the users would be confused.Regarding the buttons at the top:. The “More” button is the overflow button. Where else should it be placed but where the buttons that cannot be displayed anymore disappear?.
Exit and Logoff are the same buttons and are placed at the right together with the other generic functions (while the application specific functions are at the left). The less used functions for Cancel and Scrolling have been moved to the left area so that they are moved into the overflow first and the other functions which are in most cases more important stay on the screen even for smaller windows.What exactly is your proposal?Best regards,Frank. Hello Frank,thanks for your clarification.My proposal:Use more features from “SAP Fiori Visual Theme for Classic Applications”.And therefore I must correct me, concerning the button positions:.
For “SAP Fiori Visual Theme for Classic Applications” the Back and Exit Button are at the same position like “Belize theme without Fiori Features”. Only Cancel / Save button remain for the footer position.Probleme here is especially the actual position of Save button:At the same toolbar line and left from the Execute Button.Best Regards,Sven. Hello Sven,the problem is that SAP GUI does not know anything about the meaning of the buttons (and the Save button is not in all cases really a Save button). In Belize with Fiori features we provided these features to applications in order to let them decide what to do with the buttons:Without these features we will not be able to get things right for all cases.
And we cannot expect that all application across all supported releases would be adjusted, nor can we downport these features.This is why we decided to have this button sequence for application specific functions.Best regards,Frank. Krause,as ABAP developer I recognized a new behaviour in SE80 regarding keywords, which actually is a bagatelle, but nonetheless somehow annoying:While entering code, even with autocompletion of keywords, the new SAPGUI does not recognize them instantly as such. It may take the “Pretty printer” in order to highlight the keywords. If you would press “Enter” afterwards, SAP would loose the formatting of the previous line, additionally starting the same behaviour with the new lines entered.In formatting options of the ABAP editor all relevant check boxes are activated of course.Did you already encounter this issue or has someone reported something like that?Will there be a bugfixing in upcoming patches?The chat log at least does not provide any information about this.Thank you very much in advance!Best regards,Markus Amann. Krause,thanks for your reply and i’m sorry it took quite a while to respond.
In meanwhile we tested the new patchlevel 3 because OSS 2813505 sounded like a solution. And indeed, it helped. Keywords are highlighted as usual again.There’s a further error which has not been solved with patchlevel 3: again in ABAP-editor, when using autocompletion e.g. For class methods, the tab-position shifts to the left. Again: just a minor error.
Maybe a correction will be delivered within a later patch-level.Greetings,Markus Amann. Hello Community,I would like to provide a minor update on our features in SAP GUI for Windows 7.60.We originally planned to release this feature in the initial delivery, but during development a lot of challenges came up (like supporting this on older Windows versions). Therefore, we decided to delay the shipment of this feature until we are satisfied with the functionality and it works without limitations. This is now the case with patchlevel 3.
Import and export of SAP GUI settings (available as of SAP GUI for Windows 7.60 Patchlevel 3)The SAP GUI Options Dialog now supports the export and import of all relevant SAP GUI settings. This is for example relevant when a user receives a new PC and wants to take over the previous settings easily. The settings are exported as content of a password protected archive which can be transferred to the new PC and then be imported via the “Import” button. Hello Frank,we are about to roll out SAP GUI 7.60 SP2.We have following issues, where I didn’t found a solution.Issue 1:SAP GUI 7.60 PL2 (also with PL2 Hotfix 1 I tried both) crashes without any information (also by increasing of tracelevel) also the saplogon crashes at that time.Reproducing:After logged on in a SAP-System. If you try to save a list. SP01 – System– List – save–save. By pressing the last Save no popup appears with saving to filesystem (list with unconvertet, Text with tab HTML Format ).
SAPGUI and SAPLOGON crashes without any message.What is really curios. After crashing and you start saplogon again. And try it again it works. The list appears and you can save.If now than you stop SAPGUI (anyway stopping saplogon, or not stopping saplogon but closing sapgui) login again in a SAP-System and again trying to save a list it crashes again.Issue 2:Unfortunally I am awaiting information how reproducing the issue myself.When you start a transaction that opens Excel, Excel is open and contain the data needed. But there is no save button aktiv it is not possible to do anithing with the resulted excel-sheet.Do you know one of that issue, can someone look if it you can reproduce the issues?Additional information:I tried with a local installation. On Citrix I didnt tried myself, but users said it is the same issue. (actually don’t know if also on citrix it will work once after crashed like I described)Thanks in AdvanceSalvatore.
Dear Frank,we’re rolling out SAP GUI 7.60 PL2 and unfortunately we have faced some performance issues. The performance lack is not related to certain transactions or options e.g.
“F4 Help” or “ALV Grid” and also not very dramatical. However all in all the GUI 7.60 is slower than the 7.40 or 7.50 version. I wonder if SAP can give us a recommendation on how to configure or set up the 7.60 to get the best performance? We are using SAP Signature Theme as a default theme.
Appreciate your help.Thomas. Dear FrankThank you for providing your insights into the GUI with this article. Reading through the comments it’s interesting to read of applications areas with the screen rendering and functionality mis-behaving or illogical menus.As a customer, I raise defects with SAP Standard code for them to be fixed. For me the Belize Theme is a fundamental in the direction of travel so if the screens are misleading, broken or failing to deliver on the intended productivity it’s reasonable that they are fixed.With Reference to: –looking at the proposed benefits on page 5, it states “It speeds up the user’s workflow’ as it is ‘easier to find what you are looking for’. And on p.8 it states ‘helps users to focus on the most important tasks’.From reading your comments this is for SAP Application Teams to take ownership for and fix. And I am seeing that in some areas, but not all.For example, the Workflow Transaction SBWP when you highlight a line in Belize it is no longer clear to identify the selected line compared to Blue Crystal. I’ve been told to change to Blue Crystal for our organization.
And also to register for a Customer Influence event that appears to be neither open nor upcoming.My question is what guidance and engagement and expectation has been gifted to the Application teams to deliver on the expectations of the Belize Theme. So as customers we can refer to that guidance, as it feels like it’s not the preferred strategic choice when raising a defect.Thanks for any further information to help genuinely and consistently improve the UX with Belize when it’s highlighted from customers.Kind RegardsCheryl.
![Sap gui for mac 7.50 Sap gui for mac 7.50](https://www.worksoft.com/wp-content/uploads/2018/04/sap-before.jpg?v=4)
I recently installed SAP GUI on my MAC, OS yosemite. Dear allI just setup SAP GUI on my Mac as per the instructions given.For my sap logon details as below: SystemApplication ServerInstance NoIDClientECC40EH6800, I setup the connection as below:conn=/H/xx.xxx.xx.xxx/S/3299/H/saperp.getraind.com/S/3240However, I get the below error when I try to connect.
![](/uploads/1/2/8/1/128177421/666180011.jpg)