By babamba2
Develop SAP ABAP code in Claude Code with 25 specialized agents covering BC, Basis, and 14 SAP modules (SD, MM, FI, CO, PP, PS, PM, QM, TR, HCM, WM, TM, BW, Ariba). Create and review ABAP programs, analyze CBO objects, compare program variants, debug runtime dumps, release transports, and generate functional/technical specs — all connected to a live SAP system via MCP.
Referenced by `agents/sap-bc-consultant.md` → `<Diagnostic_Flows>`. Nine symptom-specific investigation flows. Follow the flow matching the routing-tree classification; **collect the listed evidence before recommending any fix**.
Referenced by `agents/sap-bc-consultant.md` → `<Key_Transaction_Codes>`. Every recommendation must cite one of these TCodes (or an equivalent log path) as diagnostic evidence.
SAP requirements analysis — functional specifications, gap analysis, and acceptance criteria (Opus, R/O)
SAP system architecture — technical design, ABAP architecture, and integration patterns (Opus, R/O)
SAP Ariba consultant — procurement, sourcing, supplier management, contract management, Ariba Network
Reverse-engineer an ABAP program into a Functional/Technical Specification artifact (Markdown or Excel). Socratic scope narrowing from "everything" to "only what the user needs".
CTS Transport Release workflow — list, validate, release, and confirm import
Diagnose SC4SAP plugin health, MCP server connectivity, and SAP system connection (renamed from `doctor` to avoid conflict with Claude Code's built-in `/doctor`)
View SAP system status snapshot and edit values in `.sc4sap/sap.env` (connection, blocklist) and HUD usage limits in `~/.claude/settings.json` → `env` — single entrypoint for all sc4sap runtime options
Plugin setup — detect legacy single-profile state (migrate → multi-profile), create or register a SAP connection profile under ~/.sc4sap/profiles/<alias>/, install abap-mcp-adt-powerup MCP server, optionally install DEV-only ZMCP_ADT_UTILS + ZCL_S4SAP_CM_* ALV OOP handlers (tier-gated), register both PreToolUse hooks (blocklist + tier-readonly-guard), optional SPRO / customizations extraction
Matches all tools
Hooks run on every tool call, not just specific ones
Admin access level
Server config contains admin-level keywords
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Executes bash commands
Hook triggers when Bash tool is used
Executes bash commands
Hook triggers when Bash tool is used
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Claude Code plugin for SAP ABAP development — SAP ECC / S/4HANA On-Premise / S/4HANA Cloud (Public & Private)
SuperClaude for SAP transforms Claude Code into a full-stack SAP development assistant. It connects to your SAP system via the MCP ABAP ADT server (150+ tools) to create, read, update, and delete ABAP objects directly — classes, function modules, reports, CDS views, Dynpro, GUI status, and more.
| Capability | What it does |
|---|---|
| 🔌 Auto MCP Install | abap-mcp-adt-powerup is auto-installed, configured, and connection-tested during /sc4sap:setup. No manual MCP wiring. |
| 🌐 Multi-Environment Profiles (Dev / QA / Prod) | Register multiple SAP systems per company (e.g. KR-DEV, KR-QA, KR-PRD, US-DEV) and hot-switch between them in-session via /sc4sap:sap-option. QA and Prod profiles are auto-protected: a 2-layer defense (PreToolUse hook + MCP-server guard) blocks Create*/Update*/Delete*, CreateTransport, and runtime code execution tools — bypassing the hook does not bypass enforcement. Passwords are stored in the OS keychain (@napi-rs/keyring — Windows Credential Manager / macOS Keychain / libsecret) so .sc4sap/ never leaks secrets to git. Artifacts (specs, CBO catalogs, audits) are isolated per profile with read-only cross-view so QA sessions can inspect Dev-produced specs without contaminating them. |
| 🏗️ Formatted Auto Program Maker | Builds ABAP programs end-to-end: Main + conditional Includes (OOP/Procedural), full ALV + Docking, Dynpro + GUI Status, mandatory Text Elements, ABAP Unit tests — platform-aware (ECC / S4 On-Prem / Cloud). |
| 🔍 Program Analyze | Read any ABAP object via MCP, run Clean ABAP / performance / security review, or reverse-engineer into Functional/Technical Spec (Markdown/Excel). |
| 🧪 Analyze Code | /sc4sap:analyze-code — dedicated static review pass (sap-code-reviewer): Clean ABAP, performance, security, SAP standard compliance. Severity-ranked findings with concrete fix suggestions. |
| 🔀 Compare Programs | /sc4sap:compare-programs — side-by-side business comparison of 2–5 ABAP programs that share the same scenario but split by module (MM/CO), country (KR/EU), or persona (controller/warehouse). Consultant-facing Markdown report across 10 configurable dimensions. |
| 🩺 Maintenance Diagnosis | Operational triage loop: ST22 dumps, SM02 system messages, /IWFND/ERROR_LOG, profiler traces, logs, where-used graphs — all from Claude. |
| ♻️ CBO Reuse (Brownfield Accelerator) | Inventory a Z-package once — create-program / program-to-spec prefer reusing existing CBO assets over duplicates. |
| 🧷 CBO Extension Awareness (CMOD / GGB1·2 / BAdI / APPEND) | Inventories user-exits (CMOD), substitutions & validations (GGB1/GGB2), BAdI implementations, and APPEND structures. create-program / BAPI flows prefer existing Extension fields (e.g. BAPI EXTENSIONIN / table appends) over new CBOs; dump & incident diagnosis inspects Extension points as first-class suspects. |
| 🏭 Industry Context | 14 industry reference files (retail, fashion, cosmetics, tire, automotive, pharma, F&B, chemical, electronics, construction, steel, utilities, banking, public-sector). |
| 🌏 Country / Localization | 15 per-country files + EU-common (KR/JP/CN/US/DE/GB/FR/IT/ES/NL/BR/MX/IN/AU/SG). e-invoicing, banking, payroll, tax localization. |
| 🧩 Active-Module Awareness | Cross-module integration hints: MM + PS active → auto-suggest WBS fields on MM CBOs; SD + CO active → CO-PA derivation. Details → |
| 🤝 Module Consultation | sap-analyst / sap-critic / sap-planner / sap-architect delegate to 14 module consultants + 1 BC consultant when business judgement is needed. Users can also ask a module consultant directly via /sc4sap:ask-consultant — auto-routes SD/MM/FI/CO/PP/PS/PM/QM/TR/HCM/WM/TM/BW/Ariba/BC by keywords, answers against the configured SAP environment (version, industry, country, active modules), read-only. |
npx claudepluginhub babamba2/superclaude-for-sap --plugin sc4sapComprehensive ABAP development skill for SAP systems. Use when writing ABAP code, working with internal tables, structures, ABAP SQL, object-oriented programming, RAP (RESTful Application Programming Model), CDS views, EML statements, ABAP Cloud development, string processing, dynamic programming, RTTI/RTTC, field symbols, data references, exception handling, or ABAP unit testing. Covers both classic ABAP and modern ABAP for Cloud Development patterns.
ABAP system exploration and analysis tools powered by sapcli
SAP ABAP development for Claude Code: bundles the ARC-1 MCP server (read/write/search/activate/lint/diagnose ABAP via the ADT REST API) with best-practice skills for RAP services, CDS modelling, ABAP Unit tests, clean-core audits, and UI5 modernization. Read-only by default; opt-in write gates.
Generate SAP Fiori Launchpad URLs from app names
Especialista em ADVPL e TLPP para desenvolvimento TOTVS Protheus e consultoria funcional - geracao de codigo, migracao, debug, documentacao e configuracao de dicionario
Plugin Claude Code + CLI pra ADVPL/TLPP (TOTVS Protheus): indexa em SQLite/FTS5, compila via advpls, edita .prw cp1252 sem corromper acentos e guarda credenciais no cofre nativo do OS. ~16× menos contexto consultando o Protheus.