Everything in the atlas
Type
Domain: 2
Origin
Signals
More: 3
Group by: Capability
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.
Captures CAP service errors, deduplicates them and mails alerts
Alerting by mail is not telemetry — if you need traces and metrics correlated across handlers, that is a different layer. It also publishes no repository, so the package is the only thing to read.
ABAP class implementing the Either pattern
No published releases; repository quiet for 25 months.
Result pattern for ABAP instead of exceptions for expected failures
Raises an ABAP exception from a text or the last system message
Release and repository quiet for 26 months.
ABAP classes for calling Azure services from SAP processes
ABAP report that runs Salesforce SOQL queries and exports results
No published releases; repository quiet for 91 months.
ABAP client for Firebase's Realtime Database REST API
No published releases; repository quiet for 95 months.
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
Web service client and connector layer for calling out of ABAP
Quiet No published releases; repository quiet for 28 months.
Functional boundary The maintainer records SSL as a known issue: an SAP Basis problem in older systems that depends on the remote certificate, so a system that cannot carry the remote certificate chain will not complete the call. It is published as free to use at your own risk, with no support statement behind it.
HTTP client for classic on-premise ABAP and ABAP Cloud
No published releases; repository quiet for 32 months.
Puts a number from an abap2UI5 app on a Fiori launchpad tile
There is nothing here for ABAP for Cloud: the requirements name Standard ABAP releases only, and a CDS/SADL based OData service for `ABAP for Cloud` compatibility stands under Limitations & Todo.
ABAP framework for OData services with one class per entity
OData and Gateway shims serving SEGW-style services on Node.js
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
ABAP code and slides from a talk on building SAP Gateway services
Swagger UI for SAP NetWeaver Gateway services
No published releases; repository quiet for 49 months.
Generates ABAP client classes and server stubs from OpenAPI
Exposes ABAP class methods as REST services with Swagger UI
No published releases; repository quiet for 47 months.
Swagger UI for a CAP service's OpenAPI definition
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.
Protocol Buffers (proto2) implementation in ABAP
JSON parser and serialiser for ABAP with a node tree
Parser of TAB-delimited text into ABAP internal tables and back
Regex RuleSets that read barcode strings into named fields
The project states that until v1.0.0 is reached, breaking changes may occur without prior notice. Rule items do not chain: every rule operates on the original input string, so a format whose second step needs the result of the first needs a custom logic class. A REPLACE rule whose replacement produces the exact same string as the input is reported as `no match`, which the documentation records as a known limitation.
ABAP library generating and parsing JSON strings
No published releases; repository quiet for 90 months.
RFC 4180 CSV parser and generator for ABAP
MCP server inside a CAP application with model and query tools
MCP server answering plain-English questions against a CDS schema
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.
MCP server SDK written in ABAP
Server side only, and deliberately: the author states there is no realistic way to support the SSE streaming a client needs, so there are no notifications, no `listChanged`, no `subscribe` and no logging. It is also frozen — protocol versions up to 2025-11-25 and no further, with everything after that in a separate V2 SDK, so starting here today is starting on a closed branch.
Stateless ABAP MCP server SDK for the 2026-07-28 protocol draft
Stateless by design: with no `Mcp-Session-Id` and no SSE, notifications of any kind, `resources/subscribe` and stream-close cancellation are excluded, which the author states are protocol-level impossibilities on stateless ICF rather than gaps to be filled later within this design. ABAP Cloud is not supported and not planned, the stated reason being SAP pushing its own MCP strategy and features in BTP; the first iteration targets 7.5x classic, with 7.02 to 7.4x served from a separate generated downport repository. No authorization object and no default auth check are delivered, so a user who may call the ICF node may call every `AREA`/`SERVER` registered under it until `check_authorization` is redefined.
MCP server for SAP BTP and Cloud Foundry acting as the logged-in user
MCP server publishing SAP functions as tools from config tables
Not reachable Not reachable since 2026-10-20.
Functional boundary What it exposes is whatever somebody put in the configuration table, which moves the governance question inside the SAP system and out of the server — an advantage if that table is controlled and a hazard if it is not. The web management interface is a second surface to secure alongside the MCP one.
CAP plugin letting the REST adapter accept XML payloads
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.
Injectable wrapper for SY fields and date functions in ABAP Cloud
Reports Clean Core ATC results per system as Level A to D KPIs
Polyfill for CL_ABAP_CODEPAGE under Clean Core
AWS agents for ABAP, PI/PO and BW modernisation work
There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.
MCP server answering whether SAP objects are released for ABAP Cloud
It answers about the object catalogue, not about your code: nothing here reads your system, so it will tell you a table is not released and not that you used it. That check is ATC's, and this is what makes ATC's answer actionable.
BTP Core Services as MCP tools with in-chat dashboards
It administers a real account through Core Services, so what it can change is what the caller can change. And the UI half depends on hosts that render mcp-ui or MCP Apps resources; elsewhere those five tools return markup nobody displays.
VS Code extension editing ABAP systems over ADT as a filesystem
CLI that pulls and pushes ABAP packages as local files over ADT
A Python 3.10+ CLI, installed with pipx rather than through any SAP-provided package manager. Its own README lists what it does not do yet: where-used, syntax check and unit test runs — for those it says to reach for [ADT/Eclipse](external:eclipse) or an MCP server. First release, v0.1.0, and no standalone LICENSE file in the repository — the MIT grant is in the README and in pyproject.toml's project metadata rather than its own file.
SAP GUI transaction for one-click transports of copies
VS Code extension automating ActiveControl transport forms
Uploads, downloads and imports ABAP transport requests as files
Adds a program's dependent objects to a transport request
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Report creating transports of copies without a new version
No published releases; repository quiet for 42 months.
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.
Framework for runtime parameters, ranges and value mappings in ABAP
Helper class for reading TVARVC parameters and select-options
No published releases; repository quiet for 33 months.
Theme, CSS and CSP settings of abap2UI5 pages kept in tables
`APP_TITLE` is not applied by the exit: the `title` field was removed from `z2ui5_if_ui5_exit=>ty_s_http_config` in abap2UI5 1.145.0, so an app that wants it as its browser tab title sets it while it runs. The live theme preview runs the frontend action `THEMING` / `setTheme` and needs UI5 1.118 or later; on an older release a saved theme applies with the next page load. The code is written for ABAP 7.50 and the README states there is no downported 7.02 version, no 702 branch and no workflow that builds one.
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
MTA deploying CAP, HDI container and a Fiori elements app
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.
Report listing user-exits, BAdIs and enhancement spots of a program
Feature toggle for ABAP read via is_active on view ZFEAT_TOGGLE
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
Log fetcher and parser for one Cloud Foundry app
Merged log tail of every started app in a Cloud Foundry space
Object-oriented wrapper around the Business Application Log
Chainable logger for ABAP Cloud around CL_BALI_LOG
Fluentd client in ABAP for sending log lines to a collector
No published releases; repository quiet for 96 months.
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.
Logging library for ABAP over the Application Log
Message logger for ABAP Cloud that saves to the Application Log
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.
Application logging for ABAP transpiled to JavaScript on Node.js
UI5 library collecting an app's JavaScript errors
Release and repository quiet for 43 months.
Release and repository quiet for 37 months.
Promise and async/await implementation for ABAP
No published releases; repository quiet for 36 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.
Coroutine framework for ABAP with awaitable results
No published releases; repository quiet for 26 months.
Parallel task library for ABAP over the SPTA framework
Threading library for ABAP modelled on Java's Thread and Runnable
No published releases; repository quiet for 37 months.
AWS agents for ABAP, PI/PO and BW modernisation work
There is nothing to clone here: "Access is provided through a registration page. Once registered, you will receive access to the GitHub repository containing the agents, deployment guides, and documentation", and that repository answers 404 to anyone who has not registered, so neither the agent code nor the deployment guides can be read before the form is filled in. AWS states the agents are published as an unsupported solution, with customers responsible for testing and securing the code before deploying in production, and that they are intended for non-production SAP environments rather than production systems. The documentation link in the README is still a placeholder.
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
Exposes ABAP stack metrics to a monitoring tool
The declared repository is archived.
OTLP serialisation of traces, metrics and logs in ABAP
Prometheus client for ABAP, installed with abapGit
No published releases; repository quiet for 39 months.
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.
Policy enforcement and field masking for MCP-enabled CAP apps
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
CAP plugin joining external entities with internal tables at query
The declared repository is on SAP's internal GitHub (github.tools.sap) and is not publicly reachable, so npm is the only place to read anything about it.
Template pairing a FastAPI service with ABAP reports that call it
Release and repository quiet for 36 months.