/sap-se37

name: sap-se37
description: |
  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).
argument-hint: "<function-module-name> [path-to-source]"

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` (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` (its `fm` dimension covers CALL FUNCTION signatures) before deploy when the source isn't generator-emitted. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_rfc_syntax_check.ps1` | Headless compiler syntax **pre-check** (Step 4.6) — runs `EDITOR_SYNTAX_CHECK` via the dev-init wrapper `Z_GENERIC_RFC_WRAPPER_TBL` before the GUI deploy. FM fragments use `-Subc F -Wrap` (Strategy A) for a best-effort **body** check pre-upload, findings line-mapped to the original file; degrades to COULD_NOT_CHECK (never blocks) when the signature is too complex or RFC/wrapper is unavailable. The in-context Ctrl+F2 (Step 5a/5b) stays authoritative. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_error_hints.ps1` | frequently_errors recorder. The Final step feeds deploy syntax/activation errors (`-Action record -Source SE37 -RawOutputFile ...`) so FM/METHOD-related failures are captured to the team store. Best-effort; never changes the verdict. | | `<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. (The source **upload** pastes via the Windows clipboard + SendKeys — SAP GUI reads no file — so it does NOT trip the dialog; it uses the OS-level foreground guard instead.) | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_gui_security_precheck.ps1` | Read-only allow-list pre-check (`saprules.xml`) — `ALLOWED` (exit 0) / `NOT_COVERED` (exit 1). Used by Step A before the source download. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_gui_security_sidecar.ps1` | OS-level (Win32) watcher that auto-dismisses the SAP GUI Security dialog (ticks Remember + clicks Allow). Launched as a background process before the Step A download. |

---

Step 0 — Resolve Work Directory

**Resolve `work_dir` via the env-aware helper** — do NOT take `work_dir` from a direct `settings.json` read (that ignores the `SAPDEV_AI_WORK_DIR` env var and `userconfig.json`). Use the `WORK_DIR=` value printed by:

powershell -NoProfile -ExecutionPolicy Bypass -Command ". '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_settings_lib.ps1'; . '<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_connection_lib.ps1'; Write-Output ('WORK_DIR=' + (Get-SapWorkDir)); Write-Output ('RUN_TEMP=' + (Get-SapRunTemp))"

The settings note below still applies to the OTHER keys.

**Settings reads/writes follow `shared/rules/settings_lookup.md`** — merge per-key on the `.value` field (env var → `settings.local.json` → `userconfig.json` → `settings.json`); non-per-connection writes go to `userconfig.json`. Resolve sap-dev-core paths: 2 levels up from `<SKILL_DIR>` to the plugin root, then `settings.json` and (if present) `settings.local.json`. Read `custom_url`.

| Setting | Default if blank | |---|---| | `work_dir` | `C:\sap_dev_work` | | `custom_url` | `{work_dir}\custom` |

Set `{WORK_TEMP}` = `{work_dir}\temp`

Ensure the temp directory exists:

cmd /c if not exist "{WORK_TEM