Change Impact Analysis: From Transport and Release Note to Test Scope

Keep this: job aid

Change impact to test scope card

• Inventory every change: SAP upgrades, feature/support packs, notes, configuration, code, data, integration, roles.
• Ask explicitly: what changes in this window do not travel in a transport?
• Code: where-used list. Configuration: which business situations hit the entry?
• Map transactions and apps to process steps in the process hierarchy.
• Filter by production usage (ST03N, SCMON/SUSG); confirm rare and periodic use with owners.
• Read What's New, simplification items, Readiness Check and notes; classify unused / behavior / UI / deprecated.
• Scope = baseline + impacted regression + targeted tests; depth by risk.
• Every inclusion and exclusion gets an evidence-based reason; owners confirm.
• Run an SME review for blind spots: configuration, runtime enhancements, master data, integration, roles.
• Re-scope late changes on arrival; learn from every escaped defect.