sap-se38listed

Deploys ABAP source to a SAP system via SE38 (SAP GUI Scripting) — creates or updates programs: existence check, source upload (file path or pasted code), syntax check, save, activate, and (for Report type 1) selection-text update. Also three secondary modes on an existing program: check-and-fix ("fix PGM" / "check and fix PGM" with no source file — syntax-check, download, fix errors, re-upload, activate); change-attributes (Title / Status / Type / header fields via Goto → Attributes, then Save + Activate so it persists); delete ("delete program <X>" — irreversible, asks for explicit confirmation, verifies removal). Handles the SAPLSETX original-language popup and the Workbench-request popup per /sap-transport-request. Prerequisites: active SAP GUI session (/sap-login first).
sapdev-ai/sap-dev · ★ 7 · Data & Documents · score 73

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

# SAP SE38 Deploy Skill You deploy ABAP source code to a live SAP system via SE38 using SAP GUI Scripting. The skill checks if the program exists, then creates or updates it. 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 program source must follow modern syntax, OOP scaffolds, no literal MESSAGE strings, perf-band-appropriate SQL. Run `/sap-check-abap` before deploy when the source isn't generator-emitted. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_log_lib.ps1` | Structured logger. Driven via the shared `sap_log_helper.ps1` wrapper that persists `run_id` between skill steps. | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_log_helper.ps1` | Shared start/step/end wrapper around `sap_log_lib.ps1`. Persists r