Across the many events in which we have participated over the past few months, including Sapphire, UI5con, SAP Connect Day for UX, and several DSAG technology days, we have heard many questions from customers and partners about SAP Fiori elements, SAP Fiori tools, SAP Fiori apps, our MCP servers. and how they fit into the future with Joule Work. In this post, I’ll answer questions on using SAP Fiori elements, the underlying technologies, how our AI tools work for building apps, and a little on the future of the SAP S/4HANA Cloud application experience.
Use SAP Fiori elements whenever it makes sense
When should we use SAP Fiori elements?
Use SAP Fiori elements when the app fits common enterprise patterns such as list report, object page, or custom page comprised of building blocks. If the business scenario requires a highly customized interaction model, specialized visualizations such as maps or process diagrams, or full control over every UI behavior, freestyle SAPUI5 may be more appropriate.
Generally, the answer is “start with Fiori elements and only move toward freestyle SAPUI5 where the business requirement justifies the added development and maintenance cost” and not “always use Fiori elements.”
We offer guidance for developers in the UI5 demo kit.
What happens if our requirements do not fit the standard SAP Fiori elements floorplans exactly?
Use a layered approach: you can start with a floorplan, extend it with building blocks, and fill any remaining gaps with freestyle SAPUI5. Building blocks still benefit from SAP Fiori design consistency and standard behavior such as draft handling. This gives more flexibility without immediately taking on the full maintenance burden of freestyle SAPUI5.
How do we prove the business value beyond saying developer productivity improves?
While we can provide a list of general benefits of using SAP Fiori elements: improving developer productivity, driving UX consistency, and reducing the cost of delivering enterprise readiness features, the specific savings will depend on your use case and cost structure.
For calculating the business value of using SAP Fiori elements, we recommend that you pick one process, compare the current task completion time, training cost, error or rework rate, and support tickets, then measure the same items after delivering a Fiori elements-based app. The value case is strongest when it links UX consistency to measurable outcomes in your business, not just faster coding.
How does SAP Fiori elements support a clean core strategy rather than creating more custom code?
Clean core is a set of principles for continuous transformation, resilient processes, seamless integration, efficient operations, and high data quality. Fiori elements supports clean core by encouraging extension through metadata, annotations, reusable building blocks, and defined extension points instead of modifying the ERP core. SAP’s clean core extensibility guidance is intended to let SAP S/4HANA Cloud customers extend where needed while still allowing smooth upgrades and handling of extensions.
The technologies behind SAP Fiori elements
What is the SAP Fiori elements learning curve for developers who already know SAPUI5 or ABAP?
For SAPUI5 developers, the main shift is from hand-coding much of the UI to working with OData services, annotations, building blocks, and floorplans.
For ABAP developers, RAP plus OData and annotations are how you build on-stack apps.
SAP Fiori tools reduces the learning burden by generating projects, providing guided development steps, code snippets, code completion, app editing, previews with mock or live data, troubleshooting tips, and AI-assisted generation.
Try a quick example to see how easy it is.
How do we choose between RAP and CAP, and on-stack development vs. side-by-side BTP development?
If the app requires tight SAP S/4HANA integration, on-stack development with the SAP S/4HANA Cloud ABAP environment and RAP may be the right fit. If the app is cloud-oriented, loosely coupled, or integrates with multiple systems, CAP or side-by-side development on BTP can be more appropriate. Fiori elements apps run in the browser with OData V4 and annotations, connected through either RAP or CAP to your SAP S/4HANA data sources.
How our AI tools accelerate application development
Does AI-assisted development work with SAP Fiori elements faster?
AI can accelerate first drafts, repetitive configuration, and guided development, but teams still need developer review, architecture governance, security checks, and testing before production use. As our chief architect says “you own the code!”
How do we manage the risk of AI generating incorrect or inconsistent code?
Treat AI output as assisted development, not autonomous delivery. MCP provides structured project metadata, executable functions, and guidance for app development tasks. Agent skills can support repeatable intents such as creating apps, adding visualizations, filtering, driving the CLI, validating code with ESLint, and writing OPA5 tests.
The practical control model is to combine AI generation with established development guardrails: linting, automated tests, code review, architecture rules, and clean core governance.
The future of the application experience is a mix of SAP Fiori and Joule Work
If SAP Fiori and Joule Work are complementary, should we still invest in apps?
Yes. Apps remain the foundation of SAP Cloud ERP while conversational experiences provide an adaptive UX option. Application experiences continue to provide transactional and analytical capabilities from SAP S/4HANA systems; Joule Work adds another interaction layer for AI-native, agentic, and generative experiences.
Companies should keep building clean, well-structured application experiences and expose the right data and services so future engagement-layer experiences can build on them.
How do I start working with SAP Fiori elements?
Start with a small, high-value use case rather than a broad app rollout. First, check whether a standard SAP Fiori app already exists and can be used as is or adapted. If you need a custom app, choose a scenario that can use a set of building-blocks, define the OData service and annotations, use SAP Fiori tools to generate, and iterate.
You don’t need to figure it out on your own. Use SAP’s extensive resources for support: the SAP Fiori development portal, SAPUI5 documentation, SAP Community topic pages for Fiori elements and Fiori tools, SAP Learning content.
Do you have more questions on SAP Fiori elements or SAP Fiori tools? If so,
- Post your question in the comments below.
- Join our monthly development roundtable call.
- Attend an upcoming SAP Connect Day for UX in Newtown Square on September 2, 2026 or Walldorf on December 8, 2026
Happy coding!
Source link
