Two things we build today

The install, the groups and the skills are how we learn what to write into these two files.

Today

Words we use today

How it fits together

Claude Codein the Eclipse terminal, with your company Claude account

localhost:2234 · token

SAP ADT MCP serverpart of ADT 3.62+, runs inside Eclipse

Eclipse’s own connection to SAP

SAP DEVNetWeaver 7.40. AI writes only to one package.

Safe by default

Install 1 of 7

Eclipse with ADT, connected to DEV

1. Open Eclipse. Menu Help → About Eclipse IDE → Installation Details. Find “ABAP Development Tools”. The version must be 3.62 or higher.
2. Lower or missing? Help → Install New Software → field “Work with” → paste the address below → tick ABAP Development Tools → Next → accept → Finish → Restart.

   https://tools.hana.ondemand.com/2026-09

3. Connect DEV: File → New → Project → ABAP → ABAP Project → choose DEV from the SAP Logon list → client, user, password → Finish.

Install 2 of 7 · admin step · one person, once

The workshop package ZAI_WORKSHOP

One admin (the internal lead) does this once, in SAP. Everyone else continues with step 3.

1. Transport: transaction SE09 → Create (F6) → Workbench request → description “AI workshop” → Save. Write the number (DEVK9…) on the whiteboard.
2. Package: in Eclipse File → New → ABAP Package → name ZAI_WORKSHOP, type Development, your software component and Z transport layer → pick the transport → Finish.
3. Copies for groups 2 to 4: right-click the object → Duplicate → new name ZAI_G2_…, ZAI_G3_REPORT, ZAI_G4_… → package ZAI_WORKSHOP.
4. Test class ZAI_TEST_CLASS with one ABAP Unit test, for the morning write test.
5. Inputs: 2 Jira ticket numbers, the name of 1 old Z program, spec.md for 1 small change, dump.txt without personal data.

This becomes a standard admin step in your onboarding guide: a new project or team gets its own AI package the same way.

Install 3 of 7

Claude Code on Windows

1. Start menu → type PowerShell → open “Windows PowerShell” (no admin rights needed).
2. Paste this line (right-click pastes) and press Enter. Wait for “installation complete”:

   irm https://claude.ai/install.ps1 | iex

3. Close PowerShell, open it again, type claude, press Enter. A browser opens: log in with your company account, never a private one.
4. Check:

   claude --version

Install 4 of 7

The team folder and the terminal in Eclipse

1. Unzip the starter kit from your trainer to C:\: right-click the zip → Extract All… → type C:\ → Extract. You now have C:\sap-ai.
2. In Eclipse: Window → Show View → Other… → type “Terminal” → select Terminal → Open.
3. In the Terminal view click the small monitor icon “Open a Terminal” → Local Terminal → OK.
4. Go to the team folder and start Claude:

   cd C:\sap-ai
   claude

Why this folder: Claude reads CLAUDE.md and the list of blocked tools from the folder you start it in.

Install 5 of 7

Switch on SAP’s MCP server

1. Window → Preferences → ABAP Development → MCP Server.
2. Tick Enable ADT MCP Server and Enable access restrictions.
3. Projects: add only DEV.  Packages: add ZAI_WORKSHOP.
4. Tick Enable Edit File tool. Without it AI can only read.
5. Click Copy token, keep it for the next step → Apply and Close.
6. So the server starts with Eclipse: open eclipse.ini in Notepad (in the Eclipse folder, e.g. C:\eclipse\), add this line under -vmargs, save, restart Eclipse:

   -DadtMcpServerPrefEnabled=true

Install 6 of 7

Connect Claude Code to the server

1. In the Eclipse terminal. If you see Claude’s prompt ›, type /exit first: this command runs in the plain terminal.
2. Replace <TOKEN> with the token you copied (right-click pastes), then Enter:

   claude mcp add --transport http --scope user abap-adt http://localhost:2234/mcp --header "Authorization: Bearer <TOKEN>"

3. Check:

   claude mcp list

Install 7 of 7

The 10 skills and the team rules

1. Start Claude in the team folder: cd C:\sap-ai, then claude.
2. Type these two lines, one by one, Enter after each:

   /plugin marketplace add marian-kamenistak/sap-ai-skills
   /plugin install sap-abap@sap-ai-skills

3. Restart Claude: /exit, then claude.
4. Type /sap-abap: and wait: a list of 10 skills appears.
5. Type /memory: it must list C:\sap-ai\CLAUDE.md. That file is the team rulebook.

