BACK

Creating test Environments in SAP

Up-to-date data in productive systems are a must for all companies that use SAP.  But what about the data in test systems? It makes sense to have current data in your test systems to ensure accurate testing and the objective is quite simple, however the way to get there is rather more difficult.

A complete copy of your SAP productive system often oversteps hardware, resources, time and budget limits. Companies are facing similar problems during the migration of their primary productive system to SAP HANA.

 

Staying upto date

This shouldn’t be a problem, but in practice the data on the development and test systems are usually outdated. With a rapidly growing SAP systems, testing new developments, check changes in customising. Usually the requirement is to check these changes against the current developments, configurations and the support systems of the SAP landscape.

 

What to Copy?

Apart from conventional SAP system copies, there are a number of approaches in order to transfer the productive test data to the development and test systems.

 

This is divided into two categories:

 

  • Complete System Copy
    A complete copy of the productive system, which requires a lot of storage space of the entire system landscape as a consequence.

 

  • Selective System Copy
    Only the data that is actually needed is transferred from the productive system. The system landscape therefore reduces the load on the system and the test environment stays lean.

 

The Smart Approach for creating Test Environments in SAP

A complete copy of the productive system, which requires a lot of storage space.

Partial copies of SAP systems, create savings and make complete copies superfluous in many cases. Additionally, they can be automated and enable the generation of test data in real time. They are particularly recommendable for planned migrations to SAP HANA.

 

Regardless as to whether a complete or selective copy is made, when looking for a good solution the following criteria are important:

 

  • Full integration of the solution into the SAP landscape
  • Support of all SAP products to be copied
  • Update frequency of development or testing systems
  • Stronger focus on maximum flexibility or maximum usability
  • Availability of predefined solution modules (e.g. copy and selection rules)
  • Criteria according to which data is to be copied selectively (e.g. on an application or time basis)
  • Need for a cyclic time slice approach 
for all tables
  • Consideration of customer applications or possibility to fully integrate 
such applications with little effort
  • Data anonymity or pseudonym requirements

One comment on “Creating test Environments in SAP

Leave a Reply

Your email address will not be published. Required fields are marked *