Yes, you can customize a Fiori application, and SAP provides multiple avenues for doing so, ranging from simple personalization options for end-users to in-depth, code-level extensions for developers.
The approach you choose depends on the complexity of the changes required, your technical skills, and whether you are extending a standard SAP app or building a new custom one. For the most robust, upgrade-safe customizations, SAP's strategic approach is to use the SAP Business Technology Platform (BTP) for "side-by-side" extensions.
Levels of Fiori customization
1. End-user personalization (no-code)
The simplest level of customization is for individual end-users who want to adjust their personal Fiori Launchpad experience.
- Launchpad content: Users can create custom "My Home" pages, add or remove app tiles, and organize them into groups or rearrange sections to improve navigation.
- Settings and appearance: Through the "Settings" menu in the user actions menu, users can change the overall color theme, language, and default values for their profile.
- App variants: An end-user can also save multiple "views" of a single app, which are essentially pre-configured filters or settings for a specific task.
2. Key-user extensibility (low-code)
Key users, typically business experts or process owners, can make modifications to Fiori apps for a group of users, or even the entire company, without writing code. This is often done using SAP Fiori tools within the Fiori Launchpad itself.
- Adapt UI: With the "Adapt UI" feature, key users can add, remove, or rearrange fields, rename labels, and hide UI elements by simply using a drag-and-drop interface. These changes are saved at runtime and are considered modification-free, meaning they are not impacted by future SAP upgrades.
- Custom fields and logic: For more advanced changes, key users can use the "Custom Fields and Logic" apps in S/4HANA Cloud. This allows them to add new custom fields to business contexts and create simple business logic, such as field validations or derivations.
- App variants for all users: Key users can save and publish UI adaptations as a new app variant. This variant, with its modified layout and behavior, can then be assigned to specific business roles, making the changes available to all relevant users.
3. Developer extensibility (pro-code)
This is the most powerful method of customization, allowing for deep, code-based modifications and the creation of entirely new applications.
- In-app extensions (on-stack):
- Developer Extensibility with RAP: For customers on a private cloud or on-premise, developers can use the ABAP Development Tools (ADT) within Eclipse to write ABAP code for custom logic. SAP's modern ABAP RESTful Application Programming Model (RAP) ensures these in-app extensions are upgrade-safe by only using released SAP objects.
- Side-by-side extensions (on BTP):
- Adaptation projects: Using SAP Business Application Studio (BAS), developers can create "adaptation projects" that non-invasively extend standard Fiori apps. These projects sit separately from the original application, meaning core code is never touched. Adaptation projects can be used to extend controllers, replace views, or modify app descriptors.
- Freestyle development: Developers can use templates in SAP BAS to create brand-new, standalone Fiori applications from scratch. These applications are built using the SAPUI5 framework and connect to backend SAP data via OData services.
- Custom OData services and CDS views: Developers can create custom OData services and extend existing Core Data Services (CDS) views to expose additional data from the SAP backend. This allows custom fields and data sources to be used in both standard and custom Fiori apps.
4. Low-code/no-code platforms
For organizations seeking to accelerate Fiori development, third-party platforms offer specialized tools.
- Neptune Software: The Neptune DXP (Digital Experience Platform) is a popular, SAP-certified, low-code/no-code platform for building Fiori apps. It features a drag-and-drop builder and reusable application building blocks, which can significantly speed up development.
- SAP AppGyver (now included in SAP Build Apps): This no-code platform on SAP BTP allows business users to create sophisticated applications using a visual interface, which can be integrated into the Fiori Launchpad.
Customization strategy: A tiered approach
A successful Fiori customization strategy often involves a tiered approach, starting with the least invasive methods and escalating only when necessary:
- Start with personalization: Empower end-users to make simple personal adjustments to their Launchpad layout and app settings. This covers the majority of user requests without requiring IT intervention.
- Use key-user extensibility for UI changes: For changes that need to be standardized for a business role, use the Adapt UI feature. This is an excellent way to streamline an interface for a team and is completely upgrade-safe.
- Use side-by-side extensions for complex logic: When new functionality is required, or a standard app needs significant enhancements, use adaptation projects or build new apps on SAP BTP. This keeps the core SAP system clean while providing maximum flexibility.
- Adopt low-code tools for accelerated development: For projects requiring rapid development and deployment, especially with a backlog of business requests, consider low-code platforms to increase agility and reduce reliance on highly specialized developers.
- Use on-stack development for deep, tightly coupled extensions (cautiously): This is the final and most invasive option. For core business process extensions that are tightly coupled to the underlying SAP system, use RAP-based development within the S/4HANA system itself. While upgrade-safe, it should be reserved for scenarios where a BTP-based extension isn't suitable.