sap-se01listed

Manages SAP transport requests via transaction SE01 using SAP GUI Scripting. Two modes: (a) CREATE — default. Creates a new TR. Defaults to Workbench (W); only creates Customizing (C) when the user explicitly asks. Description is rendered per userConfig.rule_of_tr_description (ASK/PATTERN/FIXED/ RANDOM) and truncated to the 60-char SE01 limit. After creation the VBS itself resolves the new TRKORR via SE16N on E070 (filter by AS4USER + AS4DATE today, sort by AS4TIME desc, first row with TRFUNCTION K or W) and echoes `INFO: TRKORR=<...>`. (b) RELEASE — invoked as `/sap-se01 release <TR>`. Releases the TR (and any open tasks) via SE01 Transport Organizer (Display + F9 loop). Asks the user for explicit confirmation before releasing — release is irreversible. Prerequisites: Active SAP GUI session (use /sap-login first).
sapdev-ai/sap-dev · ★ 4 · Web & Frontend · score 77

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

# SAP SE01 — Transport Request Management Skill You manage SAP transport requests via SE01 using SAP GUI Scripting. Two modes: **CREATE** (default) and **RELEASE**. 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 | | `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/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 **Setti