sap-se38listed

Deploys ABAP source code to a SAP system via SE38 using SAP GUI Scripting. Creates new programs or updates existing ones. Includes program existence check (SE16N on TRDIR), source upload, syntax check, save, and activation. For Report programs (type 1), also updates selection text elements after activation. Source can be a file path or pasted ABAP code. Also supports check-and-fix mode: when no source file is provided and the task is "fix PGM" or "check and fix PGM", opens the program in SE38, runs a syntax check (Ctrl+F2), downloads the source, fixes all errors, re-uploads, and activates the program (Ctrl+F3). Also supports change-attributes mode: when the user asks to change a program's Title, Status, Type, or other header attributes (no source involved), opens the SE38 Attributes dialog and updates only the supplied fields. Handles the SAPLSETX original-language popup (only shown when logon language differs from MASTERLANG) and the post-save Workbench request popup per `/sap-transport-request`. Also suppor
sapdev-ai/sap-dev · ★ 4 · Code & Development · score 77

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/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 run state to `{WORK_TEMP}\sap_se38_run.json` so this skill's discrete bash blocks share one logical run. Logging is best-effort and never breaks the skill.