6 November 2026 · Christian Buck
When Fiori Elements is enough and when freestyle SAPUI5 is needed
For almost every new user interface on SAP BTP or S/4HANA, the same question comes up early: Fiori Elements or a freestyle SAPUI5 application? Often the team's habits decide. Yet the choice affects effort, maintenance and upgrades for years.
How Fiori Elements works
Fiori Elements provides ready-made page templates, the floorplans: List Report, Object Page, Worklist, Analytical List Page and Overview Page. Annotations on the OData service define which fields, filters and sections appear. UI.LineItem determines the table columns, UI.SelectionFields the filter bar, UI.HeaderInfo and UI.Facets the structure of the Object Page.
In CAP, these annotations live in CDS files, for example annotate CatalogService.Books with @UI.LineItem: [ ... ];. In the ABAP RESTful Application Programming Model, metadata extensions take on this role. The user interface thus becomes part of the data model and can be versioned together with the service.
The benefit shows mainly in maintenance. The application follows the SAP Fiori design guidelines, accessibility and keyboard support are built in, and new SAPUI5 versions bring improvements without custom code. Draft handling, value helps and variant management are also available without programming.
Extending instead of rebuilding
Many teams switch to freestyle SAPUI5 too early because a single requirement does not fit the standard. For OData V4, the flexible programming model offers extension points for this: custom sections on the Object Page, custom columns and actions, controller extensions for additional logic and custom pages within the same application. Building blocks such as table, form or chart can also be used in custom views and are controlled there by annotations as well.
This keeps most of the application standard, and only the part with special logic is custom code. SAP Fiori tools in SAP Business Application Studio and Visual Studio Code support this with the Page Map and Guided Development.
When freestyle SAPUI5 is the better choice
Some requirements are outside what the floorplans are designed for. These include highly interactive interfaces with drag and drop, graphical planning boards, custom visualisations and processes that cannot be described as a list with a detail page. If more than half of an application consisted of extensions, the standard would contribute little.
In these cases, a freestyle SAPUI5 application is easier to maintain than a Fiori Elements frame with many exceptions. Layout, state management, accessibility and adaptation to new SAPUI5 versions are then the responsibility of the team.
My rule of thumb: I first check whether the requirement can be described as a List Report with an Object Page. If so, I start with Fiori Elements and use extensions only where the standard is not sufficient.
Conclusion
Fiori Elements saves the most effort where data is searched, displayed and edited, which covers most business applications. Extension points handle individual special requirements without giving up the standard. Freestyle SAPUI5 pays off when the user interface itself is the product.
What has your experience been with extensions in Fiori Elements?
Questions about this article or your project? info@bissanda.com · All articles