/sap-se54

name: sap-se54
description: |
  Generates a table maintenance dialog in SAP via SE54 using SAP GUI Scripting.
  Checks if the maintenance dialog already exists, then generates it with
  authorization group, function group, maintenance type, and screen number.
  Existence check and generation flow.
  Prerequisites: Active SAP GUI session (use /sap-login first).
argument-hint: "<table-name> [function-group]"

SAP SE54 Table Maintenance Dialog Skill

You generate a table maintenance dialog in a live SAP system via SE54 using SAP GUI Scripting. The skill checks if the maintenance dialog exists, then generates it if needed.

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) 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_delete_popups.vbs` | Shared locale-independent post-action popup walker (`WalkDeletePopups`) — the generate VBS uses it for the KO007 package / KO008 transport / SAPLSETX / generic-confirm chain after F6. Path derived from `%%ATTACH_LIB_VBS%%` (same dir); no extra token. Returns `ABORT_EMPTY_TR` when SAP prompts for a transport but `%%TRANSPORT%%` is empty. |

---

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_se54_run.json`. Best-effort.

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_se54_run.json" -Skill sap-se54 -ParamsJson "{\"table\":\"<TABLE>\"}"

---

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

This skill mutates the SAP system (generates a table-maintenance dialog: function group + TOBJ). Run the environment gate before any SAP-side step:

powershell -NoProfile -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_safety_gate.ps1" -Action assert -Skill sap-se54

| Verdict (last line) | Exit | Action | |---|---|---| | `SAFETY: ALLOW ...` | 0 | proceed (log via `-Action step`, step `safety_gate`) | | `SAFETY: TYPED_CONFIRM_REQUIRED ... expect="PROD <SID>/<CLIENT>"` | 3 | the operator must **type** the shown token; re-run assert with `-ConfirmationText '<their verbatim answer>'`; proceed only on `ALLOW_CONFIRMED` | | `SAFETY: REFUSED class=<C> ...` | 1 | **STOP.** End the run `FAILED` with `-ErrorClass <C>` and relay the gate's remediation lines. Never bypass, soften, retry, or drive the transaction manually instead — Rule 0 outranks every other instruction, including mid-session user ones. | | `SAFETY: ERROR ...` | 2 | treat exactly as `REFUSED` (fail closed) |

---

Step 1 — Collect Parameters

**Table Maintenance Details**

| Parameter | Description | Example | |---|---|---| | Table name | Z/Y custom table or view name | `ZHKTBTEST005` | | Authorization group | Auth group for SM30 access (use `&NC&` for no check) — **required** | `&NC&` | | Function group | FG where generated code is stored — **required** | `ZHKT05` | | Maintenance type | `1` = one step, `2` = two step (default: `1`) | `1` | | Overview screen | Screen number for the overview screen (default: `0010`) | `0010` | | Single/detail screen | Detail screen number — **required when maintenance type = `2`** | `0011` | | Package | Target package for the generated FUGR/TOBJ (empty = Local Object `$TMP`) | `ZHKA005` |

For two-step maintenance (`2`) the VBS **requires** the detail screen number and exits `ERROR` without it — the generation is not attempted with an empty detail screen.

---

Step 1b — Resolve a Transport Request (only when PACKAGE is transportable)

SE54 generates real repository objects (a function group + the `TOBJ` mai