Everything in the atlas
Type
Domain
Origin
Signals: Last 12 months
More: 2
Group by: Type
Git client written in ABAP that runs inside the system
Transpiles ABAP to JavaScript to run on Node.js
Compiler from a CDS service to SEGW model and data provider classes
The generated files are copied or deployed into the ABAP system by hand, the fourth step of its own usage list, so nothing keeps an activated service in step with the model it was generated from. Its peer dependency is `@sap/cds` ^9.8, so it does not install into a project on an earlier CAP release.
ESLint rules flagging deprecated CAP configuration
UI5 middleware recording OData traffic as mock server datasets
It records what the app actually asked for, so an entity no recorded journey touched is not in the dataset and replay will not answer for it. Its own README asks for `fiori-tools-appreload` to be disabled while recording, because a reload loop is what happens otherwise.
UI5 Tooling task writing the service name into the importer manifest
UI5 build task warning when the app's UI5 version reaches EOCP
The version list comes from ui5.sap.com, so a build that cannot reach it has nothing to match the project's version against. It checks the version written in `ui5.yaml`; a framework version a deployed app loads from elsewhere is outside what it sees.
CAP Java plugin for soft delete with a softdelete aspect
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The Maven coordinate its README gives, io.github.miyasuta:cds-feature-softdelete:1.0.0, does not resolve on Maven Central as of 2026-09-07 — you build and install it from source.
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
Endpoint discovery for CAP services deployed to Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Static end-to-end tracer of one CAP operation across repositories
Static analysis for ABAP source outside a system
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
Attaches a debugger to a CAP app running on Cloud Foundry
Terminal UI running Bruno collections against a CAP service
Ten short CAP Java references, one document per topic
Interactive generator for CAP event handler files
Interactive project installer for CAP Node.js
Fills db/data with relationally consistent CSV from a .cds schema
Yeoman generator for Application Frontend config in UI5 libraries
It targets the Application Frontend service only — not the HTML5 application repository — fixes authentication to IAS, and always creates new service instances, so reusing existing ones means editing the generated `mta.yaml` afterwards. Version 0.1.0 is the only release.
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
Eclipse plugin bringing Claude into ABAP Development Tools
Eclipse plugin linking ABAP transports to SAP Cloud ALM features
An Eclipse installation older than the 2026-03 release, or a Java below 21, cannot take it: both are listed prerequisites, and 2026-03 is named as the oldest release the current ADT installs on. The tenant, region, client ID and client secret are entered per installation in Eclipse preferences, so each developer configures the Cloud ALM connection in their own IDE.
Parser for ABAP CDS DDL source with a typed AST
Writer module for changing a CAP project's configuration from code
There is nothing to run: it is published for a generator or a script to call, not for a developer to invoke in a project, and it declares Node.js 22 or later.
UI5 apps written as one ABAP class, rendered by a generic shell
Bridge from CAP Java to SAP AI Core, with Fiori field recommendations
TextMate grammar for the CDS language
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
CAP Java plugin for SAP Integration Suite, advanced event mesh
CAP Java attachments with database storage and an Object Store module
For deployed environments, the [README](https://raw.githubusercontent.com/cap-java/cds-feature-attachments/302f61c8bb76a0f54f43482ad91d89bf7dc5540f/README.md) excludes the cds-feature-attachments-fs file-system target, which is intended only for local development and testing.
CAP Java plugin sending audit log events to SAP Audit Log service
Connects a running CAP Java app to CAP console for monitoring
Connects CAP Java messaging to SAP Cloud Application Event Hub
Triggers n8n workflows from CAP Java through the outbox
Business notifications from CAP Java via SAP Alert Notification
Generates Open Resource Discovery documents from a CAP Java model
CAP Java plugin for attachments in SAP Document Management
If document versions are required, the [documented restrictions](https://raw.githubusercontent.com/cap-java/sdm/673769f24ef66fd97daa6a6be41262d45065d3fe/README.md) exclude versioned repositories.
SAP's specification for serialising ABAP objects to files
Open, versioned style guide for ABAP
Starter repository for an abap2UI5 app with CI and agent setup
Java implementation of the capire/bookstore composite app
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
CAP Java draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
Spring Boot apps routing AWS SDK traffic over SAP Private Link
Hands-on building an AI agent with the SAP Cloud SDK for AI
CAP review skill for coding agents with gates and prohibitions
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary There is no licence, so there is no grant to use or redistribute it. Everything else is secondary to that. Note too that its 'verified' claim means the skill text was checked against itself by an evaluation suite — not that the advice was run against a CAP version.
abap2UI5 transpiled to JavaScript and run in a browser tab
It is not the framework and takes no framework fixes: those belong upstream in abap2UI5, and nothing under `src/`, `downport/`, `output/` and `build/` here is a source file. The build is frozen on pinned commits with no scheduled rebuild, so it does not show what abap2UI5 main does today, samples in subfolders of the samples repository are excluded because they require a real SAP system, and a known upstream transpiler issue leaves `check_on_init( )` always false, so backend-built view XML may not be returned.