SAP system deployment scenarios
Possibility of manual intervention in case of delta import
Unicode conversion: A Unicode target system is built from a non-Unicode source system. Unicode conversion can only be performed using procedures based on R3load.
The suite idea has established itself here as well as in many other software areas. And for good reasons. In addition, such automation tools are moving even more strongly in the direction of the IT topic of system management.
Consideration of additional QA clients
Until now, it has been common practice to create test systems as a client or system copy of the production system on a specific date. In these cases, a single client or the entire SAP system is duplicated. The corresponding instances of the SAP system have to be reinstalled. In addition, a copy of the source database must be created. These are standard procedures, but they can be disproportionately expensive for productive data sets of several terabytes. SAP and third-party tools for selective data extraction can significantly reduce the cost of deploying non-production SAP systems.
"The creation of SAP system copies used to represent an enormous effort," says Martin Schulz from SAP Basis Administration. Almost 4,000 employees worldwide access our SAP systems directly. If the SAP systems are down, then nothing works in many departments - and that certainly happened in the past. Although the actual copying process is completed in just a few hours, the manual post-processing - which includes, for example, adjusting parameters, users and rights, profiles, system settings and interfaces - can take up to a week. This keeps the entire seven-person SAP Basis team busy.
SAP system copy is made much easier by the "Shortcut for SAP Systems" application.
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.
You must purchase all required licenses for SAP Landscape Management from SAP.