Everything in the atlas
Type
Domain: 2
Origin
Signals
More
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.
Result pattern for ABAP instead of exceptions for expected failures
ABAP report that runs Salesforce SOQL queries and exports results
No published releases; repository quiet for 91 months.
ABAP API for Google Apps, with upload to Google Docs
No published releases; repository quiet for 97 months.
ABAP client for Firebase's Realtime Database REST API
No published releases; repository quiet for 95 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
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.
Swagger UI for SAP NetWeaver Gateway services
No published releases; repository quiet for 49 months.
Exposes ABAP class methods as REST services with Swagger UI
No published releases; repository quiet for 47 months.
Configurable CSV reader and writer for ABAP
JSON encoder and decoder for ABAP, modelled on Go's encoding/json
No published releases; repository quiet for 49 months.
Open-source Z* version of /UI2/CL_JSON for ABAP to JSON
JSON parser and serialiser for ABAP with a node tree
SAP GUI browser for tables, views, CDS views and joins
A system below ABAP 7.50: some of the classes it uses are only available from 7.50, and the maintainer states that downward compatibility to 7.40 in a single branch is currently not possible without resorting to dynamic programming.
Read-only SAP GUI report listing where HCM object data is stored
Thirty classic transactions rebuilt as abap2UI5 apps
Not on ABAP Cloud: the system tables and the classic Workbench APIs the screens use are not released for the ABAP Cloud language version, and there is no 7.02 version below the 7.50 floor either. Not where the full original function is needed, since only the listed transactions exist and about 300 buttons and fields are shown disabled. The authorization checks are rebuilt rather than the originals, which is why the README asks that the screens be tried with a restricted user on a sandbox before the ICF service is opened to more people.
Table content browser in abap2UI5, for ABAP Cloud and on premise
Not as it stands on a system past development: it reads the contents of any table the user names without an authorisation check of its own, so access is bounded only by whatever restrictions exist on the underlying handler or service. The README asks for your own checks first, naming `AUTHORITY-CHECK` on `S_TABU_DIS`/`S_TABU_NAM`, and for a restriction on who may run the app. There is no 7.02 downport either, because the selection-screen dependency has no `702` branch.
Multi-window SAP GUI explorer for tables, views and CDS SQL views
Browser-based SQL console built on abap2UI5
It runs whatever SQL a user types without an authorisation check of its own, and the native path additionally uses ADBC, which bypasses ABAP authorisations and client separation; the README asks anyone running it beyond a development system to add authorisation checks and restrict who may start the app. The native console needs Standard ABAP, so on ABAP Cloud only the Open SQL console is available.
Open SQL editor for ABAP with ALV output
UI5 app for OData test requests and ABAP Push Channels
Software-engineering metrics for an ABAP class or package
No published releases; repository quiet for 43 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.
SAP GUI code review tied to transport release
No published releases; repository quiet for 31 months.
Shows a whole ABAP object as it stood at a past version
No published releases; repository quiet for 38 months.
ABAP debugger extension drawing objects as a Graphviz graph
No published releases; repository quiet for 97 months.
Debugger script exporting an object hierarchy as Graphviz
No published releases; repository quiet for 67 months.
SAP GUI debugger script recording steps so execution can run backwards
ADT backend for the ABAP Call Hierarchy Eclipse plugin
ADT backend for the ABAP Tags Eclipse plugin
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.
Collection of ABAP Development Tools IDE Actions
Thirty classic transactions rebuilt as abap2UI5 apps
Not on ABAP Cloud: the system tables and the classic Workbench APIs the screens use are not released for the ABAP Cloud language version, and there is no 7.02 version below the 7.50 floor either. Not where the full original function is needed, since only the listed transactions exist and about 300 buttons and fields are shown disabled. The authorization checks are rebuilt rather than the originals, which is why the README asks that the screens be tried with a restricted user on a sandbox before the ICF service is opened to more people.
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 report setting up a new ABAP Developer Edition or trial system
Quiet No published releases; repository quiet for 24 months.
Functional boundary Not against a system holding local repository changes that have not been pushed: Pull Repos overwrites every repository named in zdevsysinit_params, which is why the maintainer leaves that box unticked and calls it a danger zone. The maintainer calls the whole report work in progress, to be used at own risk.
ABAP program drawing UML class diagrams through PlantUML
No published releases; repository quiet for 54 months.
In-system ABAP source search by string or regular expression
Finder for ABAP Dictionary objects
No published releases; repository quiet for 58 months.
No published releases; repository quiet for 66 months.
Thirty classic transactions rebuilt as abap2UI5 apps
Not on ABAP Cloud: the system tables and the classic Workbench APIs the screens use are not released for the ABAP Cloud language version, and there is no 7.02 version below the 7.50 floor either. Not where the full original function is needed, since only the listed transactions exist and about 300 buttons and fields are shown disabled. The authorization checks are rebuilt rather than the originals, which is why the README asks that the screens be tried with a restricted user on a sandbox before the ICF service is opened to more people.
Report searching ABAP source in methods, enhancements, DTPs and more
No published releases; repository quiet for 58 months.
Search over ABAP program variants for a value or pattern
No published releases; repository quiet for 62 months.
Fake data generator for ABAP
No published releases; repository quiet for 53 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.
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.
Git server implemented in ABAP for abapGit clients
Helper programs around abapGit
Where abapGit itself is not installed in the system, since every tool here acts on its repositories.
Server-side component of TRM for importing and exporting transports
Shows abaplint results inside abapGit
Open-source rule pack for SAP Code Inspector and ATC
SAP GUI tool for static analysis of ABAP call flow and code metrics
ATC and Code Inspector checks for Clean ABAP
This is the legacy edition, for on-premise systems from SAP_BASIS 7.40. On ABAP Cloud, [the Cloud Edition](artifact:sap-code-pal-for-abap-cloud) is the one that runs.
Uploads and downloads Code Inspector check variants as XML
Replays stored database snapshots in ABAP unit tests
No published releases; repository quiet for 28 months.
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.
Uploads ABAP Unit code coverage to codecov.io
No published releases; repository quiet for 67 months.
Backend exposing ABAP Unit runs and coverage over REST and OData
Release and repository quiet for 37 months.
BDD framework turning Given/When/Then into ABAP Unit steps
No published releases; repository quiet for 40 months.
Loader of Excel-prepared ABAP unit test data, with stub generation
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.
Snapshot testing library for ABAP, from debugger or unit test
Quiet No published releases; repository quiet for 28 months.
Functional boundary Values the test data container cannot hold: references of any kind, complex structures, and tables whose line type is a complex structure or another table. Structures must be defined in the ABAP Dictionary, so one declared locally cannot be stored at all.
No published releases; repository quiet for 59 months.