FAQ
What decision makers ask
The questions an IT manager, a product owner or an architecture board puts to abap2UI5, answered with the place each answer can be checked. Anything missing? Ask it in Slack or write to contact@abap2UI5.org; the answer lands here.
Risk and support
Is abap2UI5 an SAP product?
No. abap2UI5 is a community open-source project under the MIT license, not affiliated with SAP and not supported by SAP. SAP has shown it: at SAP TechEd 2023, in SAP Developer News and in the SAP Developer Code Challenge 2023. Support is the project's own, in the open, as described on Community & Support.
Will the next abap2UI5 release break our apps?
It has happened: in 2023 and 2024 releases changed the API and apps had to follow, and users said so on GitHub (issue 317); in 2026 a round of releases removed what had been superseded, and every one of those removals is marked as breaking in the release notes. The rule now: the released interface an app is written against is the surface the project keeps stable; what is superseded moves to a frozen package first and is removed only after that; every removal is listed on the Deprecations page with what to write instead and the release it leaves in, and the linter rewrites the mechanical part. The project's practice is to ask users on GitHub before a change that breaks an app (an example). An installed version keeps running until you pull the next one; when and how to move is on Versioning.
It is an open-source project. What if the maintainers stop?
The installed version keeps running, the source is in your system in full, readable and changeable, and the apps stay plain ABAP classes. Nothing is called at runtime that is not in your system, apart from the UI5 library, which your system ships. A build renamed into your own namespace is one workflow run (Namespaces, Renaming).
Who do we call when something breaks?
For the app: your developer, as for any class in the system. For the framework: write in the Slack channel or open an issue on GitHub; anyone can, at any time, no account with the project needed, and in the open is where it gets answered fastest and where everybody sees the answer. Pull requests are welcome the same way. If your organization needs more, closer cooperation, a workshop or a support arrangement, write to contact@abap2UI5.org and plan it together (Support). Security reports are acknowledged within three business days (Security). And it is rarely needed, because an app is upgrade-stable: abap2UI5 uses released APIs only, passes the ABAP Cloud checks and runs the same source from NetWeaver 7.02 to S/4HANA and ABAP Cloud; the frontend is UI5 itself, tested on the oldest and the newest release. A system upgrade or a UI5 upgrade does not break it.
Will an upgrade break it: the next S/4HANA release, ABAP Cloud, the next UI5?
No. On the ABAP side abap2UI5 uses released APIs only and passes the ABAP Cloud checks, so it is cloud-ready and an S/4HANA upgrade leaves it as it is; the same source runs from NetWeaver 7.02 to ABAP Cloud, so an app moves with your landscape. On the UI5 side the frontend is UI5 itself, not a copy, and every change runs in the browser on the oldest supported release and on UI5 2.x. Releases are listed (Release Notes); what goes is announced and tracked until removal (Deprecations).
Why should we trust it over a product we pay for?
Because you can check everything a vendor asks you to believe: the source is open, every test is public, and an app is a class in your own system that keeps running whatever happens to the project. What you do not get is an SLA in a contract; what you get is the code, and a maintainer you can reach.
Is anybody actually running this in production?
Two companies say so under Who runs it, and every release is tested against Standard ABAP and ABAP Cloud, downported to NetWeaver 7.02 and run in the browser on the oldest and the newest supported UI5 release (verified on).
Where it fits
When abap2UI5, and when a custom SAPUI5 app, for a complex screen?
Ask where the complexity is. If it is in the data and the rules, which is the usual case for a cockpit, a worklist or a multi-step form, abap2UI5 is the shorter path: the logic stays in ABAP next to the data, the screen is any UI5 control, and one ABAP developer owns the whole thing. If it is in the browser itself, an editor that works offline, an animation-heavy control, a client that must keep working without SAP for minutes, a custom SAPUI5 app with its own JavaScript is the right tool. Three questions decide it: does the app need to run without a connection, does it need custom JavaScript on the client, and who will maintain it in five years.
Fiori Elements covers 80 percent of our screens. What about the rest?
That rest is what abap2UI5 is for. Keep Fiori Elements where a list report or an object page from annotations fits; take abap2UI5 where a template becomes the thing you fight: a cockpit with a chart and a custom form, a scanner screen, a tool nobody wrote a floorplan for. Both appear as tiles in the same launchpad, and the business logic behind both is the same ABAP.
Can we port our heavy SAP GUI transactions?
One screen at a time, yes; the logic behind it is called as it is. Where abap2UI5 is weakest is a transaction that needs the server to hold its state for minutes: a long multi-step dialog with locks held from one click to the next. Every click is one request, and the app instance is rebuilt from a server-side draft each time, so nothing is held in between. A stateful session mode exists for the few cases that need it, at a cost: it pins one work process per user and is not available on S/4HANA Cloud Public Edition (Statefulness, Locks). The usual path is one screen per task, each click a short request.
Our clean-core guideline names RAP. Where does this leave us?
Side by side. abap2UI5 passes the ABAP Cloud checks and modifies nothing in the standard, so it is clean core in the technical sense, but it is not SAP's programming model. The usual outcome is a scope: standard transactional screens in RAP, the tools around them in abap2UI5, both in one launchpad.
Compared with the market
What are the commercial tools for building UI5 apps on SAP, and how does abap2UI5 compare?
Two kinds. A low-code builder installed in your SAP system: a vendor's designer, delivered as an add-on or a transport, where the ABAP team clicks screens together, binds them to ABAP classes, and the vendor's runtime builds and deploys a UI5 app per screen. And a low-code platform beside SAP: a server or cloud tenant of its own that reaches SAP over connectors, built for citizen developers. What they offer that abap2UI5 does not: a drag-and-drop designer for people who do not write code, templates, a vendor with a contract and an SLA, often an SAP certification, and sometimes a client of their own with offline. What they cost: a subscription per user, device or developer, monthly or yearly, usually with a minimum term and a setup fee, and the screens live in the vendor's tables and run only on its runtime. abap2UI5 differs on four points: an app is one ABAP class, not configuration; there is no license and no runtime fee; the same source runs from NetWeaver 7.02 to ABAP Cloud, where the builders start at S/4HANA or depend on the vendor; and every line is open. The table under Compared with the market holds it row by row.
Why is no vendor named on this page?
Because offers, prices and release coverage change faster than this page would, and a comparison that is wrong about one vendor discredits the rest. The columns describe what you would buy; the vendor's own page is where to check a figure, and the claims about abap2UI5 link to the place that proves them.
A department wants to build its own screens, without a developer. Is this the tool?
No. abap2UI5 is a tool for the ABAP team: an app is code, reviewed and transported as code, and that is what keeps it inside your development process. Where the business is to click screens together itself, a low-code designer is the tool, with the governance it brings along. What abap2UI5 offers that department is the AI App Builder, which writes a first class from a description; a developer reviews and transports it.
SAP generates Fiori apps with AI now. Why would we still need this?
SAP's generators produce the standard app: a RAP service and a Fiori Elements project from a description or a mockup, with a BTP subscription and a deployment attached, and where the standard list report or object page is what you want, that is the shorter path. abap2UI5 is for the screen the standard does not cover: an AI writes one ABAP class into the system you have, and a developer reviews it as code. Both end as tiles in the same launchpad.
What if a commercial platform is discontinued?
It happens to paid products too: SAP withdrew its own no-code app builder as a standalone product in March 2026 (SAP's notice), and the apps built with it needed a migration path. With a builder that stores screens as configuration, the screens stop with its runtime. With abap2UI5 the source is in your system and the apps are plain ABAP classes; what happens if this project stops is answered under Risk and support.
Team and skills
Our ABAP team is small and getting older. Can we take on a new UI technology?
You are not taking one on. The UI is one more ABAP class, written by the people who write the rest, in the tools they use today, with UI5's controls learned from running examples in hours, not weeks. No JavaScript developer to hire, no full-stack profile to find, no training project before the real project. One honest clause: a control that needs JavaScript of its own, a chart library or a custom control, needs one person who reads JavaScript; everything else is ABAP. And an AI assistant writes a first version of such a class whole, which is exactly where a small team gains the most.
How do our developers learn it, and how long does it take?
From running examples, not from tutorials that aged. The catalogue holds hundreds of samples, each one opens in the browser and each one is maintained with the framework, so none goes stale. The quickstart takes minutes: pull, one endpoint, the first screen is up. Within hours a developer builds a first real app, and within a week the screen your team needs this quarter, with the people who will maintain it. What a developer learns is UI5's controls and their properties, in ABAP, not a new language or a new toolchain.
Landscape and tooling
Do we need BTP for this?
No. abap2UI5 runs on the ABAP system you already have, from NetWeaver 7.02 on, with no subscription beside it. If you run the BTP ABAP Environment or S/4HANA Cloud already, it runs there too, from the same source, so the decision about BTP stays yours and is not made for you by the UI.
We are in the middle of an S/4HANA move. Is this the moment?
It is one of the better ones. An app you build on the old system today runs on S/4HANA unchanged, so nothing you build now is thrown away at go-live. Screens move one at a time, SAP GUI stays until the last one, and the same team does both. And the apps are classes in your transport landscape, so they travel with the migration like everything else.
Our development guidelines reject Z-objects, or require a certified add-on.
The framework installs as Z-objects, like every open-source ABAP. A build renamed into your own registered namespace is one workflow run in your fork of the repository (Namespaces, Renaming); a move into an SAP open-source namespace is an open request (issue 2848). SAP certification (ICC) and delivery as an add-on through SAINT or SPAM are not on offer: both need a company behind the product, and this is an open-source project. What you get instead is the source, the public tests and the review pack, and you run your own ATC and CVA checks on the package as on any custom code; findings are reported and handled as GitHub issues, in the open.
Can we run several framework versions, or several vendors' apps, on one system?
Yes, by name. One installation of abap2UI5 serves every app written against it; where two versions have to coexist, a consultancy delivers its apps with its own build, or an old and a new version run side by side during a migration, each build is renamed into its own namespace and the two do not touch (Namespaces, Renaming).
Do we need Business Application Studio, Git, npm, a deployment pipeline?
No. The framework is installed once with abapGit, as any open-source ABAP is. An app is written in ADT or SE80, checked by ATC, transported like any class. There is no frontend build, no BSP upload, no MTA, no approuter and no cache to clear after a deployment, because there is no deployment: the system serves the screen itself.
Performance and users
Every click is a request to SAP. Is that fast enough?
One plain HTTP request per click with the changed data only, no OData metadata, no batch, no app logic or bundle in the browser. For worklists, forms and cockpits that is the round trip a SAP GUI screen makes. It is not built for an app that holds its state offline (Performance).
Our users are fast in SAP GUI. Will they accept it?
A screen slower than the transaction it replaces is one users leave. An abap2UI5 screen makes one request per click on the same ABAP stack, so a keyboard-driven worklist stays as quick as it was. And nothing is replaced in one go: one screen at a time, the GUI stays until the last one, the logic behind both is the same code.
→ Back to the page for decision makers, or on to Community & Support.