SAP Fiori for SAP S/4HANA – Top 10 Myths & Misconceptions to Avoid
Latest Update 20 March 2020: As of SAP S/4HANA 1909, certain classic UIs are touch enabled and will support some mobile devices (think touch enabled laptop/tablet). Misconception 4 has been updated for this change. For more details, supported browsers/devices, and restrictions, refer to SAP Note 2700517 – Mobile device support for Unified Rendering based frameworks: Web Dynpro ABAP and SAP GUI for HTML
Latest Update 16 October 2019: Updated for SAP S/4HANA 1909. Added new links to new innovation videos, and included links to latest blogs. Updated links to official documentation. Updated and added diagrams, e.g. for Fiori implementation experience, business role to homepage, etc.
Latest Update: Updated for SAP S/4HANA 1809. Links to the updated UI Technologies Guide, Fiori Launchpad Guide, developer requirements for SAP S/4HANA 1809, and Performance improvements in 1809 have been included.
In the SAP S/4HANA Regional Implementation Group we are privileged to gain insights into & feedback from SAP S/4HANA projects across many customers worldwide. This helps us to see what’s working and what’s not, so that we can make the journey to S/4HANA smoother for everyone. Even though SAP & its customers are now several versions into the SAP S/4HANA journey, we still come across several myths and misconceptions around SAP Fiori in SAP S/4HANA that hinder the journey to S/4HANA for customers. In this blog you will learn how to identify and avoid the top 10 most common misunderstandings.
When it comes to myths and misconceptions, forewarned is forearmed! As a customer or partner, myths and misconceptions are stumbling blocks that hinder your journey to achieving your strategic goals for digital transformation with SAP S/4HANA. Those stumbling blocks can manifest themselves as missing project skills & resources, unplanned activities, and unnecessary time wasted in raising & resolving issues via SAP Incidents.
Most myths and misconceptions around SAP Fiori for SAP S/4HANA are best avoided by giving them due consideration in your project planning and project team enablement. Knowing up front what myths and misconceptions you are likely to face, will help you make sure your S/4HANA project is better estimated, better staffed, and your project team is better enabled. Even if you are mid-project and have already fallen foul of some of these, understanding these myths and misconceptions can help you redirect and refocus your efforts towards achieving better outcomes sooner.
These are the top 10 myths and misconceptions you want to avoid:
- You can use SAP S/4HANA without SAP Fiori
- All SAP Fiori and SAP S/4HANA UX is active out of the box and/or Activating SAP Fiori is a purely technical task
- There’s a SAP Fiori app for every SAP GUI transaction
- Fiori Visual Theme converts SAP GUI transactions and Web Dynpro ABAP apps into SAP Fiori apps
- SAP Fiori apps should support every feature from the equivalent SAP GUI transactions
- All you need to do is select the Apps, it’s up to the User to organize their Home Page
- Everything will run on mobile devices without any extra thought or effort
- Fiori developers from Business Suite or Suite on HANA are ready to develop on SAP S/4HANA
- HANA means never having to do Performance Tuning ever again
- Assuming User Experience is a minor &/or technical part of your SAP S/4HANA project
You can find more on each of these below. Short on time and looking for how you can prepare your project team so they avoid these? A good place to start is the Getting Started section of Fiori for S/4HANA wiki and the Essential Roles for SAP S/4HANA Fiori projects blog (and attached summary presentations per project role).
1 – You can use SAP S/4HANA without SAP Fiori
Technically true … provided you are ok with severely limiting the business value you derive from your SAP S/4HANA solution.
Why? Well most of the business innovations of SAP S/4HANA, those that bring you the best digital transformation benefits, are delivered in SAP Fiori, such as:
- New innovations, such as machine learning, CoPilot, increased automation & exception processing,e.g.
- New insight to action paradigm, i.e. embedded analytics aligned to transactional processing, e.g.
- Supervise Collections Worklist
- Understanding insight to action app to app navigation
- Tip: There are now over 50 SAP Fiori Overview page dashboards available for SAP S/4HANA 1909!
- New/changed business processes, simpler, more efficient, and offering greater business control
- E.g. Flexible Manage Workflows, which lets the business control their own approvals without needing IT or a workflow developer
- New user experiences – simpler, easier, faster, and on mobile devices
- E.g. Pick by Cart for Warehouse Operatives
The Fiori Lighthouse Scenarios and Selecting Fiori apps blogs give more examples of these and how they impact various business roles. You can find more examples to convince your project sponsor and stakeholders in these resources.
Without SAP Fiori, you will still get some great benefits from faster analytics and of course the power of the HANA database, but with SAP Fiori you can do so much more.
2 – All SAP Fiori and SAP S/4HANA UX is active out of the box
All Fiori and S/4HANA UX is installed as part of your S/4HANA solution. However there are some activation and configuration tasks you need to complete. Why?
There are now over 1000 (1K) Fiori apps available for SAP S/4HANA across approximately 140 Business Roles. It’s a good idea to start somewhere (some customers start with as few as 20 apps), but you might not be ready to turn on all of those apps on day 1.
In other words, it’s your digital transformation journey and your organizational change management journey, so you will need to decide:
- Which business processes and business roles will be improved and when
- Which apps should be available for use now vs. later (or maybe even never)
- Which business users will access which apps
- In which situations will they use those apps – in which use cases and in which working environments
- And which devices will they use
All of that affects which apps you will need to activate, configure, and test. Anything you don’t use should be turned off, i.e. deactivated. Why? Controlling your app whitelist to only what you need:
- Reduces risk of users accessing a wrong app
- Reduces risks of data exposure
- Reduces testing effort (fewer apps to configure and test)
- Reduces security administration (fewer apps to authorize)
- Reduces support maintenance effort (fewer apps to manage).
And of course as it’s also your system environment – you have some related choices to make about how you want to run it. Such as:
- Whether you want to allow access from anywhere (Internet) or just within your VPN/Corporate network (Intranet)
- Whether you want to run Fiori on mobile devices or on desktops
- What’s the right level of security for different devices, different access paths, different business contexts
And that brings us to a related misconception…
2b – Activating SAP Fiori in SAP S/4HANA is only a technical task
Yes of course there is a primarily once-off technical process to activate apps en masse via tasks lists as per the SAP Best Practices guides or UI Technologies Guide and the Best Practices for Content Configuration section of the Fiori Launchpad Administration Guide. That’s just the start of your SAP Fiori for SAP S/4HANA journey.
IMPORTANT: Find out how to implement SAP Fiori for SAP S/4HANA efficiently using the latest tools SAP Fiori rapid content activation and SAP Fiori launchpad content manager
While most Fiori apps work as-is once they have been activated – e.g. most embedded analytics – a few require additional functional configuration. Plus most Fiori apps SAP delivers provide multiple extension and flexibility options that let you tailor the app to your specific needs for that same business role/task combination.
This is also why you should consider all the related apps in a delivered business catalog – not just the apps that appear as tiles on the Home Page. Fiori apps employ a very flexible and high reuse intent-based navigation approach that lets you tailor the user experience to the business role by adjusting the target of a button, hyperlink or tile. Adjusting these target mappings also adjusts your security authorizations, which are largely derived from the tiles assigned. Knowing which apps work together towards the whole user experience is critical to both the user experience and to your security design.
So the majority effort is in:
- Enabling the project team to understand the new user experience, extensibility options, and how to take advantage of common features as part of their business process design
- Assessing functional fit of Fiori apps to your to-be business processes, business roles and tasks
- Governance over user experience extension options and custom developments to fill any functional gaps
- Optimizing the user experience for your business roles across all functional silos and common features
And that means you not only need to enable your functional team, you need at least 1 dedicated resource enabling, driving, and guiding user experience efforts across all functional and technical silos of the project. You can call that person your UX Lead or UX Architect, and you can find out how they fit into the team in Essential Roles for SAP S/4HANA Fiori projects blog. You can find out more about what a UX Lead/Architect does in misconception 10.
3 – There’s a SAP Fiori app for every SAP GUI transaction
Take a hard look at the Fiori Design Principles: Role-based, Adaptive, Coherent, Simple, Delightful. You can’t deliver any of that with a simple facelift of SAP GUI!
Every Fiori app SAP delivers – and every Fiori app you might choose to build – involves going back to the drawing board. SAP calls this Design Led Development and it involves:
- Deeply understanding the business role and business context (use cases, working environment) to gain insights into how tasks can be made simpler, easier and more effective
- Ideating and prototyping with real users to design a new app that brings effective innovations or, as a minimum, meaningful improvements
- Only then can the new app be built from scratch
This means you will often find that Fiori apps:
- Decompose complex one-size-fits-all SAP GUI transactions to several Fiori apps
- Recompose specific features from several SAP GUI transactions to one Fiori app.
- Provide options that were never possible in SAP GUI
There are already over 1690 Fiori apps already for S/4HANA alone. Will every SAP GUI transaction that SAP has created over the last 40 years be converted? That’s difficult to say.
Certainly there are some good reasons for letting go of some of the past. Some SAP GUI transactions or parts of transactions are no longer be relevant or superseded by new innovations and simplifications. Some complex transactions will require more thought to simplify – particularly those that currently very sophisticated graphics. And some administrator transactions may always be back of house.
If you are coming from Business Suite or Suite on HANA you can use the Readiness Check 2.0 or the Fiori App Recommendations Report to give you a jumpstart in working out which apps you should consider first based on your current SAP GUI transaction usage. You can also run the Fiori Apps Recommendations relevance report yourself from the home page of the Fiori Apps Library by taking a snapshot of your current SAP GUI transaction usage as explained in the SAP Fiori App Recommendations instructions.
4 – Fiori Visual Theme converts classic SAP GUI transactions and Web Dynpro ABAP applications into SAP Fiori apps
What Fiori Visual Theme does well is to remove the clunk factor when navigating between the Fiori apps and classic apps. However Fiori Visual Theme is effectively a facelift for classic apps, it changes the appearance, but doesn’t make major changes to the operation or behavior of the underlying SAPGUI transaction or Web Dynpro ABAP application or CRM WebClient UI.
Even now with over 1K Fiori apps now available for SAP S/4HANA, realistically many business roles will still use at least some classic apps.
So you will need to set some expectations with your business, most importantly:
- Classic apps may not be guaranteed on mobile devices
- And there are some other behaviour implications for specific features
IMPORTANT: As of SAP S/4HANA 1909 some classic apps will work for touch-enabled and mobile devices. For more details, supported browsers/devices, and restrictions, refer to SAP Note 2700517 – Mobile device support for Unified Rendering based frameworks: Web Dynpro ABAP and SAP GUI for HTML
Why aren’t all classic apps guaranteed on all mobile devices? SAP GUI for HTML and Web Dynpro ABAP frameworks were largely written before such devices existed. Sometimes they work on device, sometimes they don’t. Often it might only be specific features that don’t work on mobile. In some cases you can circumvent these limitations by using SAP Screen Personas adaptive flavors and slipstream engine.
You should also carefully read SAP Note 314568 – SAP GUI for HTML functionality / Limitations / Sp. Behaviour which provides a summary of all the current differences to SAP GUI for Windows behaviour.
If you have business users who will still need to use SAP GUI for Windows, you should also consider SAP Business Client with connection type “Launchpad” for a best of both worlds experience from the Fiori Launchpad. SAP Business Client enables your users to access their Fiori apps and launches all SAP GUI transactions automatically in SAPGUI for Windows
5 – SAP Fiori apps should support every feature from the equivalent SAP GUI transactions
Take another look at misconception 3. Fiori design has a business role and task focus that supersedes the more one-size-fits-all design of many SAP GUI transactions. And that means not dragging the weight of every grown-over-time SAP GUI feature across to Fiori apps.
When you add the need to introduce new digital transformations as well there can be significant differences from older SAP GUI transactions. Your starting point for understanding what has changed is the Simplification Item Catalog.
And of course because Fiori apps are built from scratch using a design-led development discipline, creating all the new Fiori apps takes time. So there is a roadmap for building Fiori apps. That roadmap also includes consideration of which apps and which features will be provided when. The Fiori roadmap is updated quarterly and you can get the latest version of the Fiori roadmap by searching on keyword Fiori in the SAP Product and Solutions Roadmaps.
Plus even where transactions have been decomposed to Fiori apps, that doesn’t necessarily mean that every part of that transaction has a Fiori app equivalent yet. There are different roadmap timelines for different business processes, especially where simplifying the process needs more careful consideration. For example, apps related to Procurement of Goods have largely preceded apps relating to Procurement of Services.
6 – All you need to do is select the Apps – it’s up to the User to organize their Home Page
Not if you want high user adoption, which is usually a key driver for digital transformation.
Consider your ideal Day 1 go-live experience for your business users. On Day 1, you will want your business users to login to your new S/4HANA solution and then start work straight away.
That means even on Day 1, every business user will be able to look at their Home Page and it will make immediate sense to them. Every business user should be able to identify which tile or link they need to get their work done without any hesitation.
Remember you are still running a business, and that means you don’t have time for your business users to waste just trying to adjust their Home Page into something that works for them. Sure some will want to personalize their experience later, but on day 1 they still need to get their work done.
You can find some guidance on how to approach Home Page design in the blog Adapting the Launchpad to the Business Role and there’s also a SAP HANA Academy video version to explain this from a business stakeholder perspective.
7 – Everything will run on mobile devices without any extra thought or effort
Yes it’s true that Fiori Launchpad and Fiori apps are responsive to mobile devices, and will automatically adapt to the appropriate form factor.
However classic Uis are not guaranteed for smaller mobile devices, as mentioned in misconception 4. As of SAP S/4HANA 1909, most classic UIs are touch enabled and will support some mobile devices (think touch enabled laptop/tablet).
So you might need to consider which apps will be available for the same user on different devices. The Fiori Launchpad configuration marks which apps are relevant for which device, so that apps which are not relevant for the device are automatically hidden.
Even for Fiori apps adjusting the form factor is not the end of the mobile story. There are some strategic, functional, and technical considerations that impact how your business users will interact with mobile devices.
Strategic considerations include:
- Will you issue corporate devices or take a BYOD approach
- How many different types of devices are you prepared to manage and support
- Where will the device be stored when not in active use to minimize damage or loss
- How will you prevent device theft/misuse
- How will you respond if a device is lost/stolen
- Will the device be accessed over internet (from anywhere) or only over intranet (over VPN or in the office)
- Will you need your business users to use native device features
- Depending on which features you need, as a minimum you will need your users to use a container app, such as the provided SAP Fiori Client to access camera and barcode
- More advanced features such as calendar functions, offline usage, and machine learning typically involve additional SAP Cloud Platform services
Functional considerations include:
- If a user has multiple devices, you will need to consider which tasks will be performed on which device in which use cases
- Apps may be optimized for specific form factors
- You can find out the optimal form factors in the App’s details in the Fiori Apps Library
- E.g. If you have a multidimensional financial report with many columns and rows, that’s probably not going to give the optimal experience on a phone. The app should technically work on a phone, however it’s not going to be the best experience for that task/business role
- And there may be some safety and other regulatory concerns
- E.g. If you have maintenance workers trying to climb a ladder to work on industrial equipment, then a tablet is probably not going to fit on their tool belt, or meet compliance requirements for safe operation of ladders.
Technical considerations include:
- Mobile device management to distribute updates, and to wipe the data if the device is lost/stolen
- Internet/Intranet access routes and security layers
- Configuration and operation of container apps such as SAP Fiori Client
8 – Fiori developers from Business Suite or Suite on HANA are ready to develop on SAP S/4HANA
Maybe. But probably not.
Most developers who have previously worked on Business Suite or Suite on HANA solutions will need to make large strides to transition their understanding of concepts and their best practices:
- SAP ECC or Suite on HANA, i.e. SAP NetWeaver version 7.40 or 7.50
- Any Database or SAP HANA 1.0
- Fiori 1.0 (SAPUI5 1.38 and below)
- SAP S/4HANA 1909, i.e. ABAP Platform Version 1909 (equivalent to SAP NetWeaver 7.54)
- SAP HANA 2.0
- SAP Fiori 3 (SAPUI5 1.65 and above)
Tip: Yes that’s correct – as of SAP S/4HANA 1809, the term SAP NetWeaver was replaced by SAP ABAP Platform – find out more in What’s New in ABAP Platform.
To be effective in SAP S/4HANA your developers will need an understanding of:
- ABAP Development Tools for Eclipse
- RESTful ABAP Programming Model (and the ABAP Programming Model for SAP Fiori)
- SAP Fiori elements vs. freestyle vs. hybrid design
- Extension options for SAP S/4HANA
- Special features and common services, e.g. Default Values, Key User Extensibility, Flexibility Services, attachment services, manage workflows
There’s a lot to learn so the sooner you get your team started the better. Some of these topics can be learned and practiced even on SAP Business Suite before you transition to SAP S/4HANA. Others are enablement activities you will need in your project plan to grow your team as you transition.
You can find resources and starting points in the Deep Dive section of the SAP Fiori for SAP S/4HANA wiki
9 – HANA means never having to do Performance Tuning ever again
Regardless of the power of your backend database, when you are running over a thin client Web Browser, bandwidth and network are critical. Even more so when you are running apps over mobile devices.
If you are using container apps for mobile devices, such as SAP Fiori Client, or running apps over a VPN or Citrix connection, that can also complicate matters.
Running a Performance trace can quickly identify bottlenecks and targets for tuning.
You should especially take note of the Performance recommendations around client and server side caches in the Operations section of the Fiori Launchpad Administration Guide.
Latest Update: As of SAP S/4HANA 1809 you can also opt to run GUI transactions launched from the Fiori launchpad in Stateful Container mode. Refer to Improving Navigation Performance for SAP GUI applications
And then there are options you are strongly recommended to consider. Especially:
- Using the Content Delivery Network (CDN) for the Fiori bootstrap file that is needed by the Fiori Launchpad and every Fiori app. Note: We have customers who have measured this as a 8x factor of improvement alone in starting up Fiori apps
- Schedule the HANA View Results Cache job to pre-calculate related dynamic analytics before your users login in the morning so their Home Page starts up fast
- Avoid using Compatibility Views in your custom code extensions and custom developments, as these are a known performance drain
- Consider using SAP Business Client for desktop bound heavy users of SAPGUI transactions – this lets them use SAPGUI for Windows for GUI transactions launched from the Fiori Launchpad
Latest Update: As of SAP S/4HANA 1809 there have been some major improvements to the performance of the Fiori launchpad and the performance of SAP GUI for HTML. Refer to the What’s New in SAP Fiori Launchpad for SAP_UI 753 SP00 for more details.
Refer to the Performance and Troubleshooting section of SAP Fiori for S/4HANA wiki
10 – Assuming User Experience is a minor &/or technical part of your SAP S/4HANA project
If you have seen any presentation on SAP User Experience you will most likely have seen this diagram (people, process, technology).
This implies that the People component is now considered as equally important as Business Process functionality and Technology. And that means that in your SAP S/4HANA project plan you need to give serious consideration to how you will achieve your user experience goals. In much the same way that you currently plan for achieving your business process goals and your technology/infrastructure goals.
You will need someone to drive UX across your SAP S/4HANA Project – this is your UX Lead/Architect. This person could come from a functional or a technical background as this is largely a coordination, advocacy and governance role.
Above all your UX Lead/Architect must be people-centric, i.e. focussed on how your S/4HANA User Experience will pragmatically work for your business users in their real working environment. And they need to be great communicators as they will need to coordinate across business stakeholders, selected business users, functional silos, the technical team, and of course your organizational change management team.
You will also need to include UX related activities in your project plan. That includes:
- UX Enablement activities for the project team
- Establishing your UX strategy and governance for S/4HANA UX, which can include
- Digital transformation goals for UX
- Launchpad approach, especially if you need to integrate Cloud Solutions or 3rd party apps
- Expectations for different business roles
- Technology and infrastructure requirements
- Device and Browser requirements
- Guidance for determining functional fit
- Governance approach for how identified gaps may be met via extension options or custom apps
- Coordination activities to select Fiori apps
- Configuration activities for Fiori common features, such as Fiori Enterprise Search, the App Finder, and User Assistance help
- Technical activation of Fiori Launchpad and Fiori apps
- Functional configuration, where needed, of your selected apps
- Optimization activities, such as design and configuration of Home Pages for your business roles
- Governance activities around extension options and custom developments
You can find a summary of essential and optional UX activities across the project in the Essential Roles for SAP S/4HANA Fiori projects blog
Becoming a SAP Fiori for SAP S/4HANA guru
You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Brought to you by the S/4HANA RIG
Brilliant once again. Thanks Jocelyn!
As always this is an excellent post and I can very well co-relate my Fiori for S/4HANA implementation experience with most of the misconceptions you have mentioned. I specifically agree with the below mentioned ones as these are the ones I see are prevalent in most of the cases.
3. There’s a SAP Fiori app for every SAP GUI transaction - one of the most common myths that business users assume to be true.
4. SAP Fiori apps should support every feature from the equivalent SAP GUI transactions - again something almost all functional test users come back to the technical team after going through the standard apps at first, expecting to see everything from the corresponding backend transaction.
7. Everything will run on mobile devices without any extra thought or effort - Fiori = mobile is the assumption that almost all customers make at the beginning.
Awesome blog for a top topic!!!!
Hi Jocelyn Dart ,
Now, I will just print out this blog and share it with my managers, whenever we need to discuss on new implementation.
Please particularly raise it with your sponsors, business stakeholders, and project managers! All this stuff should be routine parts of the project - it's only when it's a surprise (usually through lack of knowledge or advocacy) that it becomes a problem.
Thanks for writing post on one more wanted topic.
. This is definitely a very good add on in my Fiori knowledge bank:)...
Extremely helpful! Thanks, Jocelyn.
Hi Jocelyn Dart,
Many thanks for sharing your knowledge and experiences. They are very helpful to understand the success key factors in a project, and addressing it in a good way 🙂
Thank you, thank you, thank you, this is one of the most valuable blogs i've come across on the FIORI topic....i've argued so many times about all the points you mention here is not eve funny anymore.
Thanks for sharing a very helpful blog. This will surely remove lot of misconceptions
great to see that this is the direction. Now all we need to convert your blog to all the presale and sales-people out there in an official document.
Important is the first point. S/4 is not complete without Fiori and that message should be a must.
Couldn’t agree more... and anything you can do to get it in front of these teams is appreciated.
Perhaps even more important is to get it in front of our Partner’s project managers. With so many S/4HANA projects implemented by partners its critical to educate the project mgrs as much as the consultants.
We have been telling people for a long time now ... S/4HANA is not an upgrade from ERP. There are new considerations at all levels including project mgt.
Excellent Article!! Thank you Jocelyn.
Great post Jocelyn Dart - perfectly summarising the general sentiment in the marketplace. There is no excuse now for partners and customers alike to be successful in implementing S/4HANA systems. 10 massive myths/misconceptions laid out brilliantly. Thanks and well done!
Are we going to see a day when this application replaces traditional SAP GUI, completely ?
ie Users no longer use classical transactions like VA01/VF01 etc....but gets the job done only through Fiori Apps ?
I still feel the traditional way of Custom developments/Enhancements in SAP are going to stay.
Hey I answered that one already in misconception 3... part of the considerations here is the race between re-designing Graphical User Interfaces and the climb of new UI options such as Voice User Interaction.
Certainly for now we are scaling fast and there are some roles that already have a large number of Fiori apps available. Such as Accounts Payable Manager, Purchaser, Sales Manager, Warehouse clerk. https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/filters/RoleNames
We are also encouraging customers to move to the ABAP Programming Model for Fiori even for custom developments - as that is a) easier than the old ways - once you learn it b) gives you the power of HANA and Fiori to the same degree as delivered SAP Fiori apps
I like the one about no performance with HANA. I never believed that one. How about the one where Fiori is always fast? It really isn't. There are a lot of blogs, articles, SAP Support notes.... Oh boy it makes my head spin. I'm sure it will be eventually. But just try it when you have a lot of authorization. And then go on the hunt for performance guides.
Re Fiori is always fast... well it should be and it can be... as per Fiori Qualities . Like all code it depends on a number of factors including but not limited to...
And sometimes too much authorization is part of the problem... aka Launchpads with unrealistically large numbers (I have seen 100s!) of tiles.
Plus the confusion with Fiori Visual Theme.. sigh
As always insist on evidence and measurement via performance traces - otherwise you can waste a lot of time adjusting things that will make no discernible difference in your particular environment.
It's just going to be a real challenge to set up correctly. I assume when it is set up it will work great. 🙂 The programs - right now - are pure out of the box Fiori.
Just a quick reminder that even out of the box apps could cause issues. Fiori seems to be a big one as I read and re-read and check again.
Yes performance traces should be a real help.
Hi Michelle, Most apps are fine. Of course you want to check your Fiori Launchpad is optimized as that's central to everything. One of the interesting results is that Chrome/Firefox are known to run significantly faster than IE11 with the same apps... so your tech team should always have more than one browser for testing.
There was a hit list of apps with issues as at 1709 FPS00 at https://launchpad.support.sap.com/#/notes/2519264 - most have been remediated by now. We have also seen occasional problems with very large datasets (millions of datapoints) with some of the analytical apps - sometimes the issue is in the CDS View, sometimes in the rendering - so definitely performance tracing is needed there to resolve it.
As a rule check for any Important Notes listed for your apps in the Fiori Apps Library for the latest related to a specific app.
Yes - I didn't set up the Fiori box. But I know they have been looking at notes, limiting our roles, adding profiles... And much, much more.
I guess my point is unlike SAP GUI it will take some time to get it right. And if you get it right the first time, I am impressed. Remember this is SAP tiles and not custom ones.
There really isn't a real reason that our Fiori should run slow. We are a small company. Our material master is around 4000 records.
Thanks for the pointer. I will check out that note. By the way - great blog.
Ok Michelle - definitely 4K records should not be any issue for HANA !
Please get your team to do a performance analysis on the backend and from the frontend. If it's slow on the backend it could be someone has extended the OData Service using a compatibility view (an old DDIC view that overlays the simplified table).
Compatibility views are an intermediate solution so that when you first move to S/4HANA custom apps and custom code exits keep working .. but they have known performance problems and you should ideally be rewriting any code to avoid using them as part of your implementation project.
If the problem is in the frontend it's more likely to be web browser network/bandwidth/proxy issues or bootstrap loading. Those are all solvable -e.g. Akamai CDN for faster loading of the bootstrap.
Please make sure your team are aware we have a whole section on Performance and Troubleshooting in our wiki the https://wiki.scn.sap.com/wiki/display/Fiori/SAP+Fiori+for+S4HANA
Definitely keep at your team to get this solved... remember they are building their skills with Fiori just like you are 🙂
And thanks for the encouragement!
How About SAP Screen Personas fitment with Fiori @ S/4 HANA....
HI Oza, SAP Screen Personas has been a good fit with SAP S/4HANA since the early days. Follow Peter Spielvogel for the best blogs such as this one
More blogs like this please! Congrats. FM
VERY good! Number 4 and 10 especially! Thanks for blogging this!
Nice article, also it is good to know that most customers issues is the SAP functional configuration steps for the SAP Fiori apps is not at all same as customers configurations because each customer will have their own Z* Y* configurations that will not work for the SAP Fiori apps configuration steps.
(SAP way for configuration is not like other customer way of configuration) so developing custom app is easier and more efficient than modifying (not extending extinction will make you get more issues ) the SAP Fiori app source code / odata service classes etc..
Also you will find comments and bugs throughout the source files of SAP Fiori apps since the app is developed by many SAP developers with outdated UI5 version API methods (way older than S4hana UI5 version) 🙂 and without following their own developer guidelines.
It's true that where Fiori apps provide additional configuration, typically the Fiori app configuration is different to the configuration for the SAP GUI for HTML.
However that's not a hard and fast rule. One of the major benefits of using the Key User Extension options and Fiori apps such as "Custom Fields and Logic", "KPI Workspace", "Custom Analytical Queries" is that they enable you to extend existing SAP Fiori apps safely and according to SAP S/4HANA best practice. Some of these apps - especially Custom Fields and Logic - even ensure that equivalent changes apply in both Fiori and SAP GUI.
Also feel free to provide SAP Incident feedback on any app where you find outdated UI5 version methods that are having a negative impact on app behaviour or performance. We have fairly strict governance procedures in place across all of SAP Development, but of course:
The SPRO config steps for the SAP standard Fiori apps will not work for customers because each customer has their own way of config than the way SAP assume.
I've shared via Linked-In. Big Thank you!
Thanks for sharing!
Excellent consolidation of critical myths around SAP Fiori for S/4HANA. Thanks for putting this together.
Excellent summary that can come only from great insight and thorough experience. Thanks Jocelyn.
Thanks Jocelyn for the wonderful summary.
Thank you Jocelyn, I found it very useful!
I am looking for activation step by step guide for fact sheet standard fiori app. Can you please guide me regarding this.
Please follow the Best Practice Guides for deploying all apps.
Also you may find the videos in our UX Virtual Bootcamp helpful
I like your blogs and this blog is very useful on setting the expectations on Fiori.
I have couple of queries . We intend to use Fiori Apps for scanning.
Thanks in advance.
It's very difficult for us to answer specific questions in blog comments. Please post them as *separate* questions in https://answers.sap.com with tag Fiori.
Scanning is a very specific topic and that's an older technique that I can't help you with.
However there are others in the community with some experience in this and related techniques such as the following blog... so please ask your question in answers.sap.com