Differentiation between homogeneous and heterogeneous SAP system copy
This is why companies need professional test data management
Preparation before system copy - All information about transport requests that should be re-imported on the target system of the system copy is evaluated and collected: Already released transport requests that have not yet landed on production. Open transport requests that should survive the system copy (maintain development status). The respective owners of the transports have the possibility to discard an obsolete development.
RFC data transfer was completed within 1 day. Effort decreases from 1st test to 2nd test to final copy.
Easy integration also in the system copy of systems of older releases possible!
Internationally active companies that operate systems with several terabytes of data and hundreds of users in different time zones depend on high system availability. If necessary, the system is copied incrementally, table by table, on weekends and at night. Complete shutdown of the production system is best avoided altogether.
The guideline that integrated job logic is preferable to customizing has also proven its worth. The key point here is that each step of a copy job knows the overall context, including the steps that preceded and follow it.
From now on, this will be easier. "Shortcut for SAP Systems" contributes to a time-optimized execution of this complex process, no matter when and at what frequency, and while maintaining a high degree of flexibility even in changing environments.
Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.
But providing test data can also prove to be a challenge.
For each group the parameters jobNum, taskArgs and loadArgs can be defined separately.