SAP Fiori 2.0 end of maintenance 2027 despite S4/HANA
Reading time: 4 min
Suddenly, no one in the company can record working times any more – a horror scenario that could soon come true. The trigger? The imminent end of maintenance for the HCM Fiori 2.0 add-on on 31.12.2027. What initially seems like a technical detail turns out to be a strategic tipping point on closer inspection. This is because many companies currently assume that their investments in S/4HANA will automatically secure the future viability of their HR front-end landscape. This assumption is dangerous and often wrong. Fiori 2.0 will no longer be included in regular maintenance under S4/HANA from December 31, 2027.
What is the SAP HCM Fiori 2.0 AddOn?
In simple terms, the SAP Fiori 2.0 for SAP ERP HCM add-on is the modern Fiori interface for the classic SAP HCM system.
It provides the front-end components such as user interfaces, Launchpad content and apps. This allows HR processes to be used in the browser instead of in classic SAP GUIs. Employee Self-Services (ESS) and Manager Self-Services (MSS) are at the heart of this add-on. Employees can use them to independently view their remuneration statements, submit vacation requests or record their working hours, while managers can issue approvals, view evaluations or the team calendar via a clear launchpad.
The underestimated blind spot in the SAP roadmap
Most transformation programs are currently dominated by one topic: the switch to S/4HANA. The focus is on finance, logistics and data models, while HR front-end technologies are often seen as downstream. HCM Fiori 2.0 is running stably in many places, is established and therefore does not appear to be an acute need for action.
But this stability is deceptive. Maintenance ends are nothing unusual in the SAP environment, but this one is different. It doesn’t affect just any backend component, but the central user interface for HR processes – precisely the area that employees and managers use on a daily basis.
When support ends, it means more than just the absence of new features. It’s about security updates, legal adjustments and the long-term stability of the applications. Especially in the HR context, where sensitive data is processed, this is a risk that should not be underestimated.
Recommendations for action: Start now
On paper, one year in advance may sound sufficient. In reality, however, this time window shrinks dramatically. New functionalities are rarely used productively immediately, but are first subjected to internal tests, coordination with specialist departments and technical adjustments. Moreover, support packages are often only installed months after release, when a certain degree of stability is guaranteed. So how do you prepare for the end of maintenance?
Create awareness and get started & overcome the basic hurdle
The central question at the beginning is: Is your system already running on S/4HANA Release 2025? If not, this is your starting point. This upgrade is not an optional measure, but the mandatory basis for all further steps towards Fiori HCM migration.
At the same time, you should not view the topic in isolation. Anchor the migration of your Fiori HCM landscape in your IT strategy at an early stage and in a binding manner. How? With clear prioritization, the planning of necessary resources and a realistic and resilient roadmap. If you start too late, you risk unnecessary time pressure in later project phases.
Modular approach
Get a complete overview of the Fiori HCM apps currently in use. Only on this basis can you make informed decisions and prioritize sensibly.
Ask yourself the question: Which of these apps can already be migrated today? This is exactly where your quickest leverage lies. Take advantage of this potential and start with the first conversions at an early stage.
Make a conscious decision to use a step-by-step, modular approach. Each successfully migrated app reduces complexity as you progress and brings you closer to your goal. At the same time, you avoid ending up with a big bang that is difficult to control.
For apps that cannot yet be migrated, plan for this now. Define early on when and how the changeover should take place as soon as the corresponding solutions are available. According to SAP’s current statement, all new apps should be made available by December 31, 2026 at the latest. The key advantage of this approach? You streamline the overall project. Effort, costs and resources are spread over a longer period of time. This gives you more control and planning security, while at the same time enabling you to manage your financial expenditure much better.
Conclusion: Don’t forget the SAP Fiori HCM apps
Between finance, logistics and data model migrations, HR front ends such as SAP Fiori are often forgotten in H4S4 projects. Yet these are precisely the applications that are in direct contact with employees and managers. What happens if they suddenly stop working? Employees can no longer record their times? Unimaginable. That’s why you should start the migration of your SAP Fiori HCM apps early. Our recommendation: take a modular approach to avoid running into time constraints. You should also define the migration date and possible solution for apps for which there are no successor applications yet. At best, the migration should be completed by 31.12.2027 at the latest.
