Skip to Content

With TechEd Barcelona coming up next week I was preparing my questions and things I want to find out while I’m there. Following my previous blogpost on the subject (New SAP UI Roadmap – What’s changed since 9 months ago?) and the positive comments I got on it I thought I’d write another one with my findings. I compared the UI Roadmap of April 2015 with the most recent one (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0e5d250-3e9a-3010-97a0-a0c7f48b5bd8?QuickLink=index&…).

Overall

There are no changes to the Table of Contents. No mentions of new technologies and no current technologies have fallen off. Of course it would have been a big surprise if there were any. There are also no changes to the UX Strategy apart from some new images and textual fine-tuning. SAP is going strong with the new-renew-enable paradigm. The key UI technologies and how they relate to each other have not changed either.

Trends

Screen Shot 2015-11-06 at 11.18.02.jpg

There’s been a little shuffle of the trends on the left side and one addition (highlighted). I do think it’s an important addition and I recognise it to some degree. People see the power of simplicity in Fiori apps and want that for their processes too. After implementation of the basic (and indeed simple) Fiori app I too often am requested to build a list of features into an app that make the app more and more complex. Before you know it you’ll be building a complete transaction again and that’s something you should not want. If you’re building a Fiori app, always keep in mind the Fiori principles (simple, coherent, responsive, role-based and…I always forget one…ah yes: delightful). Especially the simple and (thus) delightful often get overlooked. If you need to build a transactional app, consider one of the other key UI technologies, such as WDA/FPM.

SAP UI5


April 2015 October 2015
Screen Shot 2015-11-06 at 11.29.55.jpg Screen Shot 2015-11-06 at 11.27.08.jpg


By far SAP’s hottest UI technology these days. You can tell from the many shifts of items in the columns and the continuous adding of new items. What I think is really great is that the transactional enablement of UI5 is shifted from Future Direction to Today. A lot of steps have been made in that area and I expect to get more details at TechEd. Something to watch is the use of Smart Templates. This will help to make the creation of new Fiori apps a lot easier. Much needed of course considering that S/4HANA will be completely Fiori. You can imagine the need to convert all the current screens into simple Fiori apps. it’s good to see the Demo Kit and documentation are getting improvements as well. Layered configuration / personalization is also very welcome. It will give developers the abilities to provide (key) users with options to optimize their app to their liking like we know from WDA/FPM (I imagine).

Future Direction seems stable but the 3 remaining items in there are very generic. On the next slide you see some elaborations on the subjects. For instance for new controls: “Tree, Tree Table, Analytical Chart and many other control improvements”. I know that Tree Table was a customer requested feature and I’m curious to see how they will make it happen and if it will work for mobile.

SAP Web IDE

Screen Shot 2015-11-06 at 12.43.52.jpg

On the Description slide in the latest roadmap a couple of lines were removed. E.g. from the Key capabilities list: “Embraces “open source” framework(s)”. It makes you wonder whether SAP decided that they’re not embracing them anymore. My educated guess is that they haven’t but just thought it’s not really a key capability of the Web IDE. From the Benefits list we see that the line “Enables business experts and designers* via highly efficient tools” is removed. With the beta of Build (www.build.me) released you would think that the (planned) prototyping capabilities of Web IDE will be shifted to Build (in that case I’d remove “prototyping” from the tagline). Why SAP decided to release another tool instead of integrating it with with the Web IDE puzzles me and I’d like some clarification on that decision.

In the previous roadmap a slide was dedicated to the building of new apps and one to extending existing apps. These slides are gone in the newest roadmap (presumably because they were not adding much value on top of the Description slide) and new slide about Web IDE Plugins was added.

Screen Shot 2015-11-06 at 12.28.00.jpg

The fact that the Web IDE is a modular platform (much more than merely a tool) is one of its biggest benefits IMHO. You can even add your own plugins allowing you to add your own features to the Web IDE. The graphical viewer of the OData Model Editor was a much requested feature and I’m happy that they’ve added it. Next step hopefully is to the ability to edit the model in the graphical view.

Floor Plan Manager / Web Dynpro ABAP (FPM/WDA)

April 2015 October 2015
Screen Shot 2015-11-06 at 13.43.17.jpg Screen Shot 2015-11-06 at 13.44.14.jpg


Many think that SAP UI5 will replace Web Dynpro ABAP eventually. I’m still not sure whether this will happen or not but based on the UI Roadmap I see no pointers in that direction. For instance the “Tighter integration of SAPUI5” was and is still in the Future Direction.