You can write prompts in Czech. The skills answer in the language you write in.

10:50

Install check: every laptop

1. Help → About: ADT 3.62+, DEV connected
2. claude --version answers, logged in with the company account
3. claude mcp list → abap-adt connected
4. /sap-abap: shows 10 skills, /memory shows CLAUDE.md
5. Ask:
   › Find class ZCL_… and explain what it does.
   The answer must name your tables and fields.

Not working on your laptop? No problem: each group needs one laptop where it works. Write down what failed: it goes into the onboarding guide at 14:40.

Morning write test: 5 minutes, once, on the big screen

1. The lead, on one laptop:
   › Change the comment in the first line of ZAI_TEST_CLASS to "AI write test", then check, activate and run its ABAP Unit tests and ATC.
2. Claude asks before each step. Read the diff, then say yes.
3. In Eclipse press Ctrl+Shift+F3: ZAI_TEST_CLASS must not be in the list of inactive objects.
4. Negative test:
   › Change a comment in <any object outside ZAI_WORKSHOP>.
   The server must refuse.

Pass → groups 2 to 4 let AI write in ZAI_WORKSHOP. Fail → fallback: Claude prepares the code, a person pastes it into Eclipse (Ctrl+S, then Ctrl+F3 to activate).

11:20 · stand up, 5 minutes

Split into four groups

Every group works on real code from your DEV system and hands in rows of the SDLC guide.

How to form the groups

Work as a mob: one laptop, one task, everyone helps

Swap roles after lunch. The Approver never picks “Yes, and don’t ask again” for edit, create or activate.

Ten skills along your SDLC

The rule for today: before you run a skill, open its file and read how it works. Two minutes.

The files are on GitHub: marian-kamenistak/sap-ai-skills → skills/<skill>/SKILL.md.

Run a skill by name, e.g. /sap-abap:spec-grill, or describe the task and Claude picks the skill.

Group 1 · block 1 · 11:30–12:30

Get the ticket into a file

1. Driver types:
   › Load ticket <ID> with our Jira skill and save description, acceptance criteria and comments to ticket-1.md
   You will see Claude asks “May I run…?” → the Approver says yes. A file ticket-1.md appears in C:\sap-ai.
2. Outside the company network? Open the ticket in Jira, copy the text, ask Claude:
   › Save this text as ticket-1.md: <paste>

Group 1 · block 1 · 11:30–12:30

Sharpen the spec

3. › /sap-abap:spec-grill Sharpen the spec in ticket-1.md. Ask me one question at a time.
   You will see One question at a time: “Which company codes?”, “What happens if the field is empty?”
   You do The person who knows the business answers. Nobody knows? Answer “we don’t know”: it becomes an open point. That is a result too.
4. Claude looks up every table or program the ticket names on DEV. Something does not exist? That is your first finding: the Note-taker writes it down.

Group 1 · block 1 · 11:30–12:30

Score it and save it

5. › Score the spec 0 to 10 and list what is missing to reach 8.
6. Below 8? Answer the missing points, ask for the score again.
7. › Save the final spec to spec-1.md, with the open points at the end.
8. Note-taker: how many questions, how long it took, what surprised you.

Group 1 · block 2 · 13:30–14:20

Swap roles. How does the old program work?

9. › /sap-abap:reverse-engineer Explain how program <ZPROGRAM> works: entry point, call chain, where-used, data flow. Draw a Mermaid diagram. Save it to program-explained.md.
   You will see Claude asks to read objects from DEV, one after the other. Reading is safe: here “Yes, and don’t ask again” is fine.
10. The where-used part is empty? In Eclipse open the program, right-click its name → Get Where-used List (Ctrl+Shift+G) → copy the list → paste it to Claude.

Group 1 · block 2 · 13:30–14:20

Check Claude, then do ticket 2

11. The person who knows the program picks three claims from Claude’s explanation and checks them in the code (Ctrl+click jumps to a method). Right or wrong? The Note-taker writes it down.
12. A wrong claim is valuable: it becomes a team rule (“always check X yourself”).
13. Time left: spec-grill on ticket 2, faster. Time it and compare with how long a spec usually takes.

Group 1

When you get stuck

• Where-used is empty → Eclipse where-used (Ctrl+Shift+G), paste the list.
• Tables are read as structures (DDIC), never with their data.
• your Jira skill fails → copy the ticket text by hand.

Write every “stuck” moment down: it goes into the onboarding guide. Your rows in the SDLC guide: 1 and 2.

