adam0thman
UserClaude Code skills for SAP Basis / technical operations at the OS & DB layer — start/stop, housekeeping, health triage, transport, kernel patch, backup/recovery, logs, security patch, and DB-specific commands (HANA/Oracle/ASE/Db2/MaxDB/SQL Server) for NetWeaver/S4 on Linux, Windows, AIX. Cited to help.sap.com.
Categories
Indexed Skills (33)
sap-ase-hadr
SAP ASE (Sybase) HADR / Always-On built on SAP Replication Server — the RMA command surface (sap_status, sap_failover, sap_materialize), setuphadr, the Fault Manager, split-brain and when `force` is legitimate, sync vs async, the three-node DR topology. Use for "ASE HADR", "Sybase high availability", "Always-On", "ASE failover", "companion server", "split-brain ASE", "setuphadr". NOT HANA System Replication.
sap-backup-recovery
Back up and (critically) recover the database under a SAP system — backup and recovery types, log/recovery-mode prerequisites, and the per-DB restore commands for HANA, Oracle, ASE, Db2, MaxDB and SQL Server on Linux/Windows/AIX. Use for "restore the database", "recover to point in time", "backup strategy", "test restore", "brrecover", "RECOVER DATA", "db2 rollforward", "RESTORE DATABASE".
sap-btp-cli
SAP BTP command-line administration — the btp CLI (subaccounts, directories, entitlements, role collections, environments, service instances) and the cf CLI as SAP uses it, including the MultiApps plugin (deploy, bg-deploy, rollback-mta, undeploy) and mbt. Use for "btp CLI", "btp login", "create subaccount", "assign entitlement", "role collection", "cf CLI", "cf push", "deploy MTA", "mtar", "blue-green deploy", "mbt build".
sap-client-copy-accelerator
Rescue an SAP client copy (SCC9 / SCCL / SCC7) that has stalled or is crawling on ONE huge table — ACDOCA, BSEG, FAGLFLEXA, MATDOC, COEP — by moving the rows database-natively instead: batched DELETE, then parallel INSERT...SELECT partitioned by fiscal year, on HANA (Smart Data Access) or Oracle (database link). Diagnoses FIRST and exhausts the supported levers before bypassing anything; gates cross-database access on explicit licence confirmation. Use for "client copy slow", "client copy stuck", "SCC9 stuck on ACDOCA", "SCCL stuck", "accelerate client copy", "client refresh running for days", "SDA table copy", "client copy ETA 13 hours" — even when the user only says the refresh will miss its window.
sap-cloud-connector
Operate the SAP Cloud Connector (SCC), the on-premise agent linking SAP BTP to on-prem systems — start, stop, restart, the admin UI on 8443, Master/Shadow HA, ports and auto-restart, on Linux/Windows/macOS (not AIX). Use for "start/stop/restart cloud connector", "scc is down", "cloud connector admin UI 8443", "SCC high availability master shadow".
sap-compliance-docs
Map an SAP landscape or subscription to the governance, certification and usage-rights documents that apply to it — the Trust Center Compliance Finder, the certification catalogue (ISO 27001/27017/27018/27701/42001, SOC 1/2 and bridge letters, C5, PCI DSS, CSA STAR, TISAX, GxP, FedRAMP, IRAP, NIS2), AI governance, ALM usage rights (Cloud ALM, Solution Manager, Focused Run, Tricentis), and the contract stack (order form, CSD/SDG, DPA, GTC, SLAs, TOMs). Use for "which ISO certificate covers my service", "SOC 2 report for", "compliance finder", "trust center", "do we need to license Focused Run", "service description guide", "SLA document", "DPA", "what did we actually buy". Locates authoritative documents — not legal or licensing advice.
sap-crypto-pse
sapgenpse and CommonCryptoLib — managing the PSEs behind SNC and SSL/TLS: get_pse, gen_pse, import_own_cert, export_own_cert, maintain_pk, seclogin, the PSE/cred_v2 pairing that causes "works as one user, fails as another", SECUDIR, PSE types, SAProuter certificate renewal, HSM-backed PSEs. Use for "sapgenpse", "PSE", "SNC certificate", "SSL certificate SAP", "import_own_cert", "seclogin", "cred_v2", "SECUDIR", "renew SAProuter certificate", "GSS-API no credentials". Linux/Windows/AIX.
sap-db-command-reference
Start, stop, connect, status and basic backup commands for the SAP-supported databases (HANA, Oracle, ASE/Sybase, Db2, MaxDB/liveCache, SQL Server), with Linux / Windows / AIX variants. Use whenever a task needs the DB layer: "stop the database", "connect to HANA/ASE/Oracle", "is the DB up", "restart the database before/after the SAP instances", or when sap-system-lifecycle hands off DB start/stop.
sap-db2-hadr
IBM Db2 for LUW HADR under SAP — synchronization modes, multiple standbys and HADR_TARGET_LIST, VIP vs Automatic Client Reroute, cluster automation with SA MP or Pacemaker, takeover and the Graceful Maintenance Tool, rolling Fix Packs, Reads on Standby, and the non-logged operations that silently invalidate a standby. Use for "Db2 HADR", "DB6 HADR", "takeover", "standby database Db2", "HADR_SYNCMODE", "peer state", "automatic client reroute", "db2haicu", "rolling fix pack", "SQL1776N".
sap-dormant-clients
Assess whether a client is genuinely dormant and retire it safely — 000/001/066 and abandoned project/sandbox clients. Builds evidence from last logon (RSUSR200/SUIM), ST03N workload statistics, jobs (TBTCO/TBTCP), change documents and client-specific table volumes, then deletes with SCC5 (test run first) and handles what it leaves behind — TemSe, spool, T000, SAP*. Use for "can we delete client 001", "is client 066 still needed", "dormant client", "unused client", "SCC5", "client cleanup".
sap-gui-landscape
Central SAP GUI landscape configuration — SLMT (report RSLSMT) and the SAPUILandscape.xml / SAPUILandscapeGlobal.xml files SAP Logon, Business Client and SAP GUI for Java read: maintaining them centrally, distribution by UNC or HTTP(S), the LandscapeFileOnServer registry keys and HKCU-vs-HKLM precedence, and the full connection-string grammar (/H/ /S/ /M/ /G/ router chains) including SNC parameters. Also Windows client deployment: SAPSetup / NwSapSetup, silent install, AWUS, frontend SNC (SNC_LIB, SNC_LIB_64). Use for "SLMT", "SAPUILandscape.xml", "distribute SAP GUI connections", "connection string", "SAP GUI for Java SNC", "sncqop", "logon group not working", "NwSapSetup", "silent install SAP GUI", "SNCERR_UNKNOWN_MECH".
sap-hana-lifecycle-tools
The two HANA command-line tools outside SQL — hdblcm for install, update, add/remove hosts, host roles, internal network and SLD registration (resident vs media, --action, batch mode), and hdbcons for expert diagnostics when SQL is unavailable: runtime dumps, call stacks, memory analysis, savepoints, log release. Use for "hdblcm", "add host HANA", "update HANA revision command line", "hdbcons", "runtime dump", "HANA hangs SQL not possible", "call stack HANA", "mm ipmm", "log release", "cons.crashdump".
sap-hana-system-replication
Configure, operate, monitor and take over HANA System Replication — the full hdbnsutil set (sr_enable, sr_register, sr_takeover, sr_unregister, sr_changeReplicationMode, sr_state), replication and operation modes, multitier and multitarget, Active/Active read-enabled, takeover with handshake, failback, and the systemReplicationStatus / getTakeoverRecommendation checks. Establishes the revision BEFORE quoting a command, since syntax and defaults differ across HANA 1.0 SPS09-12 and 2.0 SPS01-08. Covers HA/DR provider hooks and SAPHanaSR vs SAPHanaSR-angi. Use for "set up HANA replication", "register secondary", "HSR takeover", "failback", "replication is out of sync", "logreplay vs delta_datashipping", "multitarget replication", "Active/Active read enabled".
sap-hana-xsa
SAP HANA XS Advanced operations — `xs` for normal work and `XSA` for local maintenance when remote access is gone (diagnose, collect-traces, restart, du, list-tenants). Covers the org/space model, routing mode (unchangeable after installation), the app-working directory and its sizing, global_allocation_limit, certificate expiry, tenant-database registration and the joint-recovery backup rule, and XSA under HANA System Replication. Use for "xs CLI", "XSA", "xs login", "xs apps", "XSA diagnose", "xscontroller not starting", "xs command not found", "routing mode", "app_working". NOT the BTP `cf` CLI.
sap-health-triage
First-response health check and triage for a NetWeaver / S/4HANA system from the OS shell — is it up, is it healthy, and if not, why. Uses SAPControl read-only diagnostics (GetProcessList, ABAPReadSyslog for SM21, ABAPGetWPTable, dev traces, CCMS alerts), sappfpar, disp+work, dpmon and filesystem checks. Also the out-of-band fallback when the system is jammed: sapstartsrv is a separate process, so sapcontrol still returns SM50/SM66, the dispatcher queues and the syslog when SAP GUI will not log on and RFC hangs. Use for "is <SID> up/healthy?", "all work processes occupied", "cannot log on to SAP", "RFC hangs", "system jammed", "PRIV mode", "dispatcher queue full", "why won't it start", "check the syslog / traces / work processes".
sap-housekeeping
Keep a SAP system's logs, traces, spool, job logs, ABAP dumps, audit logs and work directory from filling the filesystem — via the standard reorganization jobs (RSBTCDEL2, RSPO1041, RSSNAPDL, RSBDCREO …) and safe OS-level cleanup, on Linux/Windows/AIX. Use for "clean up logs/traces", "/usr/sap is full", "reorg spool/jobs/dumps", "housekeeping jobs", "delete old work-dir files", "audit log cleanup".
sap-kernel-patch
Patch the SAP kernel and update the SAP Host Agent on Linux/Windows/AIX — version assessment, the manual swap (stop → back up exe → SAPCAR extract SAPEXE/SAPEXEDB → saproot.sh → start → verify), Host Agent self-upgrade, rollback, and which archives you actually need: SAPEXE/SAPEXEDB exist only for SP Stack Kernels, everything between is a cumulative hotfix (DW.SAR, LIB_DBSL.SAR, TP.SAR). Covers Rolling Kernel Switch — the separate-ASCS prerequisite, StoC.xml, the mandatory cluster switch, no Java/dual-stack. Use for "patch the kernel", "kernel upgrade", "update disp+work", "update the host agent", "rolling kernel switch", "RKS", "SP Stack Kernel", "which DW.SAR do I need".
sap-log-reference
Find and read the right log or trace for any SAP component or database — instance work-directory traces (dev_disp, dev_w*, dev_ms, dev_rd, dev_icm), ABAP logs (SM21, ST22, SM50, SLG1), standalone components (Web Dispatcher, SAProuter, Cloud Connector, Host Agent, IGS) and each database's own logs (HANA trace dir, Oracle alert log, db2diag, ASE errorlog, MaxDB KnlMsg, SQL Server ERRORLOG) — from the OS shell or remotely via SAPControl. Use for "where is the log for X", "read the trace", "which log shows <error>".
sap-maxdb-ha
SAP MaxDB, liveCache and Content Server HA/DR — the four mechanisms and when each is right: cluster failover (MSCS, UNIX agents, LifeKeeper), shadow/standby via log recovery, Hot Standby with a storage-vendor HSS library, and snapshot/split-mirror. Covers why SAP recommends a shadow database over Hot Standby for DR, the read-only Hot Standby constraint, hss_enable, the single-database limit in MSCS, and log-area mirroring rules. Use for "MaxDB high availability", "liveCache hot standby", "standby database MaxDB", "shadow database", "libHSS", "hss_enable", "MaxDB cluster", "APO liveCache HA".
sap-nw-java-pi
SAP NetWeaver AS Java and PI/PO operations — NWA, the J2EE sapcontrol functions, jcmon and the telnet admin shell on 5<nr>08 as out-of-band channels, the AS Java log set (defaultTrace, std_server*.out, dev_jcontrol), and on PI: PIMON, message monitoring, the EOIO stuck-message decision tree, CPA cache and adapter traces. Explains why JCo is the WRONG tool for AS Java and what the real programmatic surfaces are (SOAP web services, monitor servlets, sapcontrol SOAP, JMX/P4, telnet). Use for "AS Java", "NWA", "PIMON", "PI message stuck", "To be delivered", "EOIO HOLD", "CPA cache refresh", "ESR", "Integration Directory", "defaultTrace", "server0", "adapter trace".
sap-oracle-dataguard
Oracle Data Guard under SAP — what SAP actually permits, which is narrower than Oracle's own documentation: physical standby only (logical is forbidden), the Broker, the three protection modes and the Maximum Protection trap that terminates the primary, Fast-Start Failover (permitted but unsupported), Active Data Guard and Far Sync licensing, and the read-only rule that blocks starting an SAP instance on a standby. Covers the DGMGRL command surface, BR*Tools interaction and standby backups. Use for "Oracle Data Guard SAP", "physical standby", "DGMGRL", "switchover", "failover", "Maximum Availability", "ORA-16724", "is Data Guard supported by SAP".
sap-os-executables
The SAP executables that cross the OS/ABAP boundary — sapevt to raise background-processing events from outside SAP (it needs no dialog work process, so it triggers work when nobody can log on), sapxpg as the controller behind SM49/SM69/DB13/SXPG_COMMAND_EXECUTE with its Y/Z privilege boundary and S_LOG_COM, and sapinst unattended with an inifile. Use for "sapevt", "raise SAP event from script", "trigger job when SAP GUI is down", "sapxpg", "SM49", "SM69", "external command failed", "SXPG_COMMAND_EXECUTE", "sapinst", "SWPM unattended". Linux/Windows/AIX.
sap-saprouter
Operate SAProuter, the application-level proxy controlling network routes to/from SAP support — start, stop, status, the saprouttab route-permission table, port 3299, SNC and niping connection tests, on Linux/Windows/AIX. Use for "start/stop saprouter", "saprouttab", "route to SAP support", "niping test", "saprouter SNC".
sap-security-patch
The monthly SAP Security Patch Day workflow — retrieve the current month's Security Notes from the Support Portal, narrow them to the subset that applies to THIS system (installed component versions + kernel), compare against what is already applied (System Recommendations / Focused Run / RSECNOTE), prioritize by CVSS/HotNews, and implement via SNOTE. Use for "check this month's SAP security notes", "which security notes apply to <SID>", "SAP patch day", "HotNews", "compare released notes vs applied".
sap-software-download
Find, qualify and download SAP software from the SAP for Me Software Center — Support Packages, kernel and patches, installation media, add-ons — and build a correct SP import queue. Resolves a component (e.g. "ST-PI 740") to exact filenames, object keys, sizes, SHA-256 checksums, the required SPAM/SAINT level and the EPS .PAT name via the Software Center's OData service, then covers where files go and how to verify them. Downloads are scriptable with X.509 client-certificate auth. For add-ons it walks the INSTALLATION vs EXCHANGE-UPGRADE tree. Use for "download a support package", "which SP is latest", "get the kernel SAR", "SP queue from SP28 to latest", "software center", "automate SAP downloads", "SAPCAR extract", "EPS/in", "SAINT installation package".
sap-space-reclaim
Landscape space-reclamation assessment — what can be deleted, what has a configurable retention, what is self-service vs change-controlled, and how much disk you actually get back. Covers ABAP technical tables (spool/TemSe, table logging, application log, job logs, dumps, IDoc/RFC queues, workload stats, change documents), the Security Audit Log archive/delete path, per-database diagnostic files and crash dumps across all six platforms, and OS-layer leftovers (work-directory traces, core dumps, old kernels, SUM directories, installation media). Honest that deleting rows does not shrink a database without reorganization. Use for "database is full", "reclaim disk", "what can we clean up", "retention settings", "core dumps", "db2diag", "adrci", "DBTABLOG huge", "TST03 huge".
sap-sqlserver-alwayson
SQL Server Always On Availability Groups under SAP NetWeaver — listener-based connection configuration (SAPDBHOST, dbs/mss/server, MSSQL_SERVER, MultiSubnetFailover and the case-sensitive JDBC parameter), why logins must be created by SWPM "Configure additional Always On Node" and never manually, the readable-secondary rules including the unsupported "Yes" setting, sync vs async and the latency guidance, WSFC without shared disks, and per-node failover verification. Also covers Database Mirroring. Use for "SQL Server AlwaysOn SAP", "availability group", "listener", "MultiSubnetFailover", "readable secondary", "SAP cannot connect after failover", "error 976".
sap-sscr-keys
SAP Software Change Registration (SSCR) — developer keys and object keys. Decide whether the system even needs them (S/4HANA, BW/4HANA and AS ABAP 7.51+ do not; NetWeaver 7.50 and below do), gather the parameters a key binds to, request them in SAP for Me, handle the 14-day post-upgrade SPAU grace window, and reassign/restore keys with RS_SSCR_KEY_UPLOAD. Covers DEVACCESS and ADIRACCESS and why you must never edit them by hand. Use for "developer key", "object key", "access key", "SSCR", "key required to modify SAP object", "register developer", "SPAU asking for object keys".
sap-support-case
Raise an SAP support case (incident) properly — earn it first by exhausting the supported remedies, route it to the right component using SAP's own routing KBAs rather than the component name the error text happens to print, gather the IDs SAP will ask for (correlation ID, formation/job ID, troubleshooting key), set an honest priority against SAP's published definitions, and get the subject and description right BEFORE submitting — the case wizard buries them in an early step and will happily submit a stale description written before you fixed half the problem. Covers the multi-step case wizard's navigation traps, the business-impact fields that unlock at High, the troubleshooting key as a customer consent decision, and what to do when a case goes out wrong. Use this whenever raising, drafting, routing or correcting an SAP case or incident, and for "raise an SAP ticket", "open a case with SAP", "create SAP incident", "which component should I use", "case priority high or medium", "SAP wants a correlation ID",
sap-system-lifecycle
Start, stop and restart a NetWeaver / S/4HANA system in the correct order — database and the instance layer (ERS, ASCS/SCS, PAS, AAS, Web Dispatcher) — using SAPControl and SAP MMC on Windows, on Linux/Windows/AIX. Use for "start/stop/restart the SAP system", "bounce <SID>", "start the app servers", "shut down for maintenance", or ordering the DB relative to the SAP instances. Hands DB start/stop to sap-db-command-reference.
sap-transport-mgmt
Move SAP transport requests at the OS layer with tp and R3trans — add to the import buffer, import single requests or import all, check status, and understand the transport directory, unconditional modes and return codes, on Linux/Windows/AIX. STMS is the preferred front-end; this is the command-line layer beneath it. Use for "import a transport at OS level", "tp import", "tp addtobuffer / showbuffer", "R3trans", "transport won't import", "/usr/sap/trans", "unconditional mode".
sap-troubleshooting
Method and rules of thumb for troubleshooting any SAP issue — establish the facts, enumerate EVERY relevant log/trace source (SM21, ST22, SLG1, ST01/STAUTHTRACE, ST05, RSAU_READ_LOG, SM58/SMQ1, /IWFND/ERROR_LOG, Java defaultTrace, kernel dev_* traces, DB and OS logs), correlate by timestamp, ask what changed, and escalate to SAP with the right evidence. Use whenever something is broken, slow, failing intermittently, or "worked yesterday" — before reaching for a restart. Pairs with sap-log-reference and sap-health-triage.
sap-web-dispatcher
Operate the SAP Web Dispatcher, the reverse proxy / load balancer in front of SAP HTTP(S) traffic — start, stop, status, ports, profile essentials and the admin UI, on Linux/Windows/AIX. Use for "start/stop/restart the web dispatcher", "webdisp is down", "web dispatcher ports/profile", "wdisp/system backend", "/sap/wdisp/admin".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.