← ClaudeAtlas

sap-se24listed

Deploys ABAP class source code to a SAP system via SE24 using SAP GUI Scripting. Creates new classes or updates existing ones. Existence check (SE24 Display), source upload via source-code-based view, save, and activation. Source is the complete class definition and implementation (CLASS ... DEFINITION through CLASS ... IMPLEMENTATION ... ENDCLASS). Also supports check-and-fix mode: when no source file is provided and the task is "fix Class" or "check and fix Class", opens the class in SE24, runs a syntax check (Ctrl+F2), downloads the source, fixes all errors, re-uploads, and activates the class (Ctrl+F3). Also supports change-properties mode: when the user asks to change a class's Description, Program Status, Category, or other Properties-dialog fields, opens SE24 in Display, opens the Properties dialog (Goto > Properties), toggles to change mode, updates the supplied fields, then Continues + Saves. Handles the conditional original-language popup and the post-save Workbench-request popup per `/sap-transport
sapdev-ai/sap-dev · ★ 4 · Code & Development · score 77
Install: claude install-skill sapdev-ai/sap-dev
# SAP SE24 Class Builder Deploy Skill You deploy ABAP class source code to a live SAP system via SE24 using SAP GUI Scripting. The skill checks if the class exists, then creates or updates it. Task: $ARGUMENTS ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/skill_operating_rules.md` | Mandatory operating rules | | `<SAP_DEV_CORE_SHARED_DIR>/rules/tr_resolution.md` | TR resolution flow — this skill delegates to `/sap-transport-request` (Step 1b) | | `<SAP_DEV_CORE_SHARED_DIR>/rules/language_independence_rules.md` | GUI-scripting language independence — identify by component ID + DDIC field name, status-bar checks via `MessageType` codes (S/W/E/I/A), VKey instead of menu-text, no branching on `.Text`/`.Tooltip`/window titles | | `<SAP_DEV_CORE_SHARED_DIR>/rules/abap_code_quality_rules.md` | ABAP code-quality rules — deployed class/interface source must follow modern syntax, exception-class conventions, no literal MESSAGE strings. Run `/sap-check-abap` before deploy when the source isn't generator-emitted. | | `<SAP_DEV_CORE_SHARED_DIR>/rules/sap_gui_security_handling.md` | SAP GUI Security dialog handling — the check-and-fix **class source download** (Step A) is SAP-GUI-side file IO, so it can raise the modal "SAP GUI Security" dialog (which suspends the Scripting API and hangs cscript). Pre-check + OS-level watcher wrap that download. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_gui_security_precheck.ps1` | Read-only allow-list pre-check (