SAP Development Plugins for Claude: A Complete Guide to ABAP and HANA Automation

The Claude-Plugins Community repository provides five production-ready SAP plugins—sap-dev-core, sap-gen-code, sap-migrate, sap-tcd, and sap-hana-cli—that enable Claude Code to perform ABAP development, S/4HANA migration, transaction automation, and HANA database operations.

The anthropics/claude-plugins-community repository hosts a specialized suite of SAP development plugins for Claude that transform the AI assistant into a comprehensive SAP development environment. These plugins extend Claude Code with native capabilities for ABAP code generation, custom code migration, and SAP HANA administration through a modular architecture defined in the marketplace manifest (.claude-plugin/marketplace.json).

Available SAP Development Plugins for Claude

The repository registers five distinct plugins that cover the full SAP development lifecycle. Each entry in the marketplace manifest points to an external GitHub source where the implementation resides.

sap-dev-core: The Foundation Layer

sap-dev-core serves as the mandatory prerequisite for all other SAP plugins. According to the marketplace definition at lines 114-122 of .claude-plugin/marketplace.json, this plugin provides foundational SAP development utilities including secure credential storage, BDC (Batch Data Communication) execution, and comprehensive SAP GUI Scripting support for ABAP workbench transactions like SE38, SE37, SE24, and SE11.

The plugin maintains shared resources in shared/tables/ and shared/scripts/ directories that higher-level plugins consume at runtime. When you invoke any SAP-related skill, Claude first loads this core plugin to establish authentication and session handling.

sap-gen-code: ABAP Code Generation

sap-gen-code automates the creation of ABAP artifacts from design specifications. As defined at lines 126-135 of the marketplace manifest, this plugin extracts structured data from documents, validates DDIC (Data Dictionary) objects, and generates production-ready ABAP code including CDS views and unit tests. It performs an AI-assisted semantic and security review before outputting final artifacts.

The plugin builds upon sap-dev-core's shared scripts to access the ABAP repository and execute generation pipelines, allowing Claude to produce runnable ABAP code directly from markdown or JSON design specs.

sap-migrate: S/4HANA Migration Engine

sap-migrate manages custom-code migration campaigns to S/4HANA. The manifest entry at lines 138-147 describes a workflow that inventories custom objects, flags unused code, runs S/4HANA-readiness ATC (ABAP Test Cockpit) checks, and performs bulk remediation in sandbox environments.

This plugin orchestrates multi-step migration workflows by leveraging sap-dev-core for credential handling and script execution, enabling Claude to triage findings and generate migration reports automatically.

sap-tcd: Transaction Automation

sap-tcd automates common SAP business processes through GUI scripting. Defined at lines 150-159 of the marketplace file, this plugin exposes high-level commands for creating and maintaining Business Partners (BP), Material Masters (MM01), and Sales Orders (VA01).

The plugin utilizes sap-dev-core's GUI-scripting layer to drive the SAP GUI, translating natural language requests into precise transaction executions.

sap-hana-cli: HANA Database Operations

sap-hana-cli supplies over 150 command-line tools for SAP HANA administration. The marketplace entry at lines 17089-17096 registers this plugin as an MCP (Model Context Protocol) server, enabling Claude to execute schema exploration, data import/export, performance monitoring, and security auditing through simple command interfaces.

How the SAP Plugin Architecture Works

All SAP plugins share a common dependency on sap-dev-core, ensuring consistent authentication patterns and script reuse across the ecosystem. When a user invokes an SAP-related command, Claude Code resolves the plugin hierarchy dynamically:

1. Loads sap-dev-core to initialize the SAP connection and credential store
2. Delegates to the requested high-level plugin (e.g., sap-gen-code)
3. Executes shared scripts from shared/scripts/ to interact with the target system

This architecture prevents duplicate authentication logic while maintaining secure session isolation between different SAP systems.

Using SAP Plugins in Claude Code

The following examples demonstrate how to invoke these SAP development plugins for Claude in practice. Each command requires the appropriate plugin to be available in your Claude Code environment.

Authenticating with SAP Systems

Use sap-dev-core to establish secure connections before performing development tasks:

/sap-dev-core login \
  --host "sap.example.com" \
  --client "100" \
  --user "$SAP_USER" \
  --password "$SAP_PASSWORD"

Generating ABAP from Design Documents

Pipe a JSON or markdown specification into sap-gen-code to produce validated ABAP artifacts:

cat design_spec.json | /sap-gen-code generate-abap \
  --target "/path/to/abap/project" \
  --review

Running Migration Campaigns

Execute comprehensive S/4HANA readiness checks and remediation:

/sap-migrate start-campaign \
  --project "/path/to/customcode" \
  --output "migration_report.xlsx"

Automating Business Transactions

Create SAP business objects without manual GUI interaction:

/sap-tcd bp create \
  --name "Acme Corp" \
  --country "US" \
  --city "New York"

Querying HANA Databases

Execute SQL commands against SAP HANA through the dedicated CLI plugin:

/hana query "SELECT * FROM USERS WHERE STATUS = 'ACTIVE'" \
  --connection "hanaclient://user:pwd@hanadb.example.com:30015"

Summary

• The anthropics/claude-plugins-community repository maintains five specialized SAP plugins in .claude-plugin/marketplace.json, spanning lines 114-17096.
• sap-dev-core acts as the mandatory foundation, providing authentication and shared scripting resources that all other plugins require.
• sap-gen-code enables AI-assisted ABAP and CDS view generation directly from design specifications.
• sap-migrate automates S/4HANA custom-code migration with inventory, analysis, and bulk remediation capabilities.
• sap-tcd exposes high-level commands for automating SAP GUI transactions like BP, MM01, and VA01.
• sap-hana-cli integrates over 150 HANA administration tools as callable MCP server functions.

Frequently Asked Questions

Do I need to install all SAP plugins or just specific ones?

You only need to install the plugins matching your workflow, but sap-dev-core is mandatory for all SAP operations. The other four plugins—sap-gen-code, sap-migrate, sap-tcd, and sap-hana-cli—can be installed independently based on whether you need ABAP generation, migration assistance, transaction automation, or HANA database management.

What are the prerequisites for using SAP plugins with Claude?

Your environment must support Claude Code with MCP server capabilities, and you need valid SAP system credentials for sap-dev-core to establish connections. For sap-hana-cli, you require network access to your SAP HANA database hosts. The plugins themselves handle SAP GUI scripting dependencies and shared resource management internally.

How does sap-dev-core handle authentication security?

The plugin implements secure credential storage and session management as defined in the marketplace manifest (lines 114-122). It encrypts authentication tokens and maintains isolated session contexts, ensuring that credentials used for one SAP client cannot be accessed by another. All BDC executions and GUI scripts run within these authenticated sessions without exposing passwords in process logs.

Can these plugins connect to both on-premise SAP systems and cloud HANA instances?

Yes. The sap-dev-core and sap-tcd plugins connect to traditional on-premise SAP NetWeaver systems via RFC and GUI scripting protocols, while sap-hana-cli (lines 17089-17096) specifically targets SAP HANA databases whether they run on-premise, in SAP BTP, or in hyperscaler cloud environments. Each plugin accepts connection strings that specify the target architecture.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}