/sap-se51

name: sap-se51
description: |
  Maintains screens (dynpros) in a SAP system via SE51 using SAP GUI
  Scripting. Two modes:
  (a) FLOW LOGIC — create new screens or update an existing screen's flow
      logic (PROCESS BEFORE OUTPUT / PROCESS AFTER INPUT). Existence check
      (SE51 Display), flow logic paste via Windows clipboard, save, activate.
  (b) LAYOUT / ADD ELEMENT — add layout elements (static Text labels,
      Input/Output fields, checkboxes, pushbuttons, radio buttons) to an
      existing screen via the ALPHANUMERIC Screen Painter (Edit > Create
      Element). This is the only scriptable placement path: the graphical
      drag-and-drop Layout Editor is a non-scriptable ActiveX control the
      recorder cannot capture, and the element-list grid is read-only for
      placement. Requires the per-user "Graphical Layout Editor" setting OFF.
  Prerequisites: Active SAP GUI session (use /sap-login first).
argument-hint: "<program-name> <screen-number> [path-to-flow-logic | --add-element <element-file>]"

SAP SE51 Screen Painter Deploy Skill

You maintain screens (dynpros) on a live SAP system via SE51 using SAP GUI Scripting.

**Mode dispatch — decide first:**

| User intent | Mode | Where | |---|---|---| | "deploy/update flow logic", "set PBO/PAI", a `.txt`/`.abap` flow-logic file | **Flow Logic** | Steps 0–7 below | | "add a field / text / checkbox / button to a screen", "add BUKRS and WERKS to the layout", "put an I/O field on the screen" | **Add Layout Element** | jump to **Mode: Add Layout Elements** (near the end) |

The flow-logic mode (Steps 0–7) checks if the screen exists, then creates or updates its flow logic. The add-element mode drives the alphanumeric Screen Painter to place new elements on an existing screen's layout.

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` instead of asking for the TR itself | | `<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>/scripts/sap_attach_lib.vbs` | Parallel-safe session attach (`%%ATTACH_LIB_VBS%%`) — every reference VBS includes it and calls `AttachSapSession(SESSION_PATH)` |

Skill reference scripts (`./references/`)

| File | Mode | Purpose | |---|---|---| | `sap_se51_check.vbs` | Flow logic | Existence check — SE51 Display, detect Screen Painter editor | | `sap_se51_create.vbs` | Flow logic | Create a new screen + paste flow logic (clipboard, `wscript`) | | `sap_se51_update.vbs` | Flow logic | Update an existing screen's flow logic (clipboard, `wscript`) | | `sap_se51_add_element.vbs` | Add layout element | **Append** loose layout elements (Text/IO/Checkbox/Pushbutton/Radio) from a tab-delimited element file via the alphanumeric Screen Painter. `NOT_ALPHANUMERIC` guard; `txt[0,row]` anchor fallback; 3× focus+menu retry. `cscript`. | | `sap_se51_layout_rebuild.vbs` | Add layout element | **Rebuild** the work area into tidy "label + input field" lines from a tab-delimited line-spec, via gap-cell discovery. All-or-nothing (discards on any shortfall — live screen untouched). Use for *"make each field its own line with a label and input"*. `cscript`. |

---

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))"

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_TEMP}" mkdir "{WORK_TEMP}"

Set `{RUN_TEMP}` = the per-run scratch dir (`Get-SapRunTemp` mints + creates `{work_dir}\temp\run_<id>`):

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

Per the CLAUDE.md "Two-bucket temp model" write this skill's generated scratch (`*_run.ps1` / `*_run.vbs` and the `_run.json` state) under `{RUN_TEMP}`; keep `{WORK_TEMP}` (base) only for `Get-SapCurrentSessionPath -WorkTemp`.

---

Step 0.5 — Start Logging

Start a structured log run. State file: `{RUN_TEMP}\sap_se51_run.json`. Best-effort.

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_se51_run.json" -Skill sap-se51 -ParamsJson "{\"program\":\"<PROGRAM>\",\"screen\":\"<SCREEN>\"}"

---

Step 0.6 — Safety Gate (Rule 0 — `safety_policy.md`)

This skill mutates the SAP system (screen flow logic / layout elements). Run the environment gate before any SAP-side s