Get the whitepaper!
The Test Data Imperative: Towards SAP Autonomous Enterprise

RISE with SAP

RISE with SAP test data for S/4HANA Cloud Private Edition

In RISE with SAP, SAP runs the infrastructure and you don't get operating system access, so refreshing QA means a service request for a system copy, with real production data in it. Synthesized refreshes test systems at application level with a masked, right-sized subset, on your schedule.

Book a health checkThe 10-day validation
Available on SAP Store
QA refresh options · S/4HANA Cloud Private EditionExample
System copy from production
Service request to SAP · whole system
Real data
Post-copy steps
Users, RFC destinations, transports
Your team
Masked subset with Synthesized
Company codes and dates in scope
Masked
No OS access needed
Built for the SAP & Enterprise QA toolchain
SAP S/4HANASAP AribaSAP HANASalesforceUiPathTricentis

What changes in RISE

Test data works differently when SAP runs the system

RISE moves the infrastructure and Basis work to SAP. Four things follow for test data.

01
No OS accessCustomers don't get operating system access to the managed servers, so scripts and tools that work at OS or database level don't run.
02
Copies by service requestSAP executes system copies on request. Preparing the target and the post-copy steps stay with your team.
03
Real data comes alongA copy from production brings customer, vendor and employee data into QA as it is, unless you mask it afterwards.
04
Yearly upgradesRISE customers can request an upgrade every year, and each upgrade needs a regression cycle on fresh data.

Based on SAP's published roles and responsibilities for RISE with SAP S/4HANA Cloud Private Edition. Check your own contract for what it includes.

Two ways to refresh

System copy or masked subset

System copy

A full copy, through SAP

  • Requested from SAP as a service request, then scheduled
  • The whole system, the same size as production
  • Real personal data, unless masked afterwards
  • Post-copy steps on your side every time
With Synthesized

A masked subset, on your schedule

  • Run by your team, when the test cycle needs it
  • Only the company codes and dates in scope
  • Masked before testers see it, Z-tables included
  • The same rules rerun for each cycle and each upgrade

Synthesized for SAP: key facts

SAP systems
S/4HANA and ECC, including RISE with SAP (through OData); SAP HANA 2.0+ directly
Deployment
Inside your boundary: a server, Kubernetes or OpenShift, on-premise or private cloud, air-gap capable
Integrations
Tricentis Tosca, UiPath, API and CLI
Where to buy
SAP Store, AWS Marketplace and Google Cloud Marketplace, or direct

How it fits

Outside the SAP-run landscape, at application level

S/4HANA productionCloud Private Edition
QA systemRefreshed for each test cycle
SynthesizedSubsets and masks at application level
RISE with SAP · infrastructure and Basis run by SAP
system copy: service request to SAP, real data included
Your cloud or data centre
reads what's in scope
writes a masked subset
Two routes into QA. The system copy brings everything; the subset brings only what's in scope, already masked.
  1. 01

    Connect at application level

    Synthesized runs in your cloud or data centre and connects to the RISE systems with the authorisations you approve, through SAP's OData services. Nothing is installed in SAP.

  2. 02

    Set the scope and rules

    Company codes, date ranges and business objects, plus masking rules for standard and custom tables.

  3. 03

    Refresh QA for each cycle

    Write the masked subset into QA when a test cycle or an upgrade starts.

  4. 04

    Keep system copies for what needs them

    Use SAP's system copy where you need a full, exact copy, for example to rehearse a cutover.

We've got you covered

Questions about RISE with SAP test data

Can we mask data during a RISE system copy?

The copy itself brings production data across as it is. Masking happens after the copy, or you skip the copy for QA and refresh it with a masked subset instead.

Does Synthesized need OS access to RISE systems?

No. It connects through SAP's OData services with an SAP service user you approve, so it needs neither OS nor database access.

Is S/4HANA Cloud Private Edition supported?

Yes. The SAP Store listing names S/4HANA Cloud Private Edition among the products Synthesized works with.

How often can RISE customers upgrade, and what does it mean for testing?

RISE customers can request an upgrade every year. Each one needs a regression cycle on fresh data. See SAP upgrade testing.

Does this replace SAP's system copy service?

No. Keep system copies for exact, full copies such as cutover rehearsals. Use masked subsets for the regular QA refreshes that testing needs.

Next step

Plan your next RISE test cycle

We refresh one RISE QA system with a masked subset and compare it with your last system copy.

Runs in your environmentNothing installed in SAPRead-only access to SAPSecurity and deployment
Book a health checkFind us on SAP Store

Related SAP pages

ProjectClean core test data managementClean coreProjectSAP upgrade testingUpgrade testingProjectTest data for S/4HANA migrationMigration test data
Updated October 2026

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.