#S4HANA 1610 use case series: 5b SAP Fiori 2.0 (tech view)
Welcome back to the technical view of SAP Fiori 2.0 in this series of use cases for the SAP S/4HANA 1610 release. In the last blog we learned more about the innovations that are part of SAP Fiori 2.0, today we will take a look at more aspects and tools relevant with SAP Fiori.
SAP Fiori is the overall user experience in SAP S/4HANA 1610. All applications – SAP Fiori apps and classic applications run in the SAP Fiori 2.0 visual theme ‘Belize’. Classic applications refer to SAP GUI for HTML and Web Dynpro for ABAP applications.
Customers create SAP Fiori launchpad content tailored to their needs. In this context they also want to
- include their homegrown customer applications
- apply the SAP Fiori visual theme to these applications
1) How to get customer applications into the SAP Fiori launchpad?
With SAP S/4HANA 1610, SAP delivers SAP Fiori launchpad content for more than 100 business roles.
Business roles consist of business catalogs. A single business catalog covers a set of business tasks.
The business catalog content refers to content in technical catalogs such as SAP Fiori apps, classic applications.
Furthermore, there is a repository of several thousands of app descriptors that can be enabled by administrators to extend the SAP Fiori launchpad content. The application descriptors are technical entities allowing users to call applications.
Consuming standard content
Besides SAP Fiori apps, a large number of Web Dynpro ABAP applications and SAP GUI transactions is available as standard content in predefined technical catalogs in SAP S/4 HANA. This content can be consumed in the SAP Fiori launchpad by adding the applications to business catalogs and customers can adapt it to their needs.
With the Mass Maintenance Tool, it is easy to create application descriptors for all the Web Dynpro ABAP applications and SAP GUI transactions to be integated in the SAP Fiori launchpad. The tool allows customers to create application descriptors for all applications efficiently and in one place.
In both cases, it is necessary to replicate the technical catalogs from the backend to the frontend server using an extraction report. After the replication, it is possible to create business catalogs based on the technical catalog content.
2) How to adapt customer-specific applications to the SAP Fiori visual theme
In SAP S/4HANA all applications are displayed by default with the SAP Fiori 2.0 visual theme Belize. Still, SAP recommends customers to review their customer specific applications to verify that they are properly displayed.
The new theme Belize offers design enhancements that go beyond simply changing colors. Some of these enhancements are:
- Change of header and footer display
- Application functions displayed in new header / footer bar close to SAP Fiori apps
- Use of icons instead of text
- Selected actions moved to the footer
- Right alignment of labels
- Radio buttons, check boxes may need to be newly arranged
- Enlargement of screen elements
If you need more details on the design-related innovations, have a look at this blog.
Taking into account the enhancements mentioned above, customers need to review their applications and do the corresponding adaptations.
This can be done via the classic development tool, the ABAP Workbench that has been enhanced with new functions to support the adaptation of the design. For example, you can select if a function button should appear in the header or the footer.
Stay tuned as we will take a holiday break with this series and will be back in 2017 with the next use case, Integrated Quality Management.
Discover the full scope and benefits of SAP S/4HANA 1610
- SAP S/4HANA 1610 Release Highlights Brochure
- SAP S/4HANA 1610 Release Information
- Discover SAP S/4HANA
And follow me via @SDenecken to stay on top of the latest…
Here the link to Part 5a:
Link to the series: