Everything in ABAP
Type
Domain
Origin
Signals: 3
Content
More
Group by: None
UI5 custom control that runs an abap2UI5 app inside a host app
The page and the [abap2UI5](artifact:abap2ui5-abap2ui5) service have to share an origin: an `endpoint` that resolves to another origin is refused, and abap2UI5 rejects a POST whose `Origin` names another host. A host that routes by the URL hash, such as a Fiori elements app or an app with a UI5 router, needs abap2UI5 1.146.0 or later, because 1.145.0 clears the host's hash after every roundtrip. One frontend per page: the first control that starts decides which endpoint the frontend comes from.
Command-line checker for abap2UI5 app classes and their views
Event roundtrips and visual fidelity stay with a live run: the documentation leaves those to the project's MCP server and to [abap2UI5 for VS Code](artifact:abap2ui5-vscode-extension). A class that builds view parts in helper methods without the handle idiom cannot be statically reconstructed, and the render gate is then skipped with a notice while the property gate runs on what was reconstructed. A screenshot is not a preview of the app: nothing round-trips, no event reaches ABAP, and a table filled by a SELECT photographs empty unless a mock JSON file sits beside the source.
MCP server for the abap2UI5 check, deploy and run loop
Every gate here runs off-system, so what the class does on a real system and what the view does on the oldest UI5 release it has to serve are what the `pitfalls` catalogues carry and no local run can see. It runs abap2UI5 app classes, so ABAP that is not one has nothing here to deploy into. In system mode the sandbox tools are not offered, and an `app_act` event runs on the system as the configured user.
Parser for ABAP CDS DDL source with a typed AST
Transpiles ABAP to JavaScript to run on Node.js
TypeScript SDK over SAP's headless adt-ls language server
What adt-ls cannot do headless the maintainer puts out of scope, so a consumer that needs an ADT call the language server does not expose is back to speaking ADT itself. The README states the current runtime compatibility as verified on macOS arm64, against adt-ls 1.1.2 as the minimum and `1.1.2.202608131517` as the version tested. An Eclipse installation does not supply that runtime: SAP versions the two separately, so the VS Code extension has to be installed even where nobody opens VS Code.
ABAP ADT MCP server published as an npm scope and plugin
A descendant rather than a distinct idea: if what you need is the ADT surface itself, its ancestors are entered here too and one of them may already be in your stack.
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
Library for managing ABAP constants from registered sources
Quiet No published releases; repository quiet for 41 months.
Functional boundary Not in a production environment yet: the maintainer puts abaK in beta, says its API can still change and more tests are needed, and asks that a non-beta release be waited for.
AWS's ABAP MCP server for Amazon Q Developer and Kiro
Written for Amazon Q Developer and Kiro, and the central deployment path is ECS Fargate — the further you are from AWS, the more of it is scaffolding you do not need. Python rather than the Node most of this group uses. Its README says the repository is no longer maintained and that the latest version of ABAP Accelerator is shared after registering with AWS for [Modernization Agents for SAP on AWS](https://github.com/aws-for-sap/Modernization-Agents-for-SAP-on-AWS).
Configurable CSV reader and writer for ABAP
JSON renderer and parser for ABAP with camelCase conversion
JSON encoder and decoder for ABAP, modelled on Go's encoding/json
No published releases; repository quiet for 49 months.
Swagger UI for SAP NetWeaver Gateway services
No published releases; repository quiet for 49 months.
VS Code extension editing ABAP systems over ADT as a filesystem
ABAP class for descriptive statistics over an internal table
VS Code syntax highlighting for .abap files
Quiet No published releases; repository quiet for 27 months.
Functional boundary It binds to the .abap and .ABAP file extensions inside Visual Studio Code, so it does nothing for ABAP opened in another editor, or for source read from a system over ADT instead of from a file on disk.
DeepL translation plugin for the B-Tocs ABAP SDK
No published releases; repository quiet for 32 months.
LibreTranslate plugin for the B-Tocs ABAP SDK
No published releases; repository quiet for 28 months.
B-Tocs ABAP SDK plugin connecting to Ollama models
No published releases; repository quiet for 28 months.
TypeScript library reaching ABAP service instances on Cloud Foundry
ABAP report running custom SQL queries into an ALV grid
Replays stored database snapshots in ABAP unit tests
No published releases; repository quiet for 28 months.
ABAP debugger extension drawing objects as a Graphviz graph
No published releases; repository quiet for 97 months.
ABAP client for the DeepL translation service
No published releases; repository quiet for 54 months.
Generates signed JSON Web Tokens in ABAP
No published releases; repository quiet for 68 months.
Object-oriented wrapper around the Business Application Log
Mustache template engine for ABAP
No published releases; repository quiet for 28 months.
Report pushing ABAP objects to SAP Translation Hub and back
No published releases; repository quiet for 43 months.
Scripts running the ABAP Developer Edition in Docker
No published releases; repository quiet for 83 months.
JS/TS client for the ADT resources of an ABAP system
Not a tool a developer runs: it is a library to build one with, and it ships no editor, command line or interface of its own. Its sample connects with a plain HTTP URL, a user and a password, so a system that does not expose the adt ICF service that way is out of reach.
ABAP-native MCP endpoint that drives opted-in abap2UI5 apps
Stateful apps cannot be operated: a stateful session lives in one HTTP request and an MCP call is one request, so `app_start` refuses them. The repository carries no release yet and states the addon has not been run in production use, the 7.02 downport is lint-only with no 7.02 system having run it, and the ABAP Cloud HTTP service setup is written down but still to verify on your own system.
ALV table view generated from a DDIC structure
No published releases; repository quiet for 58 months.
Generates singleton ABAP cache classes from a macro call
No published releases; repository quiet for 26 months.
ADT backend for the ABAP Call Hierarchy Eclipse plugin
Report-style programming model for abap2UI5 on ABAP Cloud
Not a way to run existing reports unchanged: a report is rewritten as a class, and `CALL SCREEN`, dynpro modules, batch input, `SUBMIT` and native SQL are refused by the converter rather than mapped. Not an SAP GUI in the browser either: the programming model is classic and the screens are UI5, and the README points at abap2UI5-addons/sapgui for SE16N or SM37. Output has gaps the README names — ALV cells show dates and times as the model carries them rather than in the user's format, print is a text file because ABAP Cloud has no spool, and value tables for F4 are read on premise only.
Chainable logger for ABAP Cloud around CL_BALI_LOG
In-system ABAP source search by string or regular expression
Validation library for ABAP checking dates, emails and GUIDs
No published releases; repository quiet for 40 months.
Framework for runtime parameters, ranges and value mappings in ABAP
SAP's specification for serialising ABAP objects to files
Fluentd client in ABAP for sending log lines to a collector
No published releases; repository quiet for 96 months.
Runtime translation layer for SAP form labels, kept in a table
ABAP logging library with one interface across output targets
No published releases; repository quiet for 36 months.
Exports Business Application Log entries to Graylog or Loki
No published releases; repository quiet for 41 months.
Software-engineering metrics for an ABAP class or package
No published releases; repository quiet for 43 months.
Exposes ABAP stack metrics to a monitoring tool
The declared repository is archived.
Debugger script exporting an object hierarchy as Graphviz
No published releases; repository quiet for 67 months.
ABAP client for calling and asserting on OData services
Generates ABAP client classes and server stubs from OpenAPI
OTLP serialisation of traces, metrics and logs in ABAP
Framework activating custom ABAP enhancements through a Fiori app
Anything below SAP S/4HANA 2023 FPS03 (ABAP 7.58), and any system not running the ABAP Cloud development model: those two are the prerequisites the README names, and it states that the framework targets ABAP Cloud exclusively.
Framework for multi-step ABAP processes with monitoring
Only on SAP S/4HANA 2023 and 2025, on premise or private cloud: [SAP S/4HANA Cloud, Public Edition](external:sap-s4hana-cloud-public-edition) and the [SAP BTP ABAP environment](artifact:btp-abap-environment) are listed as coming soon, and a 2023 system has to leave out `ZABAP_PRC_EVENTS_SE_2025`, whose event-based side effects rely on APIs released with S/4HANA 2025. Not for a system that already carries a copy, because object names are global and two versions cannot live side by side, and not for a productive system by way of the `ZABAP_PRC_DEMO*` packages, which the README states are not intended for one and whose init classes delete and rebuild their own tables on every run. While the major version is 0 the public API is not stable: minor bumps carry breaking changes with no deprecation period, so productive use means pinning a tag and reading the CHANGELOG before every upgrade.
Prometheus client for ABAP, installed with abapGit
No published releases; repository quiet for 39 months.
Protocol Buffers (proto2) implementation in ABAP
No published releases; repository quiet for 34 months.
BDD/TDD assertion library for ABAP Unit, styled after Chai.js
Seventeen agent skills for ABAP development
ABAP report that runs Salesforce SOQL queries and exports results
No published releases; repository quiet for 91 months.
Exposes ABAP class methods as REST services with Swagger UI
No published releases; repository quiet for 47 months.
Transport release check gated by GitHub pull request approval
Not below SAP_BASIS 7.40 SP08, and not on [SAP S/4HANA Cloud Public Edition](external:sap-s4hana-cloud-public-edition) or [the SAP BTP ABAP environment](artifact:btp-abap-environment), where the classic transport check, the report and job calls and the cluster table `INDX` it rests on do not exist and the maintainer names gCTS as the answer instead. Only on a development system where every developer is trusted: each developer's GitHub token is kept in a cluster table encrypted with a key held in the same table, so anybody who can run ABAP on that system can read both, and the separation between author and reviewer holds only as far as that trust does. Not where the gate has to be unconditional — `#NOREVIEW` in a request's short text skips the check for that request, `ZTR_DISABLED` switches it off for a system, a check that cannot reach GitHub lets the release go on, and nothing checks who writes the marker.
Helper class for reading TVARVC parameters and select-options
No published releases; repository quiet for 33 months.
Application job that runs and schedules ABAP Unit tests in the cloud
ABAP API for Google Apps, with upload to Google Docs
No published releases; repository quiet for 97 months.
ABAP framework wrapping the Google Sheets API for SAP S/4HANA
No published releases; repository quiet for 81 months.
ABAP API for OAuth 2.0 authentication
No published releases; repository quiet for 97 months.
UI5 apps written as one ABAP class, rendered by a generic shell
Office add-in running an abap2UI5 app in Excel's task pane
VS Code extension to preview, activate and lint abap2UI5 apps
The embedded preview needs a system that accepts basic auth: the documentation states that pure SSO or SAML without a basic-auth fallback is not supported, and points at `external` mode, which opens the app in the normal browser with the existing SAP session. On the web only the language half runs; the preview with its proxy, traffic log and screenshot, Ctrl+F3 activation, the render gate, the workspace-wide check and the MCP servers are desktop-only. The agent app tools send nothing until `abap2ui5.agent.enableAppTools` is switched on in User settings, because an event they fire runs as the configured user and changes data on the system for real.
abap2UI5 frontend as ABAP artefacts installed with abapGit
The frontend is optional: where abap2UI5 apps are reached through the framework's own HTTP service, nothing from here is installed. In S/4 Public Cloud that endpoint needs `S_DEVELOP` authorisation, which the installation guide states makes it unfit for production, and the separate frontend app with an extra tile is what it names for business users. The `cloud_new` and `standard_new` branches need an abap2UI5 newer than 1.146.0 on the system.
abap2UI5 frontend rendering with UI5 Web Components
Not for views built from controls outside the portable profile: sap.ui.table, sap.f, sap.uxap, sap.ui.comp and z2ui5.cc custom controls render as a visible unsupported-control box and are listed in the diagnostics, and `CONTROL_BY_ID` and `BINDING_CALL` stay unsupported. Nine frontend actions the profile allows, `DOWNLOAD_B64_FILE` and `SYSTEM_LOGOUT` among them, are skipped and reported rather than run, and formatters other than the profile's `Formatter.Date*` render a placeholder.
Drives abap2UI5 app classes from ABAP Unit tests
There is no control tree: visibility and enablement are not evaluated, and `set_value( )` is not checked against the bound paths. The frontend `CONFIG` (device, UI5 version, focus, scroll) is not sent at all, so an app that branches on device or theme sees initial values. It drives `z2ui5_cl_ui5_handler` and the draft service, which the README states are not part of abap2UI5's released API in `src/02`, so a core change there can require a change here.
Drag-and-drop UI5 view editor that writes an abap2UI5 app class
The class has to be moved by hand: an abapGit pull of the exported ZIP, or a paste into ADT or SE24. The palette is held to the 121 controls of UI5 1.71, and a control inserted by its class name instead comes from whatever UI5 the canvas has loaded, with nothing checking it against 1.71 - *Checks* reports that. An app class that builds no view, or more than one, is refused.
Native iOS and Android shell for one abap2UI5 endpoint
In-browser ABAP editor beside the abap2UI5 app it builds
A `SELECT` from a business table has nothing to select from: the database in the page holds the framework's own tables, and nothing can reach outside the browser, so an app that reads a system's data cannot be tried here. Only the UI5 libraries built in are available and a control from anywhere else will not load; what the transpiler cannot compile is reported in the output panel rather than run. State lives in the tab — a reload, and a press of Run, starts over on a fresh database.
Versioned specification of the abap2UI5 roundtrip protocol
Neither suite has been run against an ABAP system: the reference backends are the framework transpiled to Node and cap2UI5 on CAP, so what a check does on a real system is open. The portable profile is a subset of 61 controls, filled from a census of 247 core apps of which 64.8 % run unchanged, so an app outside it renders placeholders in the terminal and Adaptive Cards renderers.
129 abap2UI5 sample apps, one ABAP class each
A sample that needs something the system provides is not here — the samples-stack repository holds the OData, RAP, WebSocket and launchpad demos, and samples-controls the rebuilds of the UI5 Demo Kit originals. Every class in `src/` keeps to controls and properties available since UI5 1.71 and not deprecated, apart from two clipboard samples marked `(UI5 1.119+)`, so a newer control is not demonstrated here. Numbers are handed out per repository and reused across the three, so `493` alone does not name a sample: `Z2UI5_CL_SMP_APP_493` is the Hello World here.
Eleven abap2UI5 apps, one per open-source ABAP library
Not on ABAP Cloud: most of the libraries use APIs that are not released there, and the repository has no ABAP Cloud gate yet. Not beyond a development system without authorisation checks added first — the samples carry none of their own, the abap-fm-logger sample reads the log table `ZAFL_LOG` with whatever the logged calls received and returned, and the abap_fm_json sample calls function modules, limited to a hard-coded whitelist.
Ready-made dialogs for abap2UI5 apps
The value-help and search-help popups read whichever DDIC check table the user selects without an authorisation check of their own, so the README asks for your own checks and a restriction on which tables may be browsed before they are used beyond a development system. The transport-request popup works only on-premise, and the search help does not yet run on the Cloud stack.
Upload, edit and download ABAP table content as JSON, CSV or XLSX
Not an end-user app: it reads from any table the user names and writes into tables of the Z/Y namespace, with no authorisation check of its own, so the README asks a project to add its own checks on `S_TABU_DIS`/`S_TABU_NAM` and to restrict who may run it before it is used beyond a development system. XLSX upload and download are not ready for ABAP Cloud yet, and of the upload apps only the JSON one writes the file's rows back to the database.
abap2UI5 folded into the local classes of one HTTP handler
Not where the framework code itself has to change: `input/` and the three installable branches are overwritten by the workflows on every upstream push, and a framework change is a pull request to abap2UI5. Bug reports and feature requests also go to the abap2UI5 repository rather than this one.
UI5 Demo Kit samples rebuilt as abap2UI5 apps
The 221 ports under `src/02` need a UI5 runtime newer than 1.71: they install and activate on any release, and on an older UI5 the newer control does not render. The `src/03` collection is hand-written for SAPUI5-only controls and needs a SAPUI5 bootstrap. There are no per-library branches, so pulling the whole repository is the one way in and the activation takes a few minutes.
abap2UI5 apps in front of OData, RAP, events and other technology
Not the place to learn abap2UI5 itself: every package starts from a technology the system already provides, and the framework basics and the control gallery are the other two sample repositories, abap2UI5/samples and abap2UI5/samples-controls. Three packages are out of reach on ABAP Cloud, and `05` needs the 2021 release that carries RAP business events.
ANTLR4 grammar, lexer and parser for ABAP CDS
Release and repository quiet for 36 months.
Uploads ABAP Unit code coverage to codecov.io
No published releases; repository quiet for 67 months.
Maps clipboard, Excel or text data onto a declared ABAP structure
No published releases; repository quiet for 31 months.
Checks field values against domain fixed values and check tables
No published releases; repository quiet for 54 months.
Fake data generator for ABAP
No published releases; repository quiet for 53 months.
ABAP client for Firebase's Realtime Database REST API
No published releases; repository quiet for 95 months.
ABAP objects enabling ADT updates on systems older than 7.51
Quiet No published releases; repository quiet for 92 months.
Functional boundary A system that already handles the session has nothing to gain from it. The maintainer states that importing it there causes no issue and simply sets the flag twice.
ABAP transaction generating an MVC-style project from a template
No published releases; repository quiet for 48 months.
Git client written in ABAP that runs inside the system
abapGit user exits checking commit messages against repository rules
Quiet No published releases; repository quiet for 35 months.
No license Neither the package manifest nor the repository tree declares a licence.
ABAP library for creating Graphviz graphs
No published releases; repository quiet for 72 months.
Fetch API-style HTTP polyfill for cloud and classic ABAP
Neither the package manifest nor the repository tree declares a licence.
Cloud-compatible plugin for the abapify Fetch API polyfill
No published releases; repository quiet for 26 months.
Legacy-release Fetch API implementation for outbound HTTP in ABAP
Promise and async/await implementation for ABAP
No published releases; repository quiet for 36 months.
Static analysis for ABAP source outside a system
Shows abaplint results inside abapGit
ABAP client surfacing abaplint checks in Code Inspector and ATC
OA2C_SPECIFICS implementation for Microsoft Azure OAuth 2.0 in ABAP
No published releases; repository quiet for 27 months.
Open-source rule pack for SAP Code Inspector and ATC
SAP GUI code review tied to transport release
No published releases; repository quiet for 31 months.
Framework for running ABAP work units in parallel tasks
Quiet No published releases; repository quiet for 57 months.
Functional boundary The maintainer states the current state has never been used in real-world scenarios: the demo reports in package ZAPS_DEMO and the unit tests are the only runs reported, and the release table marks SAP_BASIS 740 unclear, 754 as the release it was developed on, and 750 to 756 as expected to work.
OpenPGP implementation in ABAP, scoped to signing
Not for anything important, which is the maintainer's own instruction: the README's Warning section calls it stupid to write your own encryption or PGP library, says abapPGP will most certainly contain severe bugs, and points instead at established PGP software such as [OpenPGP](http://openpgp.org/). Signing is the only scope it states.
Class-based wrapper around STRUST certificate management
Command-line ABAP pretty printer over ADT
No published releases; repository quiet for 45 months.
ABAP MCP server over ADT with a local journal that can undo writes
A system that reports itself productive, or whose role the probe cannot prove non-productive, is write-locked with no override, so changing code in production is not something this does. The permission ladder constrains the package, object name and transport request the server itself passes on a write, and is not a sandbox around ABAP it executes: `abap_run`, `abap_test` and the opt-in `core.eval` run under the connected technical user's SAP authorisations, which is where the boundary actually sits. Data preview, dump variable contents and driving a transaction by batch input stay off in every mode, `admin` included, until each is named explicitly.
Shows a whole ABAP object as it stood at a past version
No published releases; repository quiet for 38 months.
SAP GUI transaction for one-click transports of copies
Macro DSL turning a one-line select into an ALV list
SAP GUI tool for static analysis of ABAP call flow and code metrics
VS Code extension automating ActiveControl transport forms
Backend exposing ABAP Unit runs and coverage over REST and OData
Release and repository quiet for 37 months.
RFC-callable ABAP API for SAP data extraction for ADELE
No published releases; repository quiet for 73 months.
Fiori launchpad notification for application log errors
Usage, error and response-time monitor for abap2UI5
It sees [abap2UI5](artifact:abap2ui5-abap2ui5) only: the figures come from the framework's HTTP handler, its monitor hook and its draft table, so nothing outside abap2UI5 appears in them. The usage, error and performance tabs stay empty until the handler line is in place or the user exit sets `check_monitor_active`. Recording which employee used which application, when and how fast, is subject to works council co-determination in Germany (§ 87 (1) no. 6 BetrVG); user tracking is `HASH` by default, `NAME` stores user names, and the request recorder keeps the complete request and response of every roundtrip for two days by default.
Windows build packaging Eclipse with ADT as a portable IDE
ABAP classes sending push notifications to Mobile Services
No published releases; repository quiet for 54 months.
JSON parser and serialiser for ABAP with a node tree
ABAP class wrapping SALV to set column properties in one call
No published releases; repository quiet for 79 months.
In-system search tool for CDS views
No published releases; repository quiet for 29 months.
MCP server over the ADT REST API for ABAP objects
Twenty-two agent skills shipped with arc-1
Every skill that touches ABAP needs [arc-1](artifact:arc-mcp-arc-1) itself connected to a real system; nothing else is universal. `modernize-ui5-app` and `convert-ui5-to-fiori-elements` specifically need [the UI5 MCP server](artifact:ui5-mcp-server) for TypeScript conversion guidance and the linter, `convert-ui5-to-fiori-elements` also needs [the Fiori MCP server](artifact:sap-ux-fiori-mcp-server) for its LROP scaffold, and `modernize-ui5-app` needs a browser MCP (Claude in Chrome or Claude's own Preview) for its final render-verification step, since an HTTP 200 alone does not catch a blank page. A skill file alone, without the servers a given skill needs, has nothing to act on.
arc-1 extension for reading and maintaining BOPF enhancements
Classic BOPF only: business objects of the ABAP Programming Model for SAP Fiori are not handled, and on [the BTP ABAP environment](artifact:btp-abap-environment) or S/4HANA Public Cloud classic BOPF enhancements do not exist. It is version 0.1.0, verified on S/4HANA 2025 (SAP_BASIS 816) on-premise only, and [arc-1](artifact:arc-mcp-arc-1) still marks the plugin API it is built on as experimental. ARC-1 loads no extensions on its multi-target routes and offers none of these tools in its `hyperfocused` tool mode.
Hub on SAP BTP putting several arc-1 instances behind one login
Archived The declared repository is archived.
Functional boundary With one SAP system the README says to point the client at that arc-1 directly. Version 1 exchanges tokens within a single subaccount, so backends spread across subaccounts are out; it keeps its session map in memory, so more than one instance needs sticky sessions or a shared store. It routes deterministically and runs no model, which is a different thing from an assistant that reasons across systems. The `/all` endpoint drops the per-connection isolation, and the maintainer's answer to that is a PROD backend set read-only at the SAP end rather than a tool surface that hides the writes.
Fluent assertion helper for ABAP Unit tests
ABAP OData service for attachments and comments via GOS
No published releases; repository quiet for 66 months.
Template for ABAP applications with an HTML UI
The declared repository is archived.
Task tracker on a BOPF-backed CDS view with a Fiori list report
Practice repository for the unmanaged RAP scenario
Practice repository for managed RAP with unmanaged save
Demo programs for the classic CL_GUI_ALV_GRID control
Starter repository for an abap2UI5 app with CI and agent setup
Sample arc-1 extension in TypeScript with ten custom tools
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary It consumes the `@experimental` public API, which the README says may break in any release. The RFC tool dials as one shared technical user with its own credentials, so SAP's log records that user and not the person behind the agent.
ATC check classes accompanying DSAG's ATC best-practice guide
