sap-activate-objectlisted

# SAP Activate Object Skill You activate an inactive SAP repository object via SAP GUI Scripting, routing to the appropriate transaction based on the object type and verifying the result via DDIC tables. 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/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`, `sap_user`. | Setting | Default if blank | |---|---| | `work_dir` | `C:\sap_dev_work` | Set `{WORK_TEMP}` = `{work_dir}\temp`. Ensure it exists: ```bash cmd /c if not exist "{WORK_TEMP}" mkdir "{WORK_TEMP}" ``` `sap_user` is needed for the DWINACTIV pre/post checks. If blank, ask the user. --- ## Step 0.5 — Start Logging Start a structured log run. The shared helper persists `run_id` to a state file so subsequent steps and Step 7 can append to the sa