Risk-Based Testing for SAP Change

Keep this: job aid

Risk-based testing card for SAP releases

• Write risks as: "[Process] for [scope] may [fail], resulting in [consequence]."
• Separate product risks (drive tests) from project risks (drive the plan).
• Impact from process owners; likelihood from people who know the change.
• Inputs: process criticality, transport and configuration content, SCMON/SUSG or ST03N usage, defect history.
• Overlay periodic processes (month-end, year-end, price updates) on usage data.
• Agree written 1–3 or 1–5 scales; cap the share of high ratings.
• High risk: more variants, negative tests, owner review, early execution, journal-entry evidence.
• Link every test to a risk ID; every high risk to its tests.
• Update the register weekly, daily in the final week; re-score with date and reason.
• At sign-off: mitigated / partly / not mitigated, with owner, workaround, date and expiry.