abap2UI5

UI5 apps for ABAP,
built by the team you already have

Your ABAP developers build browser apps for the desktop, the tablet and the handheld scanner, in the SAP system you already run. The business logic and the data stay in SAP. You need no JavaScript team, no extra platform and no license fee. Open source since 2023, in production on the desktop and on the warehouse floor.

One ABAP class in the ABAP development tools, and the app it produces on a handheld: a table of sales orders with status and amount

What you can build

Every process in SAP that needs a screen

Whatever runs on paper, in Excel or in SAP GUI today becomes a browser app. Each card opens a running example.

A scan field for the warehouse: every scan lands in the list, no tap needed

Warehouse & logistics

Goods receipt, picking, stock transfers and counts on scanners, handhelds and tablets.

See the example app
An object page: header, status and sections, as a work order would show them

Maintenance & service

Work orders, notifications and checklists for technicians, in the workshop or at the machine.

See the example app
A planning calendar, as a shift or capacity plan would use it

Production & shop floor

Confirmations, quality inspections, shift plans and the special processes the standard never covered.

See the example app
A notification inbox with priorities and actions

Approvals & workflows

Purchase requisitions, invoices, leave and master-data requests: approve in one click, in the launchpad, in Teams or on the phone.

See the example app
Launchpad tiles with KPIs, trends and figures

Cockpits & dashboards

KPIs, charts and monitors for one team or one process, live from SAP, without a data warehouse or a BI tool.

See the example app
A form with an edit switch, instead of a paper form

Paper & Excel replaced

Forms, checklists and spreadsheets that live outside SAP become apps that write straight into it.

See the example app
A table with search, sort, filter and row actions

SAP GUI modernized

Reports, lists and transactions turn into browser apps one at a time, with the logic behind them unchanged.

See the example app
A feed app on a phone

Mobile, without an app store

Every app runs in the browser on iOS and Android, so there is no app store and no rollout.

See the example app

One app, every device

The same app, opened on a phone, a tablet and a desktop. It runs in the browser on iOS, Android and Windows, on rugged industrial handhelds too, and the layout adapts on its own.

The sales orders app on a phone: one order per row, region and status folded under it
Phone and handheld scannerPicking, counting, approving at the shelf or on the way.
The sales orders app on a tablet: the full table
TabletAt the machine or the goods receipt: the full table, touch-sized.
The sales orders app on a desktop: the full table with room to spare
DesktopThe worklist and the cockpit at the desk, next to the Fiori apps in the launchpad.

→ Browse the example apps for the screen closest to yours: hundreds of them, each running in the browser. Or read In a Nutshell for how it works.

Compared with the market

Where it is the shorter path, and where it is not

Four ways to get a UI5 app on SAP, next to abap2UI5. No vendor is named, because offers and prices change; each column describes what you would buy.

Where the parts of an app are, in three approachesabap2UI5: the browser talks to your SAP system, which holds app, logic and data. A custom UI5 app adds JavaScript, a deployment and an OData service. A low-code platform adds its server and a connector.abap2UI5Browsershows the screenYour SAP systemThe app: one ABAP classBusiness logicDataCustom SAPUI5 appBrowserruns the app's JavaScriptYour SAP systemFrontend deploymentOData serviceBusiness logic and dataLow-code platform beside SAPBrowsershows the screenThe platformapps and logic, own server or tenantConnectorYour SAP system: datadashed: an extra part to build, buy or operate
Where the parts are. With abap2UI5 the browser talks to your SAP system and nothing is in between; the two alternatives shown add parts of their own.

✓abap2UI5 is ahead–abap2UI5 is not ahead

