SAP Fiori tools
SAP Fiori tools is a set of extensions for SAP Business Application Studio and Visual Studio Code that generates, configures, previews and deploys SAP Fiori elements applications. SAP Fiori tools covers the front-end project, from the application wizard and Page Map to mock-data preview and deployment, while the OData service behind the app is built with other tools.
Quick facts
- Type
- Developer tooling (IDE extensions)
- Layer
- UI applications; SAP BTP
- Runs in
- SAP Business Application Studio (preinstalled in SAP Fiori dev spaces), Visual Studio Code
- Main extensions
- Application Wizard, Application Modeler (Page Map, Page Editor), Guided Development, Service Modeler, XML Annotation Language Server
- Deploys to
- ABAP systems and Cloud Foundry on SAP BTP
- Who works with it
- SAP Fiori developers, full-stack developers using CAP or RAP
- Applies to
- SAP S/4HANA (all deployment options), SAP BTP
Layer: UI applicationsWhere it sits ▾
What does SAP Fiori tools include?
In Visual Studio Code, installing the SAP Fiori tools extension pack adds these extensions:
| Extension | What it does |
|---|---|
| Application Wizard | Generates SAP Fiori elements projects from a floorplan or a custom page, standalone or inside a CAP project |
| Application Modeler | Page Map for pages and navigation; Page Editor for page settings; Data Editor for mock data |
| Guided Development | Step-by-step feature guides that insert code and annotations for common requirements |
| Service Modeler | Visualizes the OData V2 or V4 service, including back-end and local annotations |
| XML Annotation Language Server | Code completion and validation for annotations in XML files |
| XML Toolkit | General XML editing support |
Beyond the extensions, the toolset previews apps with live or mock data, validates projects, adds reuse libraries, creates adaptation projects for SAP-delivered apps and deploys to ABAP systems or Cloud Foundry. In SAP Business Application Studio, the SAP Fiori dev space comes with these tools preinstalled. SAP Fiori tools is therefore a toolkit for the front-end project, not a runtime or a framework.
How does SAP Fiori tools support the development lifecycle?
Suppose Alder Manufacturing needs a list report for open purchase orders, on an OData V4 service built with RAP:
- Generate. The Application Wizard connects to the system, lets the developer pick the service and the list report and object page floorplan, and creates the project with its app descriptor.
- Model. The Page Map shows pages and navigation; the Page Editor changes settings such as table type or initial loading. SAP Fiori tools saves these edits as changes to the project files or as UI flexibility changes.
- Annotate. Guided Development and the annotation language server help add UI annotations to local files or, for CAP, to CDS files.
- Preview. The app runs locally against the live service or with mock data, so UI work can continue when the backend is not ready.
- Deploy. The deployment configuration targets the ABAP repository or Cloud Foundry; an undeploy command removes the app again.
Each step produces normal project files, so the result can be versioned and reviewed like any other code. SAP Fiori tools shortens the path from service to running app without hiding what it generates.
What are the strengths of SAP Fiori tools?
- Fast start on the right floorplan. Generated projects follow SAP's current SAP Fiori elements setup, which removes boilerplate and avoids hand-built descriptors.
- Visual configuration. The Page Map and Page Editor expose manifest settings and annotation-driven options without memorizing every property.
- Learning built in. Guided Development shows how a feature is implemented, which helps developers who are new to annotations.
- Backend independence during UI work. Mock data lets designers and developers iterate before the service is finished.
- One toolset for both IDEs. The same extensions run in SAP Business Application Studio and in a local Visual Studio Code.
- Safe extension of standard apps. Adaptation projects create app variants that reference the original app instead of copying it.
For SAP Fiori elements projects, SAP Fiori tools is the toolset that SAP's own SAPUI5 documentation and tutorials build on.
Where does SAP Fiori tools stop?
- Front end only. The Service Modeler can display back-end annotations but not edit them. ABAP CDS views, behavior definitions and service bindings are maintained in ABAP Development Tools, CAP models in CDS files.
- Focused on SAP Fiori elements. SAP's documentation states that the freestyle SAPUI5 templates in SAP Fiori tools are deprecated and recommends the custom page of SAP Fiori elements for OData V4 instead. OData V2 projects remain possible, but SAP recommends OData V4.
- AI features change quickly. The Project Accelerator of SAP Fiori tools AI, which runs in SAP Business Application Studio, is planned to be deprecated at the end of 2026 in favor of the MCP server for SAP Fiori and skills, available in VS Code and SAP Business Application Studio.
- Licensing for some features. SAP notes that certain features may need a separate license; the Project Accelerator, for example, requires SAP Build Code.
- Generated is not finished. Wizards produce a working skeleton; data model quality, authorizations and performance still depend on the service.
SAP Fiori tools accelerates what SAP Fiori elements can express; it does not design the service or the process behind the app.
What are common mistakes with SAP Fiori tools?
- Starting new apps on OData V2. V4 gives access to building blocks and custom pages; choose V2 only when the backend offers nothing else.
- Generating a freestyle template by habit. A custom page in SAP Fiori elements for OData V4 keeps framework features such as building blocks while allowing custom layouts.
- Fixing back-end problems with local annotations. A local annotation file can mask a wrong CDS annotation in one app while every other consumer still sees the error. Fix it at the source when the service is shared.
- Skipping the mock-data and validation steps. Project validation and mock previews catch destination and configuration errors before deployment.
- Ignoring the SAPUI5 version of the target system. Generating against the newest SAPUI5 and deploying to an older front-end server leads to missing features; set the minimum version to match production.
Most SAP Fiori tools issues are choices made in the wizard's first screens, not defects in the extensions.
SAP Fiori tools vs. SAP Business Application Studio vs. SAP Fiori elements: what is the difference?
| SAP Fiori tools | SAP Business Application Studio | SAP Fiori elements | |
|---|---|---|---|
| What it is | IDE extensions for SAP Fiori development | Cloud development environment on SAP BTP | SAPUI5 framework that renders floorplans from annotations |
| When it acts | Design time | Design time | Runtime, in the user's browser |
| Relationship | Preinstalled in SAP Business Application Studio; also runs in Visual Studio Code | Hosts SAP Fiori tools in its SAP Fiori dev space | What SAP Fiori tools generates and configures |
| Question it answers | How do I build and deploy the app efficiently? | Where do I develop? | How is the app's UI produced? |
SAP Fiori tools is the toolkit, SAP Business Application Studio is one place to run it, and SAP Fiori elements is the framework the resulting apps run on.
FAQ
Is SAP Fiori tools free?
SAP Fiori tools is available as an extension pack for Visual Studio Code and preinstalled in SAP Business Application Studio, which itself is a licensed SAP BTP service. SAP's feature scope description notes that certain features may require a separate license; the AI-based Project Accelerator, for example, requires an SAP Build Code subscription.
Can SAP Fiori tools build freestyle SAPUI5 apps?
SAP Fiori tools still offers freestyle SAPUI5 templates, but SAP's documentation marks them as deprecated. SAP recommends the custom page of SAP Fiori elements for OData V4 instead, which allows custom layouts while keeping building blocks and other framework features.
What is the Page Map in SAP Fiori tools?
The Page Map is part of the Application Modeler extension. It shows an SAP Fiori elements app's pages, navigation and service entities, lets developers add or delete pages and navigation, and opens the Page Editor, where page settings are changed without editing files by hand.
Can SAP Fiori tools edit ABAP CDS annotations?
Not directly. The Service Modeler displays back-end annotations but cannot edit them, so ABAP CDS annotations are maintained in ABAP Development Tools. SAP Fiori tools edits local XML annotation files and, in CAP projects, CDS annotation files.
Does SAP Fiori tools work with SAP S/4HANA on-premise?
Yes. SAP Fiori tools connects to ABAP systems to read OData services and deploys apps to the ABAP repository, which covers SAP S/4HANA on-premise and Private Edition. Adaptation projects for SAP-delivered apps target these systems as well as SAP S/4HANA Cloud Public Edition.
Sources
- SAP Help Portal: Developing SAP Fiori elements applications with SAP Fiori tools
- SAP Help Portal: SAP Fiori tools — Visual Studio Code setup and extension pack
- SAP Help Portal: Feature scope description for SAP Fiori tools
- SAP Help Portal: Developing an application (Page Map, Page Editor) in SAP Fiori tools
- SAP Help Portal: Generating an Application with the Project Accelerator Using SAP Fiori Tools AI
- Applies to
- SAP S/4HANA on-premise · SAP S/4HANA Cloud Private Edition · SAP S/4HANA Cloud Public Edition · SAP BTP
- Last reviewed