# Reported issues for mcp-abap-adt

Pod holds 19 of 22 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [mcp-abap-adt](/mcp/mcp-abap-adt).

## Most discussed

### Installation through 'npx -y @mcp-abap-adt/core' fails if yaml is not yet installed

Hi @fr0ster,
Installation through 'npx -y @mcp-abap-adt/core' fails if yaml is not yet installed

```
PS C:\Users\MarioAndreschak> npx -y @mcp-abap-adt/core
node:internal/modules/cjs/loader:1503
  throw err;
  ^

Error: Cannot find module 'yaml'
Require stack:
- C:\Users\MarioAndreschak\AppData\Local\npm-cache\_npx\85b7f0d15e9f33e6\node_modules\@mcp-abap-adt\core\dist\lib\config\yamlConfig.js
- C:\Users\MarioAndreschak\AppData\Local\npm-cache\_npx\85b7f0d15e9f33e6\node_modules\@mcp-abap-adt\core

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/143) · 2026-07-03 · closed · outside contributor · 2 comments

### Installing through MCP Registry fails (outdated version reference 6.3.0)

Hey @fr0ster ,

I tried to install your server through MCP Registry https://registry.modelcontextprotocol.io/?q=mcp-abap-adt

It seems to refer to an older version

<img width="406" height="513" alt="Image" src="https://github.com/user-attachments/assets/92c8487b-eeec-4cc7-917a-3321214efacb" />

Installing it through the Registry in FLUJO (or executing the npx command in PowerShell) results in the following error:
`npm error could not determine executable to run`

```
Testing server connection

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/142) · 2026-07-03 · closed · outside contributor · 6 comments

### Writing ABAP Program into SAP

While writing the program into SAP the tool creates a one long string with the ABAP solution. This takes along time.

However the code already created as a file in the repository. Can the file be used to immidiately push into the system?

For me it worked with:
{
  "objectUrl": "/sap/bc/adt/programs/programs/PROGRAM",
  "sourcePath": "c:/.../PROGRAM.abap",
  "activateAfterWrite": true
}

This would reduce the wait time significantly.

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/29) · 2026-04-01 · closed · external user · 2 comments

### MCP error -32603: Error: SAP Error: Resource Z_TEST_REPORT is not locked

Hi Oleksii,

First of all I want to thank you for your meticulous work!
The project is really great and looks quite professional in this niche area.

I was able to connect to on-prem system and read the code, but when I try to upload the program from the local environment (VS Code + GitHub Copilot) to S/4HANA (SAP_BASIS	754), I get an error:

> MCP error -32603: Error: SAP Error: Resource INCLUDE Z_TEST_REPORT is not locked (invalid lock handle: 100C362A2C68415F9EE40FF583C4C87027869987).

SM12 i

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/12) · 2026-03-08 · closed · external user · 8 comments

### Not able to create or update.  Reads are working.

I am using this with claude code, and a global install of mcp-abap-atd.  My SAP system is on prem, at level 740.  I do have eclipse IDE and I am able to create and update there, so I know ADT is working.  I am supplying a modifiable transport #.

Any suggestions appreciated.

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/11) · 2026-02-26 · closed · external user · 41 comments

### Dump when changing with a wrong transport request number

If a tool is called with a transport request number different from the one that is locking the object, it dumps.

Prerequisites:
An object (e.g., a class) is locked in a transport request.

Steps:
1. Run a tool, e.g., update the class with a different transport request number

Result:
Error 500

In ST22, there is a dump with a description that the object is locked in a different TR number.

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/10) · 2026-02-26 · closed · outside contributor · 8 comments

### The tool GetTypeInfo does not return data for structures

It is not logical because the 'Type' category in the ABAP Dictionary relates to data elements, table types, and structures.
Structures should also be addressed.
Additionally, agents also expect structures to be returned by this tool.

Technical info:
Handler is located in
\src\handlers\system\readonly\handleGetTypeInfo.ts

Getting structure info can be referred to in the following handler (even it can be reused):
\src\handlers\structure\high\handleGetStructure.ts

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/8) · 2026-01-30 · closed · external user · 2 comments

### Correct processing of 409 error for all updating tools

There is a common problem: sometimes the MCP server does not return a detailed error message.
Instead, only generic information about the 409 error is provided.
One common issue is locking an object in a transport request.

For some specific tools, this issue has been fixed (see the following issues):
https://github.com/fr0ster/mcp-abap-adt/issues/5
https://github.com/fr0ster/mcp-abap-adt/issues/3

However, this problem may affect all update tools and should be fixed in general.
Also, code refac

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/7) · 2026-01-30 · closed · external user · 2 comments

## Most recent

### CreateProgram / UpdateProgram missing from tools/list in v8.13.0 despite being registered in HighLevelHandlersGroup.js

Running @mcp-abap-adt/core v8.13.0 via MCP. CreateProgram and UpdateProgram are documented in the README under "Program Management" and were added in #68 / fixed in #105, but they never appear in tools/list sent to the MCP client — confirmed across /mcp reconnect, full client restart, and a brand-new session/connection (so not a client-side cache issue). GetProgram (read-only, different package mcp-abap-adt) works fine. Sibling high-group tools in the same file/group (CreateClass, CreateTable, C

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/184) · 2026-08-24 · open · external user · 0 comments

### CreateFunctionGroup reports failure but creates the function group

## Summary

`CreateFunctionGroup` returns an error and **creates the function group anyway**. A caller that
trusts the error does not clean up, and the object is left behind.

Reproduced three times on a 7.5x system (SAP_BASIS 816), with three different names, on
`@mcp-abap-adt/core` 8.13.0.

