Everything in ABAP
Type
Domain: Integration & Messaging
Origin
Signals
Content
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.
RAP sample with bgPF, business events and side effects
Transactional outbox pattern in ABAP Cloud with bgPF
Library that reads and generates Excel spreadsheets from ABAP
Single-file Handlebars templating for ABAP 7.40 SP02 and up
Standalone PDF generator written in ABAP
Adobe Document Services on BTP for print and interactive PDFs
Submits an ABAP report to the spool and converts the output to PDF
ABAP template engine for Excel, Word, HTML and PDF
ABAP class filling a tagged Word .docx template with data
No published releases; repository quiet for 33 months.
Standalone ABAP class drawing PDFs without Adobe Document Server
RAP sales order using number ranges, change documents and Adobe forms
Projects integrating SAP Forms Service by Adobe with ABAP Environment
ABAP connector to Kafka through the Confluent Kafka REST Proxy
No published releases; repository quiet for 57 months.
ICF handler receiving Amazon SNS notifications in an ABAP system
No published releases; repository quiet for 64 months.
MQTT 3.1.1 client implemented in ABAP
No published releases; repository quiet for 68 months.
MQTT publish/subscribe in ABAP with an external broker bridge
Quiet No published releases; repository quiet for 75 months.
Functional boundary The maintainer calls the project beta, states there are no experiences with productive usage, and leaves productive use at your own risk. Two further conditions are stated: the implementation used a NetWeaver ABAP stack 7.50 and a 7.40 was not tested, and a system user has to be maintained for the websocket services, because the external websocket tools do not support user-based authorization.
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.
Fiori launchpad notification for application log errors
ABAP classes sending push notifications to Mobile Services
No published releases; repository quiet for 54 months.
ABAP helper class building HTML emails from templates
Quiet No published releases; repository quiet for 52 months.
Functional boundary On an SAP S/4HANA system the maintainer points elsewhere: the README calls this solution helpful for non-S/4 systems and names SAP's own e-mail templates with CDS views as what S/4 systems have instead.
RSS feed publisher for content from an SAP NetWeaver ABAP system
No published releases; repository quiet for 93 months.
JSON adapter exposing ABAP function modules over HTTP
Input arrives only as JSON, or as plain XML if the ABAP built-in transformation is switched on, whatever the output format is set to. Cross-site calls are limited to JSONP: the maintainer lists CORS support as planned.
RFC-callable ABAP API for SAP data extraction for ADELE
No published releases; repository quiet for 73 months.
SAP's on-premises agent linking SAP BTP to customer-network systems
DuckDB extension reading SAP ERP tables, CDS views and BW queries
DataZoo GmbH calls the extension experimental and states that minimal testing and benchmarking were done. The Business Source License 1.1 it carries restricts offering the software to third parties on a hosted or embedded basis, so an embedding product needs a commercial licence. Telemetry is on by default and is switched off per session with `SET erpl_telemetry_enabled = false` or for the machine with `DATAZOO_DISABLE_TELEMETRY=1`.
RFC client for Node.js and TypeScript without the NW RFC SDK
BUSL-1.1 rather than node-rfc's Apache-2.0, so a product you distribute has to be read against the licence and its Additional Use Grant first, and the source is closed: the GitHub repository is the issue tracker and the documentation, nothing else. `RfcServerOptions.bgRfcHandlers` raises instead of accepting handlers, so a server receiving inbound bgRFC units is outside what this does. An ABAP `MESSAGE`-raised failure still arrives with its T100 template rather than the rendered sentence, and the dump name is not reported as `key` for that case.
Forwards abap2UI5 roundtrips to another system over RFC
For an app that calls `client->set_session_stateful( )`, which needs the ICF session of the system it runs on; apps keeping their state in the draft table, the abap2UI5 default, work unchanged. For an app that reads a request header through the user exit on the source system, because the consumer forwards method, body, path, query string and status, not headers.
No published releases; repository quiet for 63 months.