Everything in the atlas

A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.

A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.

It presumes the estate it governs: intelligent content is installed and viewed rather than authored, and the catalog is only as useful as what has been published into it. The Databricks path is a direction data goes, which is a decision about where analytics happens and not only about a tool.

A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.

Nothing to choose here and nothing to install: it is what an ABAP Cloud system gives you. It shares a name and a lineage with CAP's CDS but is a different language in a different runtime, and a model does not move between them.

Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.

For provisioning a managed database on BTP, see [SAP HANA Cloud](artifact:btp-hana-cloud). Features differ between HANA versions; an on-premise deployment and a cloud instance are not interchangeable without compatibility checks.

Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.

A tenant with its own model layer, its own transport and its own user administration — content moves between tenants through export and import jobs rather than through your pipeline, and planning brings a calendar and a workflow that a reporting-only use never touches.

A tenant with spaces and a role model, not a database you point an application at — privileges are granted per space, and what somebody can model depends on the scoped role they hold. Federation is the default answer to moving data, and where it is not, a load has to be scheduled and watched.

There is nothing to install and nothing to deploy, and equally nothing to run headless: in VS Code it exists only while ADT for VS Code is running with a logged-on ABAP project, so it is a developer's local surface rather than anything a pipeline or a hosted agent can reach. No public repository, so what it exposes is what the documentation says it exposes.

Not reachable Not reachable since 2026-10-20.

Functional boundary `run_class` executes code in your system — that is the point and it is also the risk.

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.

It runs on macOS only. Hammer Core Services, the part installed into the SAP system, needs that system on ABAP Platform 2023 or newer with SAP_BASIS 758 or newer, and installing it needs a user who can create development objects and run background jobs in that system.

Its maker offers it commercially.

Its maker offers it commercially.

Its maker offers it commercially.

It acts on a real account. Authorisation is the caller's own — single sign-on through the SAP Default Identity Provider, across the global accounts that identity reaches — so what it can change is what you can change, and an agent invoking it is doing administration rather than proposing it. No public source, so what it exposes is what the documentation says it exposes.

This is enterprise-architecture data, not a development surface — it answers what your landscape contains, never what your code does, and nothing in it belongs in a build. Entered here because it is a first-party SAP MCP endpoint and the catalogue that tracks this corner lists it; the atlas maps SAP development, so treat it as adjacent rather than as tooling for a project.

Its maker offers it commercially.

Its maker offers it commercially.