Use case · S/4HANA
S/4HANA in production, under control from day one
No "special S/4" features: the same Basis probes, read over RFC, that matter most when a new system goes live. And the HANA database underneath, over SQL.
What it reads
Where to look after go-live
Every tab maps to a transaction, and every value comes from the system over RFC.
| Source | Transaction | What it shows |
|---|---|---|
| SNAP | ST22 | Dump type, program and user: where unadjusted code shows up |
| VBHDR · VBERROR | SM13 | Terminated and pending updates: documents that were never posted |
| TBTCO | SM37 | Job status and duration, with the deviation from the average |
| TMSBUFFER | STMS | Import queue, errors and destinations |
| BALHDR · BALM | SLG1 | Application logs filtered by outcome |
| RSAU_READ_LOG | SM20 | Successful and failed logons, users, transactions and RFC calls |
After go-live
The first weeks, when problems are new
New dumps
Type, program and user for every short dump: unadjusted code shows up here, at runtime.
Failed updates
Terminated and pending records: documents the user believes were posted.
Slower batch
Job durations compared with their average: nightly chains that get longer stand out right away.
Application logs
Filtered by outcome, with the E, W, S and I letters as SAP writes them.
During projects
Transports, locks and work processes
Transports
Import queue, errors and destinations, without opening the transaction on every system.
Long locks
Exclusive and long-running locks, the ones that stall mass loads.
Work processes
Work process status, to see when the system is saturated.
Security
A new system, with NIS2 checks from the start
Security Audit Log
Successful and failed logons and user administration on the new production system.
Compliance checks
Profile parameters, standard users, modifiable clients, certificates and the Security Audit Log, in a Word report to sign.
HANA database
Backups, disks, memory and slow queries of the underlying database, over SQL.
Declared limits
What it does not cover
SUPtime watches the technical stack. These stay with other tools.
- Fiori app and embedded analytics monitoring.
- Static analysis of custom code and simplification items: SUPtime sees their effects at runtime.
- Baselines and before/after migration comparisons.
- The SM21 system log, which is not readable over RFC: the SM20 Security Audit Log takes its place.
About to go live?
We will show you what you would see in the first weeks, on a real system.