The Future Direction for FPM/WDA has not changed but some of the planned innovations have been realised today such as the integration with SAP Fiori and the implementation of a (first version) of Screen Personas for WDA/FPM. Keep in mind that there are still WDA/FPM applications being used in e.g. Simple Finance (and I’m sure at S/4HANA as well). At first glance (which is a Fiori launchpad tile) you might think it is all Fiori/UI5 but in fact a lot of applications are still based on WDA/FPM. Having a tighter integration (such as intent based navigation) is in that case of much value, allowing contextual navigation from one object to another without limitations, regardless of the UI technology. I said it before and I’ll say it again: Web Dynpro ABAP is going strong and it is here to stay.

Web Client UI Framework


April 2015 October 2015
Screen Shot 2015-11-06 at 14.39.31.jpg Screen Shot 2015-11-06 at 14.40.10.jpg


Dear to my heart, although I haven’t touched it in quite some time now. I see only 2 planned innovations realised (Open links in new tab/window & Quick navigation between search criteria). Furthermore I guess they wanted to throw me off by shuffling and grouping some texts but you don’t fool me SAP! 😉 Honestly I don’t see many things realised and that makes me wonder about the amount of effort to be invested in on-premise SAP CRM. Especially with the addition of hybris to the cloud suite of SAP it makes you wonder whether there will ever be a CRM 7.04 or 7.1. Looking forward to discussing this with my peers at TechEd (especially in Expert Networking Session EXP27289 (SAPCRM meetup by Gregor Wolf)).

UI Theme Designer

For the UI Theme Designer one benefit was added: Apply corporate identity. Self-explanatory I’d say. No doubt a much requested feature.

As for the roadmap:

April 2015 October 2015
20151107 09.32.04 screenshot.png 20151107 09.32.28 screenshot.png

The Integration with Web IDE has been realised and is available as a shortcut from the WebIDE Home Page. There are a couple of new features in the Today column. On the other hand I see no features moved from Planned Innovations to Today. In fact one of the features (Integration with Git persistency for HANA Cloud Portal) is pushed back to the Future Direction. Perhaps a shift in priorities due to customer feedback.

SAP Screen Personas

April 2015

October 2015
20151107 09.47.16 screenshot.png 20151107 09.47.23 screenshot.png

The purpose of this tool is clear: improve productivity through personalization of ERP screens. A lot of work went into realizing the integration with other SAP UX Solutions (much like you see happening with other UI technologies (e.g. WDA)) and I think that is a good sign. As long as companies are still using the ‘old’ ERP screens, SAP Screen Personas is a valuable addition to your toolset. Something to watch is the future planned Mobile rendering. That means ‘old’ ERP screens will be somehow be mobilized. That could mean for instance reducing (a lot of) fields on VA01 and then be able to create a sales order on your iPhone. Looking forward to seeing how this would work out. Another very valueable planned innovation IMHO is the Usage analytics. This is of direct benefit to UX researchers/designers saving them a lot of time interviewing key users as they can (hopefully) directly see the most used features on a screen, allowing them to better design new screens.

SAP browser support

One new browser will supported as from SAPUI5 version 1.32 onwards: Microsoft Edge.

SAP NetWeaver Business Client

April 2015 October 2015
20151107 10.09.53 screenshot.png 20151107 10.10.00 screenshot.png

One of the last products to have NetWeaver in its name (I feel another name-change coming up!). Actually a lot of work was done in the past 9 months. Support for various platforms was realised as well as integration with Screen Personas 3.0. Seems all of the currently planned efforts are put into enabling NWBC for SAP Fiori UX which sounds logical. Not sure I’m reading this right, but “SAP Fiori with SAP GUI native experience” doesn’t sound like something to look forward to 😕

Portals & SAP UI client consolidation plan

New compared to the previous roadmaps is the addition of the roadmap slides for the Enterprise Portal (EP) and SAP HANA Cloud Portal. As such I cannot determine a delta but the trend you see in other areas is happening here too: integration with the Fiori launchpad and the Web IDE.

20151108 08.33.53 screenshot.png

There’s no delta here apart from the fixing of the description. But I think it is still an important topic because of the many entry points you can now choose from. What the user will see is the Fiori launchpad. How this is implemented (in a browser, NWBC, EP, etc.) is up to the desire of the customer. In my opinion there are (still) a lot of flavors to choose from and you’d have to be an expert to give an advice about which one you should choose. I had hoped for a more concrete path towards the ‘portal of the future’ by now. Right now it seems everything will remain as it is (apart from that it will all look like Fiori) and I think that’s not very good. Ideally I’d like to see one product (e.g. SAP Portal) with different deployment options (e.g. Cloud, on-Prem full & on-Prem light) much like was done with the Sybase Unwired Platform, Sybase 365 and Syclo Agentry into SMP. Take the best features of each product, bring them to the other products and simplify the way you offer it to customers.

