What does it mean to develop Fiori apps on the BTP?
When you develop Fiori apps on SAP BTP, you’re making a very specific architectural decision:
You build and run the application’s UI layer entirely within the SAP Business Technology Platform—regardless of the backend system (e.g., S/4HANA).
In doing so, you should pay particular attention to the following architectural aspects:
Cloud-native Development
The app is developed in the BTP, typically using:
- SAPUI5/OpenUI5
- SAP Fiori Elements
- CAP (Cloud Application Programming Model) or RAP (ABAP RESTful Application Programming Model)
- Node.js or Java Services
Decoupling from the backend
The app no longer runs on the Embedded Fiori Frontend Server of an S/4 system, but instead:
- UI is running in the BTP
- Backend data is retrieved, for example, via OData services from S/4HANA
- Connection via SAP Cloud Connector or direct cloud APIs
Clean Core
A key reason why companies develop Fiori on the BTP:
- No modifications in S/4HANA
- Custom code has been moved to a side-by-side extension
- Upgrading S/4 is easier
Extensibility via BTP Services
Fiori apps can directly use BTP services:
- SAP Build Process Automation (former Workflow Management)
- Event Mesh
- Document Management
- Identity Services
- Integration Suite
Multi-Backend-Ability
A BTP app can combine data from various systems:
- S/4HANA
- SuccessFactors
- Ariba
- Non-SAP-Systems
Centralized deployment via the Launchpad Service
Instead of the Fiori Launchpad in the ERP system, you use:
- SAP Build Work Zone / Launchpad Service
- Roles, catalogs, and tiles are maintained in the BTP
Conclusion
Fiori on the BTP platform enables modern, cloud-native, and decoupled UI development. This approach supports clean-core strategies and allows applications to run independently of the S/4 system.
Do you have any questions?
Get in touch with us.