SICK — SAP Installation Check
SICK is used to run consistency checks that help identify installation, repository and system-configuration inconsistencies. It is most useful after installation, upgrade, system copy or technical maintenance when Basis needs a quick consistency check of core system setup. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for SICK — SAP Installation Check. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 621 words
Purpose
run consistency checks that help identify installation, repository and system-configuration inconsistencies. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
SICK is typically used after installation, upgrade, system copy or technical maintenance when Basis needs a quick consistency check of core system setup. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Run SICK after the technical activity or when SAP guidance requests it.
- Read each reported finding in its release context.
- Separate informational messages from actionable inconsistencies.
- Correct the underlying installation/configuration issue rather than suppressing the check.
- Re-run the check and retain the before/after evidence.
Key data objects
These are the most useful anchors for work in SICK. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- system release — verify the exact value and its relationship to the affected execution or business object.
- installed components — verify the exact value and its relationship to the affected execution or business object.
- repository consistency — verify the exact value and its relationship to the affected execution or business object.
- database/system configuration — verify the exact value and its relationship to the affected execution or business object.
- reported check findings — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
SICK remains listed by SAP among Basis administration transactions for ABAP systems. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Treating every message as a production outage. Validate the exact object, user, timestamp and release context before applying a fix.
- Applying fixes from a different release without checking applicability. Validate the exact object, user, timestamp and release context before applying a fix.
- Using SICK as a substitute for full post-upgrade validation. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the BASIS team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/sickERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.