sap-se14listed

SE14 (DB Utility) for stuck DDIC tables — closes the gap /sap-se11 names but never implemented. check is a read-only RFC snapshot of DDIC-vs-DB consistency (DD02L active row + pending version, DWINACTIV inactive worklist, TBATG open conversion/DB-utility request with its state, DBDIFF DDIC/DB diff, QCM<T>/QCM8<T> shadow table, DDPRH log header) -> verdict CONSISTENT / ADJUST_NEEDED / CONVERSION_RUNNING / CONVERSION_TERMINATED / NOT_FOUND; it is safe to auto-chain after a failed table activation. adjust drives SE14 "Activate and adjust database" on the **save-data path only** — the delete-data radio is structurally unreachable (no code path selects it; the save-data radio is asserted by component ID before the adjust press), not merely gated. unlock recovers a TERMINATED conversion (continue = restart; release-lock only when a QCM-data guard proves no data is stranded). Both write modes are confirm-gated, GUI-driven (SAPMSGTB, identical on both releases), and post-verified by an authoritative RFC re-read. No T
sapdev-ai/sap-dev · ★ 7 · AI & Automation · score 73

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

# SAP SE14 DB Utility Skill You diagnose a stuck table (`check`, read-only, auto-chainable) and, on request, fix it via the **save-data-only** adjust or a terminated-conversion unlock — both confirm-gated, with the delete-data path structurally refused, verified by an authoritative RFC re-read. Task: $ARGUMENTS --- ## Shared Resources | File | Token / call | Purpose | |---|---|---| | `<SKILL_DIR>/references/sap_se14_check_rfc.ps1` | `-Table` | RFC consistency battery + verdict (also the write-mode post-verify) | | `<SKILL_DIR>/references/sap_se14_adjust.vbs` | GUI (`%%TABLE%%`·`%%OUTPUT_FILE%%`·`%%SESSION_PATH%%`·`%%ATTACH_LIB_VBS%%`·`%%SESSION_LOCK_VBS%%`) | SAPMSGTB save-data-only adjust driver — **recorded + live-verified end-to-end on S4D (S/4HANA 1909) 2026-07-12** | | `<SKILL_DIR>/references/sap_se14_unlock.vbs` | GUI | SAPMSGTB conversion-recovery driver — `NEEDS_RECORDING` until captured (CONVERSION_TERMINATED cannot be safely manufactured) | | `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_rfc_lib.ps1` · `sap_connection_lib.ps1` · `sap_attach_lib.vbs` · `sap_session_lock.vbs` | libs | RFC + Tier-3 attach + session lock | | `<SAP_DEV_CORE_SHARED_DIR>/rules/safety_policy.md` + `<SAP_DEV_CORE_SHARED_DIR>/scripts/sap_safety_gate.ps1` | Rule 0 | Environment guard — Step 3 runs `-Action assert` before any write mode | | `/sap-activate-object` · `/sap-run-report` (RADPROTA) · `/sap-se16n` · `/sap-dev-status` | sub-skills | Plain reactivate / full log (v1.5) / raw dumps / wrapp