← ClaudeAtlas

sap-se91listed

Manages SAP message classes via SE91 using SAP GUI Scripting. Creates new message classes or updates messages in existing ones. Existence check (SE91 Display), message text editing via inline table, and save. Messages are provided as tab-separated number/text pairs in a file. Also supports change-properties mode: when the user asks to change a message class's header attributes (Short Text, Person Responsible, ...), opens SE91 with the Header radio (radRSDAG-MIDFLAG) in change mode, updates the supplied fields on tabpHEAD, then Saves. Handles the conditional original-language popup and the post-save Workbench-request popup (per /sap-transport-request). Prerequisites: Active SAP GUI session (use /sap-login first).
sapdev-ai/sap-dev · ★ 4 · AI & Automation · score 77
Install: claude install-skill sapdev-ai/sap-dev
# SAP SE91 Message Class Maintenance Skill You manage SAP message classes and their messages via SE91 using SAP GUI Scripting. The skill checks if the message class exists, then creates or updates it with the provided messages. Supports assigning to a specific package and transport request, or saving as local object ($TMP). 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 | --- ## Step 0 — Resolve Work Directory **Settings reads/writes follow `shared/rules/settings_lookup.md`** — merge `settings.local.json` over `settings.json` per-key on the `.value` field; writes always go to `settings.local.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 `work_dir`, `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 exist