sap-se37listed

Deploys ABAP function module source code to a SAP system via SE37 using SAP GUI Scripting. Creates new function modules or updates existing ones. Existence check (SE37 Display), source upload to the Source code tab, save, and activation. Source is the full function include (FUNCTION <name>. through ENDFUNCTION.). Also supports check-and-fix mode: when no source file is provided and the task is "fix FM" or "check and fix FM", opens the FM in SE37, runs a syntax check (Ctrl+F2), downloads the source, fixes all errors, re-uploads, and activates the FM. Also supports change-attributes mode: when the user asks to change a function module's Short Text or Processing Type (Regular / Remote-Enabled / Update Module + update kind), opens SE37 in change mode, selects the Attributes tab, updates the supplied fields and saves. Handles the conditional original-language popup and the post-save Workbench-request popup per `/sap-transport-request`. Also supports reassign-function-group mode: when the user asks to move a functi
sapdev-ai/sap-dev · ★ 4 · Code & Development · score 77

Install: claude install-skill sapdev-ai/sap-dev

# SAP SE37 Function Module Deploy Skill You deploy ABAP function module source code to a live SAP system via SE37 using SAP GUI Scripting. The skill checks if the function module 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 FM source must follow modern syntax, OOP scaffolds, no literal MESSAGE strings, perf-band-appropriate SQL. Run `/sap-check-abap` and `/sap-check-fm` 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 **FM 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.