abap2UI5RAP + Fiori ElementsCustom SAPUI5 appLow-code builder in your SAP systemLow-code platform beside SAP
License costNone: MIT, for any number of users, systems and appsPart of the SAP licensePart of the SAP licenseSubscription per user, device or developer, often with a minimum term and a setup feeSubscription per user or app, plus the tenant
Who builds the appsYour ABAP developersABAP plus CDS, RAP and annotation skillsJavaScript / UI5 developersThe ABAP team, in the vendor's designer, after its trainingCitizen developers, or developers trained on the platform
What an app isOne ABAP classCDS views, behavior definitions, a service binding and a generated UI5 projectA UI5 project and an OData serviceEntries in the designer's tables, built into a UI5 app per screenA model on the platform
Where the business logic livesIn ABAP, next to the data, as it does todayIn ABAP, behind CDS and annotationsSplit: JavaScript in the browser, a service in ABAPIn ABAP classes bound to the designer's views; the screen in the vendor's tablesOn the platform; SAP is reached over connectors
SAP releasesNetWeaver 7.02 up to ABAP Cloud, one source7.5x and laterYes, with OData effort per releaseDepends on the vendor: some from NetWeaver 7.x, some S/4HANA onlyAny, over the connector
Extra infrastructure and deploymentNone: one endpoint on your SAP system, and the system serves the screenFiori frontend server; a deployment per app and versionA frontend deployment (BSP, BTP or web server)The vendor's add-on or transport, a license key per system, the designer's build per appThe platform's server or cloud tenant
Lock-inLow: apps are plain ABAP classes written against one interface, and the framework stays in your systemSAP's programming modelLowScreens live in the vendor's tables and run only on its runtime; leaving means rebuildingApps live on the platform
SupportIn the open: Slack and GitHub issues, for anyone at any time; more by mail. No SLA in a contractSAP supportSAP support for UI5; your app is yoursThe vendor's SLA, in the contractThe platform's SLA, in the contract
8 more rows: speed, UI freedom, designer, offline, certification
abap2UI5RAP + Fiori ElementsCustom SAPUI5 appLow-code builder in your SAP systemLow-code platform beside SAP
Time to the first screenMinutes; hours to the first app. An ABAP developer learns UI5's controls from the examples, not a new languageAfter the model, the service, the project and a deploymentAfter the project setup, the tool chain and a deploymentAfter the add-on is installed and licensed; the vendors say days to the first appAfter the tenant and the connectors are set up
Freedom of the UIEvery UI5 control, any layoutSAP's floorplans and their extension pointsEvery UI5 controlThe components the designer offersThe platform's widgets; a Fiori look where the vendor offers one
Performance: what a click costsOne plain HTTP request carrying only what changed; no app code and no logic in the browserOData calls with metadata, batch and draft handling, and the Fiori Elements runtime in the browserOData calls and an app bundle per app, logic in the browserA generated UI5 app per screen, with the vendor's runtime in the browserA round trip through the platform and its connector
Source codeOpen, every line, on GitHubClosedUI5 open, your app yoursClosed; some vendors export the generated appClosed
Click-together designerNone: an app is code, with hundreds of examples to start from and an AI builder that writes the classNone: annotations, in ADTNone: codeYes: drag-and-drop, templates, versions, for people who do not write codeYes
Standard transactional appsPossible, but hand-built; the standard route is RAPIts home ground: list report and object page from annotationsHand-builtFrom the vendor's templatesFrom the platform's templates
Offline and a native clientNot built for it: a browser app with its connection to SAPOffline with extra toolingPossible, with effortSome vendors ship a client of their own, with offlineUsually a native client, offline possible
SAP certification, add-on deliveryNot on offer: no company behind it. The source, the public tests and the review pack insteadSAP's ownYours to certifyOften SAP-certified, delivered as an add-on or a transportA certified integration, beside SAP
What each column stands for
RAP + Fiori Elements
SAP's standard route: a list report or an object page generated from CDS annotations on a RAP service. Part of the SAP license, supported by SAP.
Custom SAPUI5 app
A JavaScript project with its own OData service, built in Business Application Studio or VS Code and deployed to the system or to BTP. What a UI5 agency delivers.
Low-code builder in your SAP system
A vendor's designer, installed as an add-on or a transport: screens are clicked together, stored in the vendor's tables and built into UI5 apps by its runtime. Licensed per user, device or developer. Several vendors sell one.
Low-code platform beside SAP
A server or cloud tenant of its own, reaching SAP over connectors; built for citizen developers, SAP is one of many backends. General-purpose platforms and SAP's own no-code builder belong here.

Where teams choose abap2UI5

  • The team is ABAP.An app is one class in ADT or SE80: debugged, checked by ATC, transported and unit-tested like any other. What developers still learn is UI5's controls, from the examples; it is not a new language.
  • The system is older than RAP.NetWeaver 7.02 to 7.4x have no RAP and a Fiori stack that is expensive to add. An app written there moves to S/4HANA unchanged.
  • The screen is yours, not SAP's.Tools, cockpits, monitors, admin consoles, anything that used to be a report. Where a Fiori Elements template becomes the thing you fight, this is the shorter path.
  • Performance where users notice it.The browser holds one generic shell, loaded once, and every click is one plain HTTP request with the changed data only. The work runs on the ABAP stack, next to the data.
  • Your Fiori apps and your logic stay.abap2UI5 apps are tiles in the same launchpad. A report, a BAPI, a function module: an app calls it as it is.

