How we compare
Most SAP teams use one of four approaches: full system copies, client copies and scripts, an SAP add-on copy tool, or a test data platform that runs outside SAP. Here's how they differ, and how to switch without a gap in testing.
Renewal coming up? Run one refresh side by side first, and decide with numbers instead of a feature list.
On SAP, we measure results on your own data in a 10-day validation.
Side by side
Descriptions are of typical tools in each category. Check any specific product against its own documentation.
| Full system copy | Client copies and scripts | SAP add-on copy tools | Synthesized | |
|---|---|---|---|---|
| Where it runs | Database or system level | Inside SAP | Installed in the SAP system as an add-on | Outside SAP, connected through OData or HANA |
| Test system size | The same as production | Whole clients, or what scripts select | Reduced by data type and date | Reduced by business keys and dates |
| Personal data | Copied as is | Copied unless scripts mask it | Scrambling rules you maintain | Found and masked, including Z-tables |
| Systems outside SAP | Separate copies | Separate copies | Usually SAP only | The same rules and values in SAP and non-SAP systems |
| Data production doesn't have | No | Manual entry | Usually no | Generated on request |
| Test automation | Not designed for it | Not designed for it | Varies | Tricentis Tosca and UiPath integrations |
| Who runs it | Basis team | Basis specialists | Trained specialists | Test or Basis teams, self-service |
Running outside SAP
UpgradesNothing to upgrade in SAPNo add-on to re-test or re-certify when you move to a new S/4HANA release.
Clean coreFits a clean coreSAP asks customers to keep custom code and add-ons out of the core. A tool outside SAP leaves the core alone.Connected systemsOne set of rules for the whole processOrder-to-cash runs through SAP, the CRM and the data warehouse. One tool covers all of them.Questions to ask any vendor
Use it whichever tool you choose. Each question maps to a common reason SAP refreshes fail or stall.
Switching
We've got you covered
It depends on how often you refresh and what's in scope. Full copies suit rare refreshes of small systems; scripts suit simple, stable scopes; an add-on suits SAP-only landscapes with a specialist to run it; a platform outside SAP suits frequent refreshes across SAP and non-SAP systems, with masking.
A system copy duplicates a whole SAP system, every client included, usually at database level. A client copy copies one client, remotely with SCC9 or by export with SCC8, using a copy profile that sets whether transaction data comes along.
You recreate them during the validation, and add rules for any personal data the scan finds that your current rules miss.
SAP hasn't released TDMS for S/4HANA. See how each TDMS scenario maps across.
Yes. Some teams keep their current tool for SAP client copies and use Synthesized for cross-system and generated data first.
Next step
Tell us when your current tool renews. We'll run one refresh on your landscape before that date.
SAP, S/4HANA, SAP HANA, SuccessFactors, Ariba, Concur and other SAP products and services mentioned herein, as well as their respective logos, are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.