SAP Fiori launchpad

April 2015 October 2015
20151108 09.14.50 screenshot.png 20151108 09.15.03 screenshot.png

In any case this is at least the face of the ‘portal of the future’. Lots of work is done in this area and I hope to see a lot of it next week. From experience I can say that the simplified setup, config and admin processes will be welcomed with open arms by a lot of customers. Also the Push notifications will come in quite handy. Looking forward to learn how this will be implemented and what is required (perhaps SMP, ABAP Push Channels?). I can imagine that the Enhanced launchpad user experience with SAP Fiori UX 2.0 concepts will be sped up because from what I’ve heard people are extatic about Fiori 2.0.

I’m not going into the Specialized UI Technologies (Visual Business/Enterprise, Adobe IF & WDJ) as very little has changed in these areas (yes, WDJ is still dead 😉 ). The other topics at the end (SAP Fiori, SMP & Gateway) have their own roadmaps. Perhaps food for another blog!

Thank you for reading this blog post so far. I you have read it, please approach me at TechEd next week and tell me what you thought of it. If you haven’t read it, approach me anyway 🙂 Don’t forget to take a picture and enter the Catch a Mentor and Know a Mentor Missions

To report this post you need to login first.

6 Comments

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

  1. Robin van het Hof

    Great summary, and I think you hit every nail in your observation.

    WRT WebIDE / Build, maybe the two (and more?) will eventually converge in the future. At least the open structure of both could hint in that direction.

    (Yes, I hate to admit, but indeed, WDJ is indeed in a deep coma — as is Visual Composer IMO)

    (0) 
  2. Jean-Yves Guyomarc'h

    Another great post Roel!

    But for the sake of WEBCUIF, I was really hopping that you would be too busy with TechEd to blog 😛

    A lot of our new developments for this year were not quite ready for this Road Map update, but have been released in the meantime (Blue Crystal Theme, new Progress Indicator THTMLB Tag, Direct URL for Saved Searches, Integration with WPB) and some are almost out of the wood (Theme Design Integration, Design Layer Get/Set).

    So a 9 months comparison would have been much better than a 6 months comparison for us 😉 .

    (0) 
  3. Tom Van Doorslaer

    oh btw: NetWeaver Business Client is now branded as the SAP Business Client (with the release of version 6.0)

    Want to know more about the key role of the Business Client? Join me at TechEd for session #EXP27273 🙂

    (0) 
  4. Ingo Deck

    Hi Roel,

    thanks so much for another great blog and comparison to previous road map versions. I really love that external view on our document, the things you see… as sometimes when producing that road map you get pretty blind to some of the small details.. so always happy to read your blog.

    Have to admit that almost while you wrote your blog we publihed a new version of the road map on Nov 8th on SCN and some days before that on the service marketplace.

    This was an exceptional situation where we had only couple of weeks between 2 versions as the corresponding releases (SAP NW UI AddOn) anyway have been closer to each other and we had a little delay with the previous one..

    The new road map indeed has some changes as you for sure will notice.. besides the standard road map slides updates you will notice some changes in the introduction part to the strategy, no real change more an evolution. And we also changed the Clients chapter a little, putting the FLP more into focus and adding a new slide on how FLP and Portal as well as Business Client relate to each other.. and – you have been totally right on that – with the version 6.0 the SAP NetWeaver Business Client has been renamed to SAP Business Client – so the last NW is gone 😉 in our names.

    And I am sure you will find lots of more mentionable changes in that new version. By the way.. of course I will not mention any official dates, but the next road map update will not be available before end of Jan/early feb 2016.. so this short cycle this time really was an exception.

    Unfortunately I didn’t have a chance to meet you at TechEd in Barcelona, was pretty involved in end user testing.. but hope you had an insightful event!

    Kind regards

    Ingo

    (0) 
  5. Julie Plummer

    Hi Roel,

    Hats off from me too, for this really thorough analysis. I will leave much of the commenting to wiser heads, but just 2 points re NWBC / SAP BC:

    1. OK, Ingo beat me to it, but just to confirm: Yes, SAP NetWeaver Business Client (NWBC) has been renamed to SAP Business Client (SAP BC), to comply with other products, as you predicted.

    2. Re:

    “SAP Fiori launchpad with SAP GUI native experience” …OK, maybe I should rephrase that: “Launch SAP GUI native transactions from SAP Fiori launchpad” – this is only possible out of the box with SAP Business Client 6.0. (eg From standalone Fiori launchpad, you get “Webgui”). – Sounds better? Doesn’t it 😉 ?

    Best wishes,

    Julie R Plummer.

    (0) 

Leave a Reply