Group 2 · block 1 · 11:30–12:30

Two options before any code

1. › /sap-abap:implement The spec is in spec.md. The object is ZAI_G2_… in package ZAI_WORKSHOP. Read it and its where-used and propose two technical options with impact and risks. Do not write code yet.
   You will see Two options, A and B, each with what changes and what could break.
   You do The most experienced developer explains both in plain words. The group picks one. The Note-taker writes down why.

Group 2 · block 1 · 11:30–12:30

Let Claude write, read every diff

2. › Implement option A in ZAI_G2_…. Write only to ZAI_WORKSHOP, transport <TR>. Then run the syntax check and activate.
   You will see “May I edit ZAI_G2_…?” with a diff: red = removed, green = added.
   You do The Approver reads the diff aloud: “it adds a check for an empty field”. Makes sense → Yes, for this one call. Not sure → No, and tell Claude why.

Group 2 · block 1 · 11:30–12:30

Is it really active?

3. In Eclipse press Ctrl+Shift+F3: ZAI_G2_… must not be in the inactive list. If it is, activate it there.
4. Open the object (Ctrl+Shift+A, type its name) and look at the change yourself.
5. Write refused (fallback)? Ask:
   › Show me the complete new source of ZAI_G2_….
   The Driver copies it into the editor, Ctrl+S, Ctrl+F3.

Group 2 · block 2 · 13:30–14:20

Swap roles. Tests from the spec

6. › /sap-abap:test-case Write ABAP Unit tests for ZAI_G2_… from the acceptance criteria in spec.md, given/when/then. We are on 7.40: isolate the database with an interface and a local test double.
7. The class reads the database itself? Claude first proposes a small interface for the data access. The most experienced developer approves it before anything is written.
8. Approve each write after reading the diff, as before.

Group 2 · block 2 · 13:30–14:20

Run the checks, fix, describe

9. › Run ABAP Unit and ATC on ZAI_G2_… and fix what fails.
10. Check yourself in Eclipse: Ctrl+Shift+F10 runs the unit tests (green bar = good). ATC: right-click → Run As → ABAP Test Cockpit.
11. › Write manual test scenarios for QAS and a short technical note for the ticket. Save them to qas-tests.md.

Group 2

When you get stuck

• Write refused → fallback: Claude shows the code, a person pastes and activates it.
• On 7.40 the tests use an interface and a test double (the newer test tools need 7.51).
• ATC over the MCP server is missing → run it in Eclipse yourself.
• “Activated” but still inactive → Ctrl+Shift+F3 and activate in Eclipse.

Write every “stuck” moment down: it goes into the onboarding guide. Your rows in the SDLC guide: 3 and 4.

Group 3 · block 1 · 11:30–12:30

Review the old report

1. › /sap-abap:code-review Review ZAI_G3_REPORT. Start from ATC, then Clean ABAP, missing AUTHORITY-CHECK, SELECT in loops, SELECT *, FOR ALL ENTRIES with an empty table, performance. Give each finding a severity and a fix. Save it to review.md.
   You will see A list of findings, most serious first. Example: “SELECT inside LOOP: asks the database 1,000 times instead of once.”

Group 3 · block 1 · 11:30–12:30

Decide finding by finding

2. The most experienced developer explains each finding in one sentence. The group decides: fix, keep (and why), or Claude is wrong.
3. Every “Claude is wrong” goes to the Note-taker: it becomes a team rule.
4. Pick the one finding worth fixing first.

Group 3 · block 2 · 13:30–14:20

Swap roles. First: tests that record what the report does today

5. › /sap-abap:refactor Write characterization tests that pin today’s output of ZAI_G3_REPORT on our test data. 7.40: interface + test double.
6. Why first: before we change old code, we save its current result. The tests run the report on test data and remember what comes out.
7. After every change the tests run again. Same result = nothing broke. Different result = the change broke something, undo it.
8. Measure the speed before: transaction SAT → program ZAI_G3_REPORT → Execute, twice. Write down the second runtime.

Group 3 · block 2 · 13:30–14:20

Improve in small steps, measure again

9. Either:
   › Refactor ZAI_G3_REPORT in small steps following Clean ABAP. After each step write, activate and run the tests.
10. Or:
    › /sap-abap:cds-rewrite Propose what moves into a classic CDS view (DEFINE VIEW, 7.40 SP05): joins and filters. What stays in ABAP?
11. Measure after, the same way. No measured gain, no rewrite.

Group 3

When you get stuck

• On 7.40 only classic CDS views work (DEFINE VIEW, from SP05).
• Claude cannot create the CDS source → a person creates it in Eclipse (File → New → Other → Data Definition), Claude edits it.
• A test turns red after a step → say no to the next step, ask Claude to undo the last one.

Write every “stuck” moment down: it goes into the onboarding guide. Your rows in the SDLC guide: 5 to 7.

Group 4 · block 1 · 11:30–12:30

Find the cause, with proof

1. › /sap-abap:bugfix The dump is in dump.txt, ticket <ID>. Find where it crashed, walk the call chain back to the entry point and show the lines that prove the cause.
   You will see The line where it crashed, the path that led there, and Claude’s explanation of why.
   You do A person confirms the cause in the code or debugger: open the object, go to the line (Ctrl+L), set a breakpoint (double-click the left margin) and reproduce. No confirmation, no fix.

Group 4 · block 1 · 11:30–12:30

Test first, then the smallest fix

2. › Write an ABAP Unit test that reproduces the bug, then the smallest fix in ZAI_G4_… (ZAI_WORKSHOP, transport <TR>). Write, activate, run the test.
3. The test should be red before the fix and green after. Ask Claude to show both runs.
4. The Approver reads each diff aloud before saying yes.

Group 4 · block 2 · 13:30–14:20

Swap roles. Document what you fixed

5. › /sap-abap:documentation Document ZAI_G4_…: purpose, inputs and outputs, tables, who calls it and what it calls, a Mermaid sequence diagram, known risks. Save it to docs-ZAI_G4.md.
6. Someone from operations reads it: would this have helped at 3 a.m. during the incident? Fix what is missing.

Group 4 · block 2 · 13:30–14:20

Prepare the transport, do not release it

7. › /sap-abap:transport-release The change is on transport <TR>, objects <list>. Write the transport description, a QAS test plan and a rollback plan. Save it to transport-notes.md.
8. Do not release the transport today. That stays with people and your normal process.
9. › Write the root-cause text for the ticket in plain language.
   A person pastes it into Jira.

Group 4

When you get stuck

• The dump comes from a file without personal data, on purpose: AI does not read dumps from the system.
• Transports stay manual: a person creates and releases them.
• Where-used is empty → Eclipse where-used (Ctrl+Shift+G).

Write every “stuck” moment down: it goes into the onboarding guide. Your rows in the SDLC guide: 8 to 10.

14:20

Demo: 4 minutes per group

1. 1  The input: ticket, program or dump
2. 2  What AI did, live or as screenshots
3. 3  Where a person stepped in, and why
4. 4  Your one team rule for the guide

14:40 · deliverable 1

The SDLC guide

At 14:55 each Note-taker sends the file to the lead. The lead asks Claude to merge the four files into one.

The guide: who fills which rows

14:40 · deliverable 2

The onboarding guide

C:\sap-ai\
├─ CLAUDE.md             rules Claude reads
├─ .claude\settings.json  blocked tools
└─ docs\
   ├─ sdlc-guide.md      deliverable 1
   ├─ onboarding.md      deliverable 2
   └─ skills\            how each skill works

Team CLAUDE.md: the short rulebook

After today

Do we need a plugin in Eclipse?

• No. Claude Code runs in Eclipse’s own Terminal view (Window → Show View → Terminal).
• The skills come with the Claude Code plugin sap-abap, not with an Eclipse plugin.
• The link to SAP is SAP’s own ADT MCP server, already part of ADT.
• There is no official Claude plugin for Eclipse. Community ones are unofficial; we leave them out.

Access Restrictions in plain words

Window → Preferences → ABAP Development → MCP Server

Approving a write

{
  "permissions": {
    "deny": [
      "mcp__abap-adt__arc1_sap_http_post",
      "mcp__abap-adt__abap_transport_create_request",
      "mcp__abap-adt__abap_feed_query",
      "mcp__abap-adt__abap_explain_object",
      "mcp__abap-adt__abap_atc_ai_*",
      "mcp__abap-adt__abap_docs_dcp"
    ]
  }
}

Why transports stay with people

• A transport moves code toward production. That decision belongs to a person.
• Claude writes only into objects already on the transport a person created.
• Claude drafts the description, the QAS test plan and the rollback plan.
• Creating and releasing transports is blocked in the tool settings.

What changes on release 7.40

When something does not work

What goes to AI, and what never does

Where to go from here

Slides by Marian Kamenistak, Engineering Leaders Community. Free to reuse with a link to this page.