abap2UI5
Try it out

Community & support

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

abap2UI5 is open source and stays open source. People help each other in public, because transparency is how a project like this grows. Why that is the right model for a framework on SAP, how support works, what it stands on, and what you can give back.

The idea

Why open source is the right model for a framework on SAP

A UI framework sits under every screen you build on it. Whoever owns it owns a piece of your landscape: the license, the roadmap, the release cycle, the day it is discontinued. SAP customers know that dependency from both sides, and a second vendor on top of SAP doubles it.

Open source removes the owner. abap2UI5 is MIT licensed, every line is on GitHub, and the apps built with it are plain ABAP classes in your own system. Nothing can be withdrawn, re-priced or put behind a login, because there is nobody who could. If the project stopped tomorrow, your system would not notice.

It also changes how the framework gets better. Every question is asked in public and answered in public, so the answer serves the next reader too. Every bug report comes with a class that reproduces it. Every release is tested in the open, on NetWeaver 7.02 and on ABAP Cloud, and anyone can read the test. A vendor asks you to trust; this asks you to look.

  • No owner, no lock-inMIT since the first commit. Forks welcome. The apps stay yours, as classes in your system, whatever happens to the project.
  • Transparent by constructionIssues, pull requests, releases, the backlog and every test are public on GitHub. Nothing is decided in a room you cannot see.
  • Built with its usersThe people who run it in production ask, answer and contribute. The question you ask today improves the documentation for the next company.
  • Standing on open shouldersabapGit for installation and versioning, abaplint for every check, UI5 itself for the frontend: open projects all the way down, each with people worth supporting.

Support

In the open, four ways, and one more if you need it

  • GitHub issuesA bug, a question, a wish: open an issue. Anyone can, at any time, no account with the project needed; the answer stays public for the next person. Security reports are the one exception: not in a public issue, see SECURITY.md, acknowledged within three business days.
  • Slack channelThe abap2UI5 channel in the abapGit Slack: the quick question, the screenshot, the "has anyone done this". The people who run it in production read along and answer.
  • DocumentationThe manual, from the quickstart to the reference, maintained with the framework rather than left to age; most questions have their page there already.
  • Transparency: the code and the samplesEvery line of the framework is on GitHub, every test is public, and the sample catalogue holds 130 learning samples and 680 control examples that run in the browser. When in doubt, read what it actually does.

Need more? Write to us

Honestly, we hope it never comes to this. The goal is an ABAP team that is so much at home with abap2UI5 that support is as unnecessary as a support call for a selection screen or a transport into P. Most of the way there are the four channels above. But if you would feel better with somebody looking over the first screen, explaining a design or sitting next to you for a go-live, write to contact@abap2UI5.org and we will see what makes sense. One request: do not ask for a glossy slide deck full of buzzwords. There is none here, and that is the point.

→ SUPPORT.md in the framework is the source for this page.

What it stands on

Open foundations, all the way down

  • Open source, and it stays that wayMIT licensed since the first commit, every line on GitHub, forks welcome. No company owns it that could close it, change the license or put a release behind a login.
  • Built on abapGit and abaplintThe installation, the tests and every release stand on abapGit and abaplint. If abap2UI5 saves you money, consider supporting the people behind them too.
  • UI5 itself in the browserThe frontend is SAP's own UI5 library, not a copy of it: every control, every theme, every accessibility feature SAP ships, on the oldest supported release and on UI5 2.x alike.
  • A public test on every claimEvery release runs against Standard ABAP and ABAP Cloud, is downported to NetWeaver 7.02 and opened in the browser on both ends of the UI5 range. The tests are in the repository; verified on lists what each one holds.

What you can give back

Free to use is not the same as free to make

Those zeros on the cost page are written in somebody's evenings. If abap2UI5 saves your project time or money, any of these pays it back, and none of them costs a budget line.

  • Send a pull requestA fix, a sample, a sentence in the documentation: send it as a pull request. Every one is reviewed in the open, and the next release carries it.
  • Answer somebodyOne reply under an issue or in Slack saves somebody else an afternoon, and the answer stays public for the next person.
  • Add-ons: share yoursSelection screens, table maintenance, popups, a launchpad KPI: the building blocks live as add-ons in the open. The screen you solved for your plant is somebody else's next week.
  • Say what you buildA post on LinkedIn with #abap2UI5, a talk at your user group, a row under Who runs it: that is how the next decision maker learns it exists.
  • Add your companyOne row under Who runs it is what answers is anybody actually running this? for the next decision maker.
  • Sponsor the workSponsoring the contributors says the release you pull next month matters to you.

→ Back to the page for decision makers, or straight to who runs it.