Week 6 of 12
Test data and environments
Ask any SAP test lead why last night’s run failed and the answer is usually data: the customer was blocked, the material had no stock, another test consumed the purchase order, the client was refreshed.
Fix it this week, before SIT starts, because every later activity depends on it. Under RISE, note that a production-to-non-production test data refresh is an additional service, not a standard one.
This week: give every client a purpose and every test its own data
- Write down what each client is for (DEV, QAS, PRE, sandbox, training), who owns it, how it is refreshed and how often.
- Mask personal data in every copy outside production. Talk to your data protection officer before the first copy, not after.
- Make data a property of the test: each test creates, reserves or finds by criteria the data it needs. No hard-coded document numbers.
- Add the freeze rules: when transports stop during test cycles, and how emergency fixes get through.
Number of the week
Additional
is how SAP’s RISE responsibilities document classifies a production-to-non-production test data refresh.
Source: SAP Roles and Responsibilities (2025)Use this week
- Test Data & Client Strategy Planner →
Clients, masking rules, 16 test data objects and a request log.
- Test Environment & Transport Strategy (Word) →
Landscape, transport paths, freeze rules and the post-refresh Basis checklist.
Next week: the SAP system is rarely what breaks at go-live. Interfaces are.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.