abap2ui5.github.io valid

abap2UI5

Build SAP UI5 applications purely in ABAP - no JavaScript, OData or RAP

For agents: abap2UI5 project for building SAP UI5 apps purely in ABAP; offers a browser playground, searchable sample index (apps.json) and docs for developers.

abapsap ui5sample appsabap2ui5playgroundsap development

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T11:02:18.396Z. Cached copy · Source on abap2ui5.github.io

# abap2UI5

> Build SAP UI5 applications purely in ABAP - no JavaScript, OData or RAP
> required. One ABAP class per app: the framework renders the UI5 XML view,
> binds ABAP data both ways and dispatches events over stateless HTTP
> roundtrips. Runs from NetWeaver 7.02 to ABAP Cloud, on-premise and cloud.

This is the documentation site, written for people and published here in
markdown so a machine can read the same thing. Every link below is the raw
source of a page; drop the `.md` for the rendered version.

The facts, for a question that needs no page:

- Latest release: 1.148.0 - every release lists its changes in the [release notes](https://abap2ui5.github.io/docs/resources/changelog.md)
- License: MIT, commercial use included - no license key, no per-user fee, no subscription, no BTP required
- Runs on: SAP NetWeaver AS ABAP 7.02 and later, S/4HANA on-premise and private cloud, BTP ABAP Environment and
  S/4HANA Public Cloud (ABAP Cloud, released APIs only); the frontend is SAPUI5 or OpenUI5, 1.71 to 2.x, from a CDN
  or the UI5 the system ships - a system without internet access is fine
- Install: one abapGit pull of https://github.com/abap2UI5/abap2UI5 (the `702` branch below 7.50), then one HTTP service
- An app: one ABAP class implementing `z2ui5_if_app`; `main( )` runs on every roundtrip, the view is UI5 XML built in
  ABAP, data is bound both ways, and the app is stateless like any other UI5 app
- Not for: offline apps or real-time collaboration; the layout editor emits a class, there is no designer at runtime
- Support: the community, on GitHub issues and Slack; no vendor and no SLA
- Tooling: a browser playground at https://abap2ui5.github.io/playground/ that runs an app with no SAP system,
  a drag-and-drop layout editor that emits one app class, an MCP server with a Claude Code plugin, a VS Code
  extension, a linter (`@abap2ui5/linter` on npm, also a GitHub Action), and a headless frontend that tests an app
  in ABAP Unit - all on [Tooling](https://abap2ui5.github.io/docs/advanced/tooling.md), in the order a developer meets them

- [llms-full.txt](https://abap2ui5.github.io/docs/llms-full.txt): the whole documentation as one
  document, if you would rather fetch it once than page by page

- [the code map](https://github.com/abap2UI5/abap2UI5/blob/main/llms.txt): the same
  idea for the framework source - the package layering, the public API and
  where each concept lives. This file maps the prose, that one maps the code

- [the playground](https://abap2ui5.github.io/playground/llms.txt): how to open a class in the
  browser by URL, how to embed a running example in a page of your own, and
  where the samples are as data
- [the sample catalogue](https://abap2ui5.github.io/playground/samples/llms.txt): 863 complete apps
  from three repositories, each with a page of its own and the
  class in full. That file describes `apps.json`, the whole index as data:
  what each sample builds, the controls and libraries it needs, the oldest
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=abap2ui5.github.io · GET /v1/domain/abap2ui5.github.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for abap2ui5.github.io:
1. POST https://agentwebmap.com/v1/sites/abap2ui5.github.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://abap2ui5.github.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/abap2ui5.github.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/abap2ui5.github.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.