## Symptom

```
CreateFunctionGroup { "function_group_name": "ZZTEST_FG1", "package_name": "$TMP",
                      "description": "probe" }
-> Failed to create function group ZZTEST_FG1: Function grou

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/183) · 2026-08-24 · open · external user · 0 comments

### SAP_LANGUAGE from --env-path never reaches process.env

**Version:** `@mcp-abap-adt/core` 8.13.0.

### Symptom

`SAP_LANGUAGE=EN` in the file passed to `--env-path` has no effect. It is documented in
`launcher.js --help` as *"SAP language (optional, e.g., EN, DE)"*.

### Cause

The launcher hydrates only six keys from the env file into `process.env`, and `SAP_LANGUAGE` is not
among them. `systemContext.ts` then reads `process.env.SAP_LANGUAGE` and finds nothing, so
`masterLanguage` falls back to the library default.

The setting is therefore inert **

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/182) · 2026-08-24 · open · external user · 0 comments

### CheckProgram / CheckFunctionGroup force chkrun:version="inactive" and report syntax errors on sound objects

**Versions:** `@mcp-abap-adt/core` 8.13.0 with `@mcp-abap-adt/adt-clients` **8.0.0** (the nested
resolution in a global install). Also reproduced against `main` at `05688ee` with `adt-clients`
10.1.0, so this is not release-specific.

### Symptom

```
CheckProgram { "program_name": "RSPARAM" }
-> Objekt RSPARAM ... 1 error:
   "Die REPORT-/PROGRAM-Anweisung fehlt oder der Programmtyp ist INCLUDE."  MESSAGE(G46)
```

`RSPARAM` is a standard SAP program. It has no syntax error.

The same happens f

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/181) · 2026-08-24 · open · external user · 0 comments

### High-level write handlers fail — session not stateful, lock handle invalid

# GitHub Issue: High-level write handlers fail — session not stateful, lock handle invalid

**Repository:** https://github.com/fr0ster/mcp-abap-adt

---

## Title

High-level write handlers (UpdateClass, UpdateFunctionModule) fail with "invalid lock handle" — `setSessionType("stateful")` not being called before lock operations

## Description

When using `@mcp-abap-adt/core` as an MCP server against an on-premise SAP CRM system, all high-level write operations (`UpdateClass`, `UpdateFunctionModu

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/177) · 2026-08-19 · open · external user · 0 comments

### CreateProgram does not respect SAP_LANGUAGE env var for masterLanguage

When `SAP_LANGUAGE` is set to `"ZH"` in the environment, programs created via the `CreateProgram` tool have their Master Language set to `"EN"` instead of `"ZH"`.

The environment variable `SAP_LANGUAGE=ZH` is configured in both `.mcp.json` and `.env`, and the login language is correctly set to `"ZH"`. However, the `masterLanguage` attribute of created ABAP objects (PROG, CLAS, etc.) is always set to `"EN"`.

## Expected Behavior

- `CreateProgram` (and other `Create*` tools) should use the `SAP

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/105) · 2026-06-09 · closed · external user · 1 comment

### The UpdateFunctionModule operation will lose FM parameters.

The UpdateFunctionModule operation will lose FM parameters.

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/77) · 2026-04-25 · closed · external user · 1 comment

### UpdateInterface fails with "Parameter corrNr could not be found" on SAP BTP ABAP Cloud

### Description                                                                                                                                                                                                                                                                                                                                         `UpdateInterface` always fails on SAP BTP ABAP Cloud systems. `UpdateClass` works correctly
  with the same transport request, same session, same parameters

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/61) · 2026-04-15 · closed · external user · 1 comment

### Extend MCP tools for Object History and Transport Requests

Are you planning to extend the MCP tools for Object History?

What I want to achieve is to do a code review with a Custom Agent that uses MCP tools and check only the code modified in the last Transport Request.

And for that I guess we need:

1. A tool to get all the Transport Requests from an object. 
2. a) A tool to get the code at a specific Transport Request (e.g., GetObjectVersionAt). 
    b) A tool to get the code diff between two Transport Requests (e.g., GetDiff).

Thanks for your hard 

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/30) · 2026-04-01 · closed · external user · 0 comments

### A mistake in CLINE_CONFIGURATION.md

Sorry, I am new to GitHub, so not pretty sure how to report the findings in documentions.

Can you please correct this part from SAP_USER to SAP_USERNAME?
This tiny mistake made me nuts for an hour yesterday, misleading me that the client number was wrong :)

```
SAP_URL=https://your-sap-system.com
SAP_CLIENT=100
SAP_USER=your-username
SAP_PASSWORD=your-password
# or for JWT authentication:
# SAP_AUTH_TYPE=jwt
# SAP_JWT_TOKEN=your-jwt-token
```

https://github.com/fr0ster/mcp-abap-adt/blob/main/

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/14) · 2026-03-08 · closed · external user · 1 comment

### "MCP error -32603: Error: New code check failed" when connecting with DE language

One more issue from my side:

My company language is German, so when connecting under the default DE language, it throws an error:

> MCP error -32603: Error: New code check failed: Program check failed: Objekt Z_TEST_REPORT wurde geprüft.

The root cause is in utils.ts:1129:

```
/**
 * Check if error message indicates object was already checked
 * Used to handle "has been checked" / "was checked" messages as non-critical
 * @param error - Error object or error message string
 * @returns true i

[Read the thread](https://github.com/fr0ster/mcp-abap-adt/issues/13) · 2026-03-08 · closed · external user · 1 comment

The remaining reports are on [the project's issue tracker](https://github.com/fr0ster/mcp-abap-adt/issues).
