/sap-se01

name: sap-se01
description: |
  Manages SAP transport requests via transaction SE01 (SAP GUI Scripting). Four
  modes: CREATE (default — a new Workbench TR, Customizing only when explicitly
  asked; description per userConfig.rule_of_tr_description; the new TRKORR is
  resolved locale-independently and echoed as RESULT_TR, unresolvable = hard ERROR,
  never a guess); RELEASE (`release <TR>` — pre-checks status + object inventory,
  asks explicit confirmation, releases the request + open tasks — irreversible);
  DELETE (`delete <TR>` — empties then deletes an UNRELEASED request bottom-up,
  confirms first, verifies removal; refuses released / non-dev TRs); REMOVE-OBJECTS
  (`remove-objects <TR> [OBJECTS=a,b]` — unassigns E071 entries but KEEPS the
  request, clearing the name-lock so deleted objects can be re-created).
  Prerequisites: active SAP GUI session (/sap-login first).
argument-hint: "[create [W|C] [\"<desc>\"]] | [release <TR>] | [delete <TR>] | [remove-objects <TR> [OBJECTS=a,b]]"

SAP SE01 — Transport Request Management Skill

You manage SAP transport requests via SE01 using SAP GUI Scripting. Four modes: **CREATE** (default), **RELEASE**, **DELETE**, and **REMOVE-OBJECTS**.

Task: $ARGUMENTS

Mode dispatch

Look at `$ARGUMENTS` to pick the mode:

| First token (case-insensitive) | Mode | Skip to | |---|---|---| | `release` followed by a TR (e.g. `release ER1K900234`) | RELEASE | "Release Mode" section below | | `delete` followed by a TR (e.g. `delete ER1K900234`) | DELETE | "Delete Mode" section below | | `remove-objects` / `remove-object` / `delobj` followed by a TR (e.g. `remove-objects ER1K900234 OBJECTS=ZCMD_RFCVAL`) | REMOVE-OBJECTS | "Remove-Objects Mode" section below | | `create` (or no first-token keyword) | CREATE | continue with Step 1 |

Direct callers (`/sap-transport-request`) typically use the bare CREATE form.

---

Create Mode (default)

Steps 0 – 7 below are the CREATE flow.

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 (no SQL writes on standard tables; no unsolicited deploys) | | `<SAP_DEV_CORE_SHARED_DIR>/rules/tr_resolution.md` | Transport request resolution flow — defines `way_to_get_transport_request`, `rule_of_tr_description`, and the 60-char compression algorithm. This skill is a leaf called by `/sap-transport-request`; it implements the description rendering and request-type defaults. | | `<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 |

---

Step 0 — Resolve Work Directory and Settings

**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`.

**Per-connection keys (Phase 4.4)**: `rule_of_tr_description` and `tr_description_template` are SAP-system-specific (customer naming conventions vary). Per `settings_lookup.md` § Per-connection exception, read them from `connections.json[pinned-profile].dev_defaults` FIRST (resolve the pin via `{work_dir}\runtime\session_registry.json` `ai_sessions[<id>]`); only fall back to the two-file merge when `dev_defaults` is empty.

Read:

| Setting | Default if blank | |---|---| | `work_dir` | `C:\sap_dev_work` | | `sap_user` | (must be set; ask if blank) | | `rule_of_tr_description` | `ASK` | | `tr_description_template` | (blank) |

Set `{WORK_TEMP}` = `{work_dir}\temp`. Ensure it exists:

cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}"

Set `{RUN_TEMP}` = the `RUN_TEMP=` value printed above — a fresh per-run scratch directory `{work_dir}\temp\run_<id>`, already created by `Get-SapRunTemp`. Resolve it **once here** and reuse the same value for the rest of this invocation; it isolates this run's generated wrappers / state / scratch files so concurrent runs (parallel sub-agents, multi-connection deploys) never collide. **`{WORK_TEMP}` stays the base temp dir** and is used ONLY for `Get-SapCurrentSessionPath -WorkTemp '{WORK_TEMP}'` (the session-attach plumbing derives `{work_dir}\runtime` from its parent, so it must see the base path, not the run dir). Everything the skill writes itself goes under `{RUN_TEMP}`.

The logged-in SAP user (`sap_user`) is needed for the E070 lookup. If blank, ask the user.

This skill MUST honour `<SAP_DEV_CORE_SHARED_DIR>/rules/tr_resolution.md` for description and type defaults.

---

Step 0.5 — Start Logging

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

powershell -ExecutionPolicy Bypass -File "<SAP_DEV_CORE_SHARED_DIR>\scripts\sap_log_helper.ps1" -Action start -StateFile "{RUN_TEMP}\sap_se01_run.json" -Skill sap-se01 -ParamsJson "{\"description\":\"<DESC>\",\"request_type\":\"W\"}"

---

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

Every mode of this skill