Everything in the atlas
Type
Domain: Operations & Runtime
Origin
Signals
More: 3
Group by: Capability
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.
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
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.
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
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
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.
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.