Today almost every software and websites has a mobile compatible version and everyone can check anything on his mobile or tablet. This wasn’t the case 7-8 years ago. For SAP, Graphical User Interface as known as GUI was very powerful at the time when SAP launched its ERP software. With time, many other software exists with the fleet of HTML5 based powerful and more appealing modern UI-technology.
For this, the old GUI was not able to stand with it. As everyone knows, today are smartphones and tablets more powerful than pc’s. So, it was very important for SAP to find a solution and its was SAP Fiori – “One UX for all SAP Products”. Fiori is based on a framework known as SAPUI5 which is built on top of HTML5 and is compatible with any device and any screen size. The first announcement from SAP about Fiori was in May 2013 with the first release of 25 transactional Fiori apps for the most common business functions, such as self-services tasks which known as ESS/MSS.
Today, there are more than 1140 true Fiori apps available in Fiori library. The number of apps can partially supplement the previous GUI transactions. SAP offers three types of Fiori apps with different database requirements. A distinction is made between Transactional apps, Analytical apps and factsheets. Only Transactional apps can run on any database that supports SAP ERP. The other 2 types require SAP HANA as database. Since 2013, Fiori has made great progress and will continue in the coming years.
Table of Contents
1 Introduction
1.1 Problem Statement
1.2 Goal
1.3. Structure of seminar thesis
2 Fundamentals and basic Terms
2.1 SAP GUI
2.2 SAP Fiori
2.3 SAPUI5
2.4 Open UI5
2.5 Web Dynpro ABAP
3 Methodology for the literature work
3.1 Literature references
3.2 Filters
3.3 Search terms
3.4 Result for the literature search
4 Results
4.1 Fiori apps in the present and in the future
4.2 SAP Fiori UX Design Principles
4.3 SAP Fiori App Types
4.3.1 Transactional apps
4.3.2 Analytical apps
4.3.3 Fact sheets
4.4 Difference between SAPUI5 and Web-Dynpro ABAP
4.5 Fiori compared to WebDynpro Application
5 Conclusion
6 Future prospect
Objectives and Topics
The main objective of this study is to examine the evolution and future trajectory of SAP's user interface technology, specifically transitioning from the traditional SAP GUI to the modern SAP Fiori and SAPUI5 framework, while evaluating the functional differences and adoption benefits.
- Evolution of SAP user interfaces from GUI to web-based modern technologies.
- Core design principles of SAP Fiori including responsive and role-based UX.
- Comparison of functional capabilities between traditional Web Dynpro and modern Fiori apps.
- Analysis of app architectures including transactional, analytical, and fact-sheet types.
- Strategic shift towards mobile compatibility and consumer-grade user experience in enterprise systems.
Excerpt from the Book
4.2 SAP Fiori UX Design Principles
With the use of SAP Fiori UX Design Principles is meant, that employees can expect a consumer-grade user experience [11]. “Enterprise apps now demand to be more intuitive, personalized, and thoroughly designed in the way they are utilized” [11]. SAP now offers these requirements with Fiori Apps.
Improve productivity by ensuring simplicity and automated task completion [11].
Easy development of Fiori applications using SAP development tools and technology [11]
Cost reduction for training and support by simple, roll-screened screens [11]
Enhances user adoption through UX design [11]
Enhances data quality and compliance guaranteeing ease in system record entry [11]
Summary of Chapters
1 Introduction: Provides an overview of the thesis scope, defines SAP, and outlines the problem statement regarding the shift from legacy GUI to modern interfaces.
2 Fundamentals and basic Terms: Explains the technical background of SAP GUI, the framework of SAP Fiori, SAPUI5, OpenUI5, and the legacy Web Dynpro ABAP technology.
3 Methodology for the literature work: Details the research process, including utilized databases, filter criteria, and the search terms used to identify relevant literature.
4 Results: Presents an analysis of current and future Fiori app trends, UX principles, architectural types of apps, and a direct comparison between Web Dynpro and Fiori.
5 Conclusion: Summarizes the strategic importance of the transition to Fiori and the long-term impact on enterprise productivity and development practices.
6 Future prospect: Offers insights for potential future research regarding database dependencies and the complex mapping between legacy GUI transactions and new Fiori apps.
Keywords
SAP, Fiori, SAPUI5, GUI, Web Dynpro ABAP, User Experience, UX Design, Responsive Design, Transactional Apps, Analytical Apps, Fact Sheets, HTML5, HANA, Enterprise Software, Mobile Compatibility
Frequently Asked Questions
What is the central focus of this thesis?
The thesis explores the status and future development of SAP Fiori and SAPUI5 as replacements for the traditional SAP Graphical User Interface (GUI).
What are the key thematic areas covered?
The work covers SAP's UI evolution, the technical frameworks behind Fiori, architectural differences in app types, and a comparative analysis against Web Dynpro.
What is the primary research goal?
The goal is to analyze existing literature to understand the current state and future perspective of SAP's modern UI technologies.
Which scientific methodology is applied?
The author conducted a structured literature review using databases like Google Scholar, SAP Press, and ScienceDirect, applying specific search terms related to SAP UI technologies.
What topics are discussed in the main body?
The main body treats the history of SAP GUIs, the design principles of Fiori, the architectural differences between transactional, analytical, and fact-sheet apps, and a comparison of performance and usability.
Which keywords characterize this work?
Primary keywords include SAP Fiori, SAPUI5, User Experience (UX), Web Dynpro, and Mobile Compatibility.
How does Fiori improve upon the traditional SAP GUI?
Fiori provides a role-based, responsive design that works on mobile devices and browsers, offering a more intuitive and consumer-grade user experience compared to the older desktop-bound GUI.
What distinguishes the three types of Fiori apps mentioned?
Transactional apps handle user tasks, Analytical apps offer real-time business data processing, and Fact Sheets provide contextual information on central business objects, with varying database requirements such as HANA.
Why is the transition from Web Dynpro to SAPUI5 considered a "big step"?
It represents a shift toward modern web standards (HTML5, CSS, JavaScript) that enable platform independence and mobile access, moving away from server-side, browser-restricted applications.
What does the author conclude regarding the relationship between GUI and Fiori?
The relationship is not one-to-one; one complex legacy GUI transaction may be split into multiple Fiori apps, or conversely, multiple legacy tasks may be consolidated into a single, more efficient Fiori application.
- Citar trabajo
- Rohan Ahmed (Autor), 2017, SAPUI5 and Fiori. Status and Future Perspective, Múnich, GRIN Verlag, https://www.grin.com/document/426830
