Introduction
Your Fiori launchpad holds more than 500 apps, yet nobody can tell you which ones employees actually open. Business users report slow tiles, and the IT team learns about the problem only after a ticket arrives. This situation is common in SAP S/4HANA landscapes where the Fiori rollout moved faster than the monitoring setup. Teams usually track apps in spreadsheets, which stop working as soon as roles, catalogs and releases change. SAP Fiori Solution Manager, meaning the combination of SAP Fiori and SAP Solution Manager 7.2, closes this gap. This article explains seven features that help you manage, monitor, test and improve Fiori apps, and it shows when each one fits.
Centralized Management of SAP Fiori Apps
Benefits of using SAP Fiori Solution Manager:
Managing hundreds of Fiori apps manually becomes unrealistic once several business units, languages and regions share one landscape. In SAP S/4HANA, the Fiori launchpad organizes apps through catalogs, groups and spaces, and administrators assign them to users through PFCG roles. SAP Solution Manager 7.2 adds a monitoring layer on top, because it collects usage and performance data from the connected systems and presents it in one place. As a result, administrators can see which apps are assigned, which ones are used and which roles carry unused content.
Usage data also supports adoption work. When an app is assigned to 2,000 users but opened by fewer than 100, the team can review the role design or plan targeted training before it removes the app. For example, a manufacturing group with more than 500 Fiori apps across several regions can use this view to remove unused tiles and reduce the effort of role maintenance.
Integration with SAP S/4HANA
CSAP Solution Manager 7.2 connects to S/4HANA systems through the managed system setup, and the Diagnostics Agent then collects technical data from the backend and the Fiori front-end server. An embedded deployment runs the front-end server inside the S/4HANA system, whereas a hub deployment keeps it separate, so you must register both components when your landscape uses a hub. After the connection is active, Technical Monitoring evaluates metrics such as dialog response time, OData service errors and gateway failures. The alerting framework then notifies the responsible team by e-mail or through the alert inbox.
Rollouts benefit from this setup as well. Before a new finance app goes live, a team can run its test cases under the target user role and compare the results with the previous release. Consequently, problems such as missing authorizations or inactive OData services appear in the test system instead of production.
Analytics and End-to-End Monitoring
Technical Monitoring and End-User Experience Monitoring answer different questions. Technical Monitoring shows how the systems behave, for example through workload statistics and OData request times, while End-User Experience Monitoring runs scripted robots that open Fiori launchpad tiles and measure the response time a user actually experiences. Together they reveal whether a delay originates in the network, the front-end server or the backend.
Consider a Leave Request app that HR describes as slow. The IT team first compares the robot measurements with the backend response times. If the backend responds quickly but the robot still records long loading times, the team inspects front-end factors such as cache settings and UI5 resource size. If the backend time is high instead, it traces the approval workflow and the underlying OData calls. Because this analysis starts from measured data, the team can correct the cause before complaints increase.
Configuration and Personalization of Fiori Apps
Solution Manager does not provide drag-and-drop field editing, so this feature depends on where the change happens. Administrators build catalogs, groups, spaces and pages in the Fiori launchpad, and key users adjust screens with the Adapt UI function and add fields through the Custom Fields and Logic app in S/4HANA. Solution Manager enters the process afterwards, because Change Request Management documents the change, controls the approval and moves the transport through the landscape.
A sales organization that needs a Discount Approval field in its sales app illustrates the process. A key user creates the field in the development system, a change request records the business reason, and the transport reaches production only after testing and approval. Furthermore, role-based access limits who sees the field, which keeps the change consistent with the authorization concept. This approach separates the quick work of the key user from the audit trail that IT requires.
Automated Testing and Quality Assurance
The Test Suite in SAP Solution Manager 7.2 organizes test plans, test packages, and test cases. It supports the complete release cycle. Automated execution is possible through integrated tools, such as Component-Based Test Automation and certified partner solutions. Teams can therefore reuse scripts for each Fiori release.
Moreover, defects recorded during a test run can link to the related change request. This allows developers and testers to work on the same item.
Payroll apps show why this approach matters. A regression test can recalculate sample payroll results after each update. It can also verify the required approval steps. This helps catch faulty calculations before they affect employee payments.
Fiori front-end components receive frequent updates. Therefore, teams should schedule regression runs after each support package. Regular testing helps keep the risk of production incidents low.
Project and Change Management
SAP Solution Manager supports delivery through Change Request Management and, in newer implementations, the Focused Build solution. Teams capture requirements, assign them to work packages and follow them through development, testing and deployment, so every Fiori app has a traceable path to production. This also gives project members a shared view of milestones, approvals and open defects.
A procurement app rollout shows the benefit. Developers deliver the app, architects review the transport, and business owners approve the result at defined gates in one tool. As a result, handovers no longer depend on e-mail, which shortens delays and reduces escalations. Versions of the app stay documented as well, and this helps auditors who need to know who released which change.
Business Process Monitoring
Business Process Monitoring, which belongs to Business Process Operations in SAP Solution Manager 7.2, measures whether key processes finish on time. Teams define monitoring objects such as open invoices, failed IDocs or blocked orders, assign thresholds and connect them to the Fiori apps that users employ for these tasks. Process owners then see both the KPI and the app behind it.
In accounts payable, the team can monitor the number of invoices waiting for approval and the average approval time. When the figure exceeds the threshold, an alert reaches the responsible team, which then checks the approval app, the workflow or the user assignment. In this way, process data supports optimization decisions, and department-level reports show where regional bottlenecks occur.
Which Component Supports Which Task
The table below maps each Fiori management task to the Solution Manager 7.2 component that covers it.
| Task | Solution Manager 7.2 component | Typical output |
|---|---|---|
| App usage and adoption | Usage data with Technical Monitoring | Assigned vs. active users |
| Performance of Fiori tiles | End-User Experience Monitoring | Response time per tile and location |
| System and OData errors | Technical Monitoring and alerting | Alerts to the responsible team |
| Release testing | Test Suite | Test results linked to defects |
| Change and transport control | Change Request Management, Focused Build | Audit trail per change |
| Process KPIs | Business Process Monitoring | Threshold alerts per process |
Conclusion
SAP Fiori Solution Manager is best understood as an operating model, not a single product. In this model, Fiori provides the user interface, while SAP Solution Manager 7.2 supports monitoring, testing, change control, and process visibility around it. Together, these components connect the user experience with the governance and operational processes required to manage SAP environments.
Organizations that combine both can gain reliable usage data and earlier detection of performance problems. They can also maintain a documented path from requirement to production for each Fiori app.
Planning should also consider the product roadmap. SAP has announced that mainstream maintenance for Solution Manager 7.2 ends in 2027. SAP positions SAP Cloud ALM for cloud-oriented landscapes.
Teams should therefore decide which scenarios will remain in Solution Manager. They should also identify which scenarios will move to Cloud ALM. This decision should align with the organization’s S/4HANA transformation progress.
FAQs
What is SAP Fiori Solution Manager?
SAP Fiori Solution Manager is not a single SAP product. It describes the use of SAP Solution Manager 7.2 to monitor, test and govern SAP Fiori apps running on S/4HANA or ECC. Solution Manager supplies monitoring, testing and change tools, while the Fiori launchpad provides the user interface and app assignment.
Does SAP Fiori Solution Manager work with S/4HANA?
Yes. You connect S/4HANA systems to SAP Solution Manager 7.2 through the managed system configuration, after which Technical Monitoring and Business Process Monitoring collect data from the Fiori front-end server and the backend. Check the compatibility information for your S/4HANA release, because supported agent versions differ..
Can you personalize Fiori apps in Solution Manager?
Personalization does not happen in Solution Manager itself. Administrators adapt apps through Fiori launchpad tools, key user extensibility and the Adapt UI function, while Change Request Management tracks and transports these changes, so SAP Fiori Solution Manager governance stays consistent across systems.
Can Solution Manager test Fiori apps?
Yes. The Test Suite in SAP Solution Manager 7.2 organizes test plans, test cases and results for Fiori apps. It runs automated tests through integrated automation tools and links defects to change requests, which helps teams verify each release before go-live.
What does End-User Experience Monitoring measure?
End-User Experience Monitoring runs scripted robots that simulate user actions, such as opening a Fiori launchpad tile, and records response times from defined locations. IT teams use these measurements in SAP Fiori Solution Manager scenarios to detect slow apps before real users report problems.
Who is responsible for Fiori monitoring and governance?
Responsibility is shared. Basis administrators configure Solution Manager and monitoring, Fiori administrators manage catalogs, spaces and roles, developers handle extensions, and process owners define KPIs. A clear responsibility model prevents gaps between these groups, and most projects assign one central ALM lead who coordinates all four.
Is SAP Solution Manager still supported?
SAP Solution Manager 7.2 remains supported, but SAP has communicated an end date for mainstream maintenance in 2027 and positions SAP Cloud ALM as the strategic successor. Confirm the current dates on the SAP Support Portal before you plan a new SAP Fiori Solution Manager investment.
How do you track Fiori app usage?
Usage data comes from Fiori launchpad usage reporting, and Solution Manager can combine it with workload and performance metrics. Comparing assigned users with active users shows which apps need training or removal from roles, which keeps SAP Fiori app management based on facts instead of assumptions.
Resources
https://help.sap.com
https://fioriappslibrary.hana.ondemand.com
https://community.sap.com
https://support.sap.com
