One of the biggest frustrations I’m encountering with Web Dynpro (and especially BSP’s) is that they don’t work on web browsers. So far, I’ve been able to get my simple applications working just fine on Internet Explorer (version 9), but nothing works on Firefox (version 15), I can’t get anything to work on Safari (5.1.7), and only my BSP has been able to run on Google Chrome. So today I wanted to discuss some of my finding when it comes to Web Dynpro browsers and what is supported. There are numerous OSS Notes that I’m still sorting through, including:
In addition: service.sap.com/PAM talks about the availability matrix. If you navigate to the netweaver, and punch in your specific version (7.01, etc), you’ll see the web browsers that are supported.
I’m still sorting through all these notes, but to provide an application that can be given to your customer is increasingly difficult. How do I tell a customer, please use my web application, but you can only use internet explorer. In addition, there are a number of people (myself included) that upgrade to the latest browser when it comes up. So this means, there will always be a percentage of time that someone won’t be able to access my application. I welcome any experiences that people have had with this. Maybe I just don’t have the right support parks. For example, I’m using ERP 6.0 EHP4, on Netweaver 7.01. So far, this states that I can use Internet explorer (up to version 9), and Firefox (up to version 10). Now, if I was using Netweaver 7.3, EHP1, I’d have access to safari & chrome. Again, this is subject to being on the latest netweaver support pack. Short story, I’m a little concerned with selling a Web Dynpro application, because I’m afraid I’ll spend all of my time troubleshooting what releases are supported for the given clients.
Just to throw it out there… BSP’s are even worse. Since SAP has stopped supporting the technology. My Rapier application works fine in internet explorer and Google chrome, but apparently the functionality is too complicated and Firefox & Safari do not support it. My problem is that I don’t even know what functionality isn’t supported. I do a lot of dynamic things in my BSP, so it’s a lot areas to focus on. The question for me becomes, do I focus on correcting the old technology, or just convert it to web dynpro (easier said than done… but that’s another story).
Oh well, gotta do it, but at least I’m getting a better idea of what is and what isn’t supported.