Where something else fits better

  • You want the SAP standard transactional app.A list report with an object page on S/4HANA, from a released CDS model: RAP and Fiori Elements are the shorter path, and the one SAP supports.
  • The app must work offline.Every click is one request to the SAP system, so the device needs a connection.
  • Your guideline mandates SAP's programming model.abap2UI5 is clean core in the technical sense, but it is not RAP. The usual outcome is a scope, not a replacement.
  • You want the transaction as it is, in a browser.SAP GUI for HTML and Screen Personas keep the transaction and change its look. abap2UI5 builds a new screen on the same logic. If the screen may stay, SAP's own route is shorter.
  • The business should click its screens together itself.abap2UI5 is a tool for the ABAP team: an app is code, reviewed and transported as code. Where a department is to build screens without a developer, a low-code designer is the tool. What abap2UI5 offers that department is the AI App Builder, which writes a first version from a description; the review stays with a developer.
  • Your rules need an SLA on paper.Support happens in the open, in Slack and on GitHub, and more can be planned with the maintainers by mail. What is not on offer is an SLA in a contract.

→ On-Stack or Side-by-Side and One App, Many Systems are the deployment scenarios in detail.

Enterprise readiness

Enterprise ready: your security, your process, your release cycle

Logon, authorizations and data stay SAP's, and the logic stays in ABAP. No part of an app runs in the browser, so there is no client logic to secure. Every rule that applies to ABAP, from code review to the four-eyes principle on transports, applies to an app unchanged.

abap2UI5A low-code builder in your SAP system
What an app isAn ABAP classEntries in the tool's tables, read by its runtime
Where a change is madeIn the development system, in the ABAP toolsWherever the tool's designer is open, possibly production
How a change travelsA transport, like any classThe tool's own export, or a customizing transport
What happens if the tool goes awayThe classes stay; they are plain ABAP in your systemThe apps go with it
  • Logon is SAP'sA request that reaches an app has passed SAP logon. The framework has no user store, token or session of its own.
  • Authorizations are SAP'sThe authorization on the service endpoint, and the app's own checks in its code, as a transaction does them.
  • Data changes are your code'sAn app posts through the same BAPIs, function modules or RAP actions as any program, so change documents and application logs apply unchanged.
  • Data stays on your systemThe app's data never leaves the SAP system. Between two clicks the framework keeps the app's state in one table on that system, deleted after four hours by default.
  • Tested on every releaseEvery change is tested on NetWeaver 7.02, Standard ABAP and ABAP Cloud, and in the browser on the oldest and the newest supported UI5. A system or UI5 upgrade does not break an app.
  • Security reviewed in the openA strict browser security policy, automated code scanning, a weekly dependency audit and a bill of materials (SBOM) with every release. The published security model is where a review starts.
  • Clean coreReleased APIs only, passes the ABAP Cloud checks, modifies nothing in the standard.
More: request logging and accessibility
  • Every request can be loggedA monitor records user, app, event, timings and errors per request. It is off until an installation switches it on.
  • AccessibleViews are standard UI5 views, so every control is as accessible as UI5 makes it. A change can be announced to a screen reader, and a high-contrast theme is one switch away.

No shadow IT. Every app is a class under your existing development rules, and no click-together designer bypasses them.

→ The review pack: everything a review board asks for, each line with the place that proves it. In detail: Security, Authorization, the security model, Accessibility and Verified on.

What it costs

No license fee, now or later. The bill is your developer's time.

0 license fees
  • No license key, no subscription, no fee per user, system or app
Framework licenseMIT, commercial use included, any number of users, systems and apps0
Platform, runtime, hostingOne service on the SAP system you already run0
SupportIn the open, for anyone at any time; pull requests welcome0
Developer timeAn ABAP developer writes the screen, as for any class; this is the billyour rate
Training and consultingWebinars, certification, a consultancy, if wantedoptional

A low-code builder bills per user, device or developer, often with a minimum term and a setup fee. Here the line that grows with adoption is zero.

  • Nothing to sign up forThe examples run in the browser without an account, and the framework is one abapGit pull.
  • Free to leaveThe apps stay plain ABAP classes, and the skill your team builds is ABAP. A build renamed into your own namespace is one workflow run.

→ More on the License and Support.

Where it runs

On the SAP system you already have, and nowhere else

The browser loads the standard UI5 library. The app, its logic and its data stay on your SAP system, with no middleware, extra server or frontend deployment.

Every SAP operating model, from one source

ABAP Cloud clean core, released APIs only: abap2UI5 passes the checks

  • SAP S/4HANA Cloud Public EditionClean core is mandatory; the same class runs, no rewrite on the way up.
  • SAP BTP ABAP EnvironmentThe standalone ABAP system on BTP, also usable as the side-by-side system.
  • S/4HANA Private Cloud and on-premise, in ABAP CloudThe ABAP Cloud language version on a RISE or on-premise system: abap2UI5 fits the clean-core tier there too.

Standard ABAP the classic language version, every release

  • SAP S/4HANA Cloud Private EditionRISE with SAP.
  • SAP S/4HANA on-premiseYour own data centre or a hoster.
  • SAP ECC and NetWeaver 7.02 to 7.5xWhere RAP and a Fiori stack are out of reach, and an app written today moves to S/4HANA unchanged.

What installation takes

  1. Pull the package with abapGit, as for any open-source ABAP
  2. Create one service endpoint and put an authorization on it
  3. Set the four production defaults: UI5 source, error details, content security policy, endpoint authorization

No job to schedule, no extra server, no schema to migrate on upgrade.

Two ways to deploy
  • On-stackabap2UI5 on the system where the data and the logic live. An app calls BAPIs, function modules or RAP actions directly, as any program there does. The usual setup, one abapGit pull.
  • Side-by-sideabap2UI5 on a separate ABAP system, the BTP ABAP Environment or a hub, and the apps reach the core over RFC or HTTP. For a core kept clean of custom UI, or one UI layer in front of several systems.
Where an app appears
  • Browser tab
  • Fiori launchpad tile
  • SAP Build Work Zone
  • Microsoft Teams
  • Microsoft Excel
  • iOS & Android
  • Inside your own UI5 app
Without internet access
A productive installation serves UI5 from the system itself, so nothing is loaded from outside (SAP Note 2943781).

→ Productive Usage, UI5 Versions and Integration.

AI

One class is the easiest thing for an AI to write and for your team to check

Your developers describe the screen, the AI writes one ABAP class, and your rules review and transport it like any other code.

  • One app, one fileThe whole app is one file, so there is no service, frontend project or deployment to generate and keep in sync.
  • In the tools your team usesPlugins for Claude Code and GitHub Copilot, skills for any agent, and an AI App Builder in the browser that builds an app from a description.
  • Checked before anyone looksThe abap2UI5 linter tests every class the AI writes, and the AI fixes what it broke before a developer reviews it.

No AI lock-in either. Claude, ChatGPT, Copilot or a local model, with your own key.

→ Try the AI App Builder, or read Developing with AI.

FAQ

What decision makers ask

What if the maintainers stop, will an upgrade break it, do we need BTP: twenty-five questions, answered on the FAQ page.

Who runs it

In production, in the open, since 2023

Two companies run it in production and say so here; one offers training. Far more systems use it than the list shows.

  • 2,900+ systems in two weekspulled the framework from GitHub, 23 October to 5 November 2026; every abapGit pull is one clone, each system counted once
  • 25+ contributorsfrom several companies, every change public
  • Release 1.149November 2026; a release most months, each one listed
  • Every release testedon NetWeaver 7.02, Standard ABAP and ABAP Cloud, on the oldest and the newest UI5

Talks, articles and videos

16 more, 2023 to 2026

→ The figures: the repository and its releases.

Get started

One real screen, one week, your own team

Decide from a screen your team built, not from a slide.

  1. Pick one real screenOne your team has to build this quarter, not a demo.
  2. Build it in a development systemWith the people who will maintain it, in the tools they use today.
  3. Review it like any ABAPRead the class, transport it, run the code checks, check the authorizations it asks for.
  4. Compare and decideHold the time and the systems it needed against any alternative or vendor quote.

Community & support

Open source, in the open, and better with every question

Why abap2UI5 is open source and stays so, how support works, what it stands on and what you can give back: on Community & Support.