Everything in the atlas
Type
Domain: 2
Origin
Signals
Content
More
Group by: None
Business-level metrics from CDS annotations via @cap-js/telemetry
Transactional processing of asynchronous and periodic CAP events
If you need sub-second fan-out to external consumers this is the wrong layer — reach for [Event Mesh](artifact:btp-event-mesh) or Kafka. Without [Redis](external:redis), periodic processing still works but instant dispatch degrades to polling.
Live-updatable feature toggles for CAP, backed by Redis
CLI for operating tenants of multitenant CAP applications
SDK for SAP Advanced Financial Closing scheduling providers on CDS
CAP integration with SAP Integration Suite advanced event mesh
Exports AsyncAPI documents for a CAP service's events
CAP integration with the SAP Audit Log service
Generates Helm charts for the CAP Operator on Kubernetes
Consumes events from SAP Cloud Application Event Hub in CAP
Business notifications from CAP to SAP Build WorkZone
Prints documents held in CAP entities through SAP Print service
OpenTelemetry instrumentation for CAP services
Renamed copy of @cap-js/notifications under another scope
Release and repository quiet for 24 months.
Annotation-driven mail on CAP entity lifecycle events
Node below 22, or [@sap/cds](artifact:sap-cds) below 9: the package declares the first in engines and the second as a peer dependency. Any mail path other than Microsoft Graph, until a provider is written for it: graph is the only kind that sends, and basic, the kind configured by default, is the base class such a provider extends.
Copy of @cap-js/notifications published under another scope
Reach for the original unless you know why you are not. This is a republished copy rather than a fork with a direction of its own: the README points at cap-js/notifications for the details, and nothing here says what was changed or why.
CAP plugin watching Cardano addresses and emitting events
Framework core: module loader, MVC runtime, binding, routing, theming
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.
CAP plugin wrapping the SAP Forms service by Adobe on BTP
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
VS Code Multi-Target Application tools
Destination lookup and connectivity proxy for the Cloud SDK
HTTP client carrying a destination's credentials
Shared machinery under the Cloud SDK's OData and OpenAPI clients
Generated OpenAPI clients for the Cloud SDK
Timeouts, retries and circuit breaking around remote calls
General utilities shared across the Cloud SDK packages
Library for sending usage telemetry data
MTA generation and Cloud Foundry deploy for VS Code workspaces
A library a VS Code extension calls, not something installed and run on its own; there is no documented standalone CLI. No public repository either, so what it does is read from its own README rather than checked against source.
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Command line client and development toolkit for CAP
Multitenancy, tenant provisioning and extensibility for CAP
WebAssembly sandbox for tenant-specific extension code in CAP
Calls to ABAP function modules over RFC from a CAP service
SAP Passport handling for Node.js components
CLI to build, deploy, migrate and validate MDK projects
Specific to MDK metadata projects — nothing here builds or deploys a CAP service or a plain Fiori app. Closed-source, under SAP's own developer licence rather than a public repository.
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
Log fetcher and parser for one Cloud Foundry app
Read-only query tool for metrics in SAP Cloud Logging
Read-only query tool for OpenTelemetry spans in SAP Cloud Logging
Merged log tail of every started app in a Cloud Foundry space
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.
VS Code extension editing ABAP systems over ADT as a filesystem
Converts classic Open SQL SELECTs to released CDS entities
In beta by its own page's account, where conversion bugs may occur and not all functions and variants are supported yet. The shapes named as not yet supported are sub selects, FOR ALL ENTRIES, functions such as count and sum, and the IN operator with a value list, so a statement built on one of those is outside what the converter sets out to do.
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.
Object-oriented wrapper around the Business Application Log
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.
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.
Chainable logger for ABAP Cloud around CL_BALI_LOG
Framework for runtime parameters, ranges and value mappings in ABAP
Feature toggle for ABAP read via is_active on view ZFEAT_TOGGLE
Fluentd client in ABAP for sending log lines to a collector
No published releases; repository quiet for 96 months.
Logger storing RFC function module call parameters as JSON
Generic customizing table and reader for ad hoc ABAP parameters
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
Exposes ABAP stack metrics to a monitoring tool
The declared repository is archived.
OTLP serialisation of traces, metrics and logs in ABAP
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.
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.
Prometheus client for ABAP, installed with abapGit
No published releases; repository quiet for 39 months.
Injectable wrapper for SY fields and date functions in ABAP Cloud
Helper class for reading TVARVC parameters and select-options
No published releases; repository quiet for 33 months.
Library that reads and generates Excel spreadsheets from ABAP
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.
SAP GUI transaction for one-click transports of copies
VS Code extension automating ActiveControl transport forms
RFC-callable ABAP API for SAP data extraction for ADELE
No published releases; repository quiet for 73 months.
Fiori launchpad notification for application log errors
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.
Injects the Dynatrace agent into Java applications on SAP BTP
ABAP classes sending push notifications to Mobile Services
No published releases; repository quiet for 54 months.
Business data graph queried with OData V4 or GraphQL
Scales Cloud Foundry app instances by policy rules and schedules
ABAP application options as a structure with a generated editor
UI5 app and CAP service copying role collections between subaccounts
Quiet No published releases; repository quiet for 54 months.
No license Neither the package manifest nor the repository tree declares a licence.
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.
Yeoman generator for Cloud Connector mappings and BTP destinations
Containerised script setting up an SAP BTP account from JSON config
The declared repository is archived.
RAP sales order using number ranges, change documents and Adobe forms
CodeJam on LLM-backed integration flows and MCP via API Management
CAP services and a UI for trying role restrictions with mock users
Neither the package manifest nor the repository tree declares a licence.
MTA projects sharing a role collection across role templates
Neither the package manifest nor the repository tree declares a licence.
CAP project reaching S/4 via SAP BTP Private Link Service for Azure
Neither the package manifest nor the repository tree declares a licence.
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
Terraform samples for the SAP BTP Administrator's Guide account model
Instructions for deploying Edge Integration Cell onto Microsoft Azure
Getting-started guide for a Hello-World function on SAP BTP, Kyma
Guide and samples for moving Java apps from Neo to Cloud Foundry
@sap/approuter patterns in front of SAP Private Link Service
Integration flows pulling SAP Ariba spend data into SAP Datasphere
Code samples for the Getting Started with Terraform on SAP BTP course
Samples for the Terraform Provider for SAP BTP