SAP system copy SAP system update and database update - SAP Basis

Direkt zum Seiteninhalt
SAP system update and database update
SAP system copies and the DSGVO
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final copy.

Typically, the "homogeneous SAP system copy" process involves a large number of manual activities. A certain skill level is required for this, which leads to the fact that usually the employees of the SAP Basis department or external service providers realize the system copy. Depending on the structure and size of the systems, this process can take anywhere from hours to several days. In addition to making the target systems unavailable to operations and project teams, system and landscape copies also block SAP Basis administrators. Other challenges include the varying duration and quality (completeness) of the results depending on the processor, time dependency on the employees performing the work, etc.
The target system
With the entry into force of the GDPR, the topic of system copies has been expanded to include the aspect of anonymization: In many cases, personal or other sensitive data is operated on non-productive systems that usually have lower security levels and also allow access for those persons who are not normally allowed to work with GDPR-relevant data (eg developers or external consultants). For this reason, when defining the processes around system copy and, if necessary, also when selecting tools for automation, care must be taken to ensure that these also map data anonymization in accordance with the GDPR.

Powerful and sophisticated automation tools for the creation of SAP system copies provide a remedy here and demonstrably make it possible, in addition to time and cost savings, to increase the process quality of system copying, for example, or to maintain it at a consistently high level. In effect, they free up SAP Basis.

A solution such as "Shortcut for SAP Systems" offers an automatable solution for many of the activities involved in an SAP system copy.

By splitting the standard packages into several smaller packages with approximately the same 'size', the total runtime for export or import can be reduced.

For information from SAP about configuring and supporting the Connector for LaMa, see SAP Note 3078321.
SAP BASIS
Zurück zum Seiteninhalt