Development
Fiori development builds custom apps and extensions when standard apps do not meet a need. Modern Fiori development uses the RAP model, CDS and OData on the backend with UI5/Fiori Elements on the front-end, developed in Business Application Studio.
Follow the clean-core principle: build extensions on approved frameworks (side-by-side on BTP, or in-app via released APIs), not by modifying standard, so your apps survive upgrades and cloud moves.
- SAP Business Application Studio (BAS) is the cloud development environment for Fiori/UI5, with wizards, templates (including Fiori…
- Often you extend a standard Fiori app (adding a field or logic) rather than building from scratch, using approved extension points.
- CDS views: model the data on HANA.
- Watch out: Freestyle builds where Fiori Elements + RAP fit.
The modern development stack
- CDS views: model the data on HANA.
- RAP (ABAP RESTful Application Programming): define behaviour and expose OData services.
- OData: the service the app consumes.
- UI5 / Fiori Elements: the front-end, template-driven where possible.
Where you build
SAP Business Application Studio (BAS) is the cloud development environment for Fiori/UI5, with wizards, templates (including Fiori Elements) and deployment tooling. ABAP Development Tools (ADT) in Eclipse handle the CDS/RAP backend. Together they are the modern Fiori toolchain.
Extending standard apps
Often you extend a standard Fiori app (adding a field or logic) rather than building from scratch, using approved extension points. This keeps you close to standard (clean core) while meeting the specific need.
Clean core
Follow the clean-core principle: build extensions on approved frameworks (side-by-side on BTP, or in-app via released APIs), not by modifying standard, so your apps survive upgrades and cloud moves.
Common pitfalls
- Freestyle builds where Fiori Elements + RAP fit.
- Modifying standard apps instead of using extension points.
- Ignoring clean core, painful upgrades later.