Automate the routine Basis work, safely and on the record.
Client copy, client deletion and instance lifecycle, driven from one console with pre-checks, role-based access and a full audit trail. Batched across systems or scheduled for a window. No recorded SAPGUI macro, no shell script only its author can read.
What runs today
Agent-executed operations with pre-checks and a recorded result, rather than a macro screen-scraping SAPGUI.
Local client copy
Copy a client in place with SCCL, covering customizing, master and transaction data, under guided pre-checks, a copy profile (SAP_ALL, SAP_APPL, SAP_CUST…), a parallel-process count and BACKGROUND mode so long copies never hit rdisp/max_wprun_time. Dispatched through the collector agent and tracked to completion.
Client deletion
Permanently delete a client with SCC5 behind pre-checks and guardrails. 000/001 are protected and a login to the target client is verified first. Irreversible, so it runs behind explicit confirmation and a verified backup, and is fully recorded.
Start / stop / restart
Start, stop and restart instances and services through sapcontrol and sapstartsrv, per instance or whole system, across ABAP, SCS and HDB. Fan the same action across many systems as a batch, or schedule it for a maintenance window.
Automation you can hand to a team
Pre-checks before anything runs
Each operation validates its prerequisites before it runs. The destructive ones, SCC5 above all, verify state and require explicit confirmation against a verified backup.
Every action attributed
Who ran what, when, against which system, from which source IP, with the command output captured. The audit trail exports for compliance reviews.
Scoped by role
A 92-permission RBAC model separates who can execute from who can only watch. Service desk reads the results without touching production.
Scheduled and batched
Run a command now, schedule it for a maintenance window, or fan it across the landscape in one operation, with output streaming back per system as each completes.
Monitoring that informs the operation
You decide when to act on the levels below; the platform keeps them current across the landscape.
Kernel and patch levels
Kernel release and patch level read from disp+work, plus the DBSL patch level, surfaced per system so kernel drift across the landscape is visible at a glance.
Support tool versions
SPAM/SAINT versions alongside ST-PI and ST-A/PI, so you know what each system carries before an OCS support-package campaign.
Where automation is heading
We would rather under-promise. These are planned, tracked on the public roadmap, and not available today.
System refresh
End-to-end refresh orchestrating SCC5, SCCL and the BDLS logical-system rename as one guided multi-step operation.
Support packages
SPAM/SAINT add-on and support-package import (OCS) with guided pre-checks and queue tracking.
Kernel patching
Kernel swaps (disp+work, sapstartsrv) applied with a rolling approach to minimise downtime.
Go deeper
Common questions
What does the platform automate today?
Does it patch SAP or the kernel?
Can it do a full system refresh?
How does it reach my systems to run anything?
Is a destructive operation safe to expose?
See the automation against a sandbox.
We will walk a live SCCL client copy and a sapcontrol restart on a non-production system, show you the pre-checks and the audit record, and be straight about what is shipped versus planned.