Understanding the SAP Development Plugin Ecosystem and Dependency Chain

The SAP development plugin ecosystem in Claude's marketplace is a modular toolchain where sap-dev-core serves as the mandatory foundation, and sap-gen-code, sap-migrate, and sap-tcd extend its functionality by consuming shared resources and GUI scripting frameworks.

The anthropics/claude-plugins-community repository hosts this comprehensive SAP development plugin ecosystem that streamlines ABAP coding, S/4HANA migration, and transaction automation. All plugins are thin wrappers pointing to the upstream sapdev-ai/sap-dev repository, orchestrated through declarations in .claude-plugin/marketplace.json. Understanding the dependency chain is essential for proper installation sequence and runtime stability.

Core Components of the SAP Plugin Architecture

sap-dev-core (Required Foundation)

The sap-dev-core plugin provides the foundational utilities for SAP development, including login and connection management, credential storage, BDC execution, and add-on table maintenance. It ships with comprehensive SAP GUI Scripting helpers for transactions such as SE38, SE37, SE24, SE11, SE19, SE41, SE51, SE54, SE91, and CMOD. According to .claude-plugin/marketplace.json lines 14-22, this plugin has no dependencies and must be installed first as the ecosystem root.

sap-gen-code (ABAP Generation Pipeline)

The sap-gen-code plugin implements an ABAP code-generation pipeline that converts design documents into structured data, validates DDIC, generates ABAP code including CDS views, and produces ABAP Unit tests. As declared in .claude-plugin/marketplace.json lines 26-34, it requires sap-dev-core to access shared scripts and resources located at plugins/sap-dev-core/shared/.

sap-migrate (S/4HANA Migration Engine)

The sap-migrate plugin delivers a brown-field custom-code migration engine for S/4HANA, inventorying Z/Y objects, flagging unused code, running S/4HANA readiness ATC checks, and automating large-scale remediation. The marketplace entry at lines 38-46 of .claude-plugin/marketplace.json specifies its dependency on sap-dev-core for GUI scripting and shared tables.

sap-tcd (Transaction Automation)

The sap-tcd plugin streamlines business partner (BP), material master (MM01), and sales order (VA01) management through transaction automation. It leverages the GUI-automation framework provided by sap-dev-core, as noted in .claude-plugin/marketplace.json lines 50-58.

Understanding the Dependency Chain

The SAP development plugin ecosystem follows a strict hierarchical dependency model to ensure resource sharing and session persistence.

Installation Sequence

1. Install sap-dev-core first – This lays down shared scripts in plugins/sap-dev-core/shared/scripts/ and tables in plugins/sap-dev-core/shared/tables/ that downstream plugins import at runtime.

2. Install dependent plugins – sap-gen-code, sap-migrate, and sap-tcd automatically locate core resources via the path plugins/sap-dev-core/shared/*.

3. Runtime credential reuse – The core caches connection credentials, allowing dependent plugins to reuse authenticated sessions without re-authentication when invoking skills in the same Claude session.

Practical Implementation Examples

Below are executable Claude commands demonstrating the layered interaction between the core and dependent plugins.

Connecting to an SAP system:

/sap-dev-core login \
  --host "my-sap-host.example.com" \
  --client "100" \
  --user "DEV_USER" \
  --password "******"

Generating ABAP code from design documents:

/sap-gen-code generate \
  --design-doc "./my_design.yaml" \
  --target-package "Z_MYAPP" \
  --include-cds true

Running a migration campaign:

/sap-migrate start-campaign \
  --project "Z_LEGACY_MIG" \
  --sandbox-id "sandbox-01"

Automating sales order creation:

/sap-tcd create-sales-order \
  --customer "1000001" \
  --material "MAT001" \
  --quantity 10

Key Source Files and Architecture

The following files define the SAP development plugin ecosystem structure:

• .claude-plugin/marketplace.json (lines 14-22): Declares sap-dev-core plugin configuration, source repository, and shared resource paths.
• .claude-plugin/marketplace.json (lines 26-34): Declares sap-gen-code and its explicit dependency on the core.
• .claude-plugin/marketplace.json (lines 38-46): Declares sap-migrate plugin metadata and core requirements.
• .claude-plugin/marketplace.json (lines 50-58): Declares sap-tcd plugin configuration.
• plugins/sap-dev-core/shared/ (in sapdev-ai/sap-dev): Contains actual shared tables and scripts referenced by dependent plugins at runtime.
• plugins/sap-gen-code/: Implements the ABAP generation pipeline importing core helpers.
• plugins/sap-migrate/: Contains S/4HANA migration logic reusing core connection modules.
• plugins/sap-tcd/: Provides transaction-automation scripts that call core utilities.

Summary

• The SAP development plugin ecosystem requires sap-dev-core as a mandatory prerequisite for all other plugins in the chain.
• Three dependent plugins (sap-gen-code, sap-migrate, sap-tcd) share resources and GUI scripting frameworks from the core via plugins/sap-dev-core/shared/*.
• Credential caching in the core enables seamless session reuse across the plugin chain without repeated authentication.
• All plugin declarations reside in anthropics/claude-plugins-community at .claude-plugin/marketplace.json, while implementations live in sapdev-ai/sap-dev.
• This modular design isolates updates to the core while preserving backward compatibility for dependent plugins.

Frequently Asked Questions

What happens if I install sap-gen-code without sap-dev-core?

The plugin will fail at runtime when attempting to import shared scripts from plugins/sap-dev-core/shared/scripts/ or access the GUI automation framework. The dependency is enforced through runtime path resolution rather than package manager constraints, so installation proceeds but execution errors occur immediately when calling /sap-gen-code.

Where are the actual plugin implementations stored?

While the anthropics/claude-plugins-community repository contains the marketplace declarations in .claude-plugin/marketplace.json, the actual source code implementations reside in the upstream sapdev-ai/sap-dev repository under plugins/sap-dev-core/, plugins/sap-gen-code/, plugins/sap-migrate/, and plugins/sap-tcd/.

Can I use multiple SAP-dependent plugins in the same Claude session?

Yes. Once sap-dev-core establishes a connection via /sap-dev-core login, the cached credentials and session state are shared across sap-gen-code, sap-migrate, and sap-tcd invocations. This eliminates the need for repeated authentication when switching between SAP development tasks in the same session.

How do I update the SAP development plugins without breaking dependencies?

Update sap-dev-core first, as it contains the shared resources that other plugins import. The modular design isolates breaking changes to the core's shared resources, but dependent plugins may require synchronization if the core's API surface changes significantly. Always verify compatibility in the .claude-plugin/marketplace.json entries before updating.

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