SAP GUI and BEx Frontend must have the same version (for e.g. SAP GUI 7.40 fits to BI Add-On based on 7.40) Its strongly recommended to use the latest patches of SAP GUI and BEx Frontend. Office 64 BIT versions are NOT supported for BEx tools, see note 1995532.
![Sap gui 7.40 patch 12 download Sap gui 7.40 patch 12 download](http://4.bp.blogspot.com/-Ywa5AIOAXd4/VVjIZ37g_QI/AAAAAAAAKhI/0FrJt33qMKc/s1600/sap%2Bgui%2B740.jpg)
760 patch compilation 1 0 latest patch 0 This table shows the latest patch level of SAP GUI on the last line, and full compilations and their patch levels. I will try to change the information as soon as it is available. Hotfixes require the relevant patch to be installed first! How to download?
I always laugh and laigh when trying to download this from the SAP Service Marketplace. You have to navigate from window to wndow, none of the links are intuitive, and you end up with four different web pages open. Someone coming into the SAP service marketplace for the first time would think to themselves “this company clearly does not understand the importance of cloud based systems” In the same way, the other day I tried to access the SCN on my smart phone and it came out really small, unlike a lot of web sites which adapt themselves to the dveice at hand. So the same person seeing this for the first time would say “this company clearly does not understand the importance of mobility” Just to round this off, whilst navigating the SCN you often get the big dlalys whilst the “loading” barber shop pole spins round and round, sometimes quite a long delay. So that same new person might say “this company clearly does not understand the importance of fast database access” Now, I’m being really cruel here, but web sites are a customer’s (or more importantly a potential customer’s) view of a company, and do SAP really want even the smallest chance of a first time viewer coming away thinking “this company does not understand the cloud, or mobility, or databases”? According to the OSS note the first patch is due the middle of December and I cannot wait. If I had written something with so many bugs and it had gone into production, I would be sacked, and then the person replacing me would be instructed to get a fix into production as fast as possible, the same day hopefully.
![Sap gui 7.40 download for windows Sap gui 7.40 download for windows](/uploads/1/2/5/6/125623895/224005170.png)
There was clearly no testing done at SAP before this was released, common in software firms these days – probably what they were expecting to happen – which did happen the very day of the release – is that the obvious bugs were reported by dozens of foolish users like me who download new things to see what they are like, knowing full well they will not work. I have no doubt that by the end of the first week the developers inside SAP had fixed at least the most glaringly obvious bugs. So, if the first patch had come out the week after the 740 GUI then there would not have been such a torrent of abuse on the blog announcing the new 740 GUI. The banter started off light hearted but as it became clear the myriad of problems were not going to be fixed the tone turned downright nasty, so much so that the thread had to be locked, as the abuse was getting personal. The problem is being inflexible with a plan. The schedule was to release the patch in December, so that plan is fixed in stone. It does not matter there are urgent fixes needed – December is the plan, so December it will be.
This is somewhat like having a battle plan to bomb the hill where you think the enemy are, and on the day of the battle your scouts tell you the enemy have moved, they are no longer on the hill, but you say “bomb that hill anyway because that is the plan”. I’m curious to know, what has changed that the base must be installed again before applying latest patch? Originally I installed 7.40 base, then later applied patch 2 when it came out (just happened to skip 1), then patch 4 when it came out (happened to skip 3). Why not skip 5 and apply 6 now? Sure, I can try installing base again then try to apply patch 6.
But, even if that works, this does not look good for user deployment. Is this the required procedure now, to reinstall base and then apply latest patch? Hello Florian, are you running Personas 3.0? I think this particular Gui version has a problem with Personas’ usage logging. Disable usage logging ( transaction /personas/admin - Goto Menu – Analytics - Measurement Analysis: in the shown screen there should be a toolbar button “Disable Usage Logging”.) and see if the problem disappears.
Of course, there could be another Personas script (onLoad/onAfterRefresh) that causes this problem, but then it would not occur for all transaction and espectially not if not flavor is applied. Best Regards, Clemens.
Careful with patch level 9 if you’re using the MRS planning board! We’re on MRS 800 and after installing the newest PL resources and assignments are not visible anymore. It is not an authoritzational problem or anything of the kind – it has to be caused by the SAP GUI: Yesterday I was using PL8 on the same computer and it worked. To make double-sure I connected from two different VMs today. One is still on PL8 where it still worked. The other is still on 720 PL4 and worked as well.
Only 740 PL9 is not displaying any resource+assignment data. Update: PL10 is out now and with that MRS is working again. I am not sure that I fully understand your problem, but with the installation server (NwSapSetupAdmin.exe) you can make your own single.exe file installation, and include your own saplogon.ini there. Also the new versions have option to take the.ini file from a network resource, every time they start (and/or cache it), perhaps even through HTTP. If you want to merge 2.ini files, I guess copy/paste would work, not sure. Meanwhile check my tool – – solved another problem.