Test Data for SAP: Master Data, Transactions and Privacy

Keep this: job aid

SAP test data checklist

• Classify every data item: configuration, organizational, master or transactional.
• Missing configuration or org units are transport defects, not data tasks.
• Per scenario: list objects, mark what gets used up, name the source and the replenishment step.
• Partition data between testers and automated runs; record reservations with the test case.
• Readiness: views exist, stock covers runs plus retests, validity dates and posting periods cover the cycle.
• Before a refresh: inventory pending transports, export test users, warn testers.
• After a refresh: re-import transports, restore users, redirect interfaces, smoke test.
• Never assert exact next document numbers; buffered ranges skip and reorder.
• Scramble personal data before tester access, consistently and format-preserving; exclude HR data.
• Synthetic for new processes and regression; scrambled copies for volume and rehearsal.