← ClaudeAtlas

sap-se37listed

Deploys ABAP function module source to a SAP system via SE37 (SAP GUI Scripting) — creates or updates FMs: existence check, source upload (full FUNCTION … ENDFUNCTION include), save, activate. Also four secondary modes on an existing FM: check-and-fix ("fix FM" / "check and fix FM" with no source — syntax-check, download, fix, re-upload, activate); change-attributes (Short Text / Processing Type: Regular / Remote-Enabled / Update Module); reassign-function-group ("reassign FM <X> to <FG>" — moves it, then re-activates); delete ("delete <FM>" — irreversible, asks for explicit confirmation, verifies removal). Handles the original-language + Workbench-request popups per /sap-transport-request. Prerequisites: active SAP GUI session (/sap-login first).
sapdev-ai/sap-dev · ★ 7 · DevOps & Infrastructure · score 73
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. > **Pre-deploy quality (recommended).** An FM's `FUNCTION…ENDFUNCTION` source is a > *fragment* — it only fully compiles inside its function group. Run > `/sap-check-abap <file>` first for the offline + `fm` dimensions (naming, types, > SQL, CALL FUNCTION signatures); its `syntax` dimension now also gives a > **best-effort pre-insert body check** (Strategy A `-Wrap`: the fragment is wrapped > as a self-contained program so undeclared-field / typo errors are caught before > any GUI upload, findings line-mapped to the original file), degrading to > `SYNTAX_COULD_NOT_CHECK` only when the signature is too complex to model. That > pre-check does **not** replace the authoritative gate: the full **compiler syntax > check happens in-context** here, via the Ctrl+F2 that runs after the FM is saved > inactive into its function group (below). Task: $ARGUMENTS ## Shared Resources | File | Purpose | |---|---| | `<SAP_DEV_CORE_SHARED_DIR>/rules/safety_policy.md` | **Rule 0 (highest priority)** — environment guard; enforced by Step 0.6 via `sap_safety_gate.ps1` | | `<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`