Everything in ABAP
Type
Domain: Protocols & APIs
Origin: Independent
Signals
More: MIT
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.
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 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.
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.
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.
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 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 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.
Template pairing a FastAPI service with ABAP reports that call it