Everything in the atlas
Type
Domain: 2
Origin
Signals
More: 3
Group by: Capability
Maven bill of materials pinning CAP Java module versions
Ten short CAP Java references, one document per topic
Generates Open Resource Discovery documents from a CAP Java model
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
Maven bill of materials pinning CAP Java module versions
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.
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
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.
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.
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions
Local MCP server on support status from an SAP PAM export
Maven bill of materials pinning CAP Java module versions
Ten short CAP Java references, one document per topic
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Maven bill of materials pinning CAP Java module versions
Maven bill of materials pinning CAP Java module versions