SAP system copy SAP system deployment scenarios - NW Admin

Direkt zum Seiteninhalt
SAP system deployment scenarios
Applicability of Systemcopy as a Service
For a long time, manual procedures dominated, supported by SAP (guidelines), in particular by predefined procedures and a large number of checklists. In many places, this was supplemented by scripts created in-house, which, however, only automated partial tasks/processes of an SAP system copy.

SAP SE is a software company that uses the proprietary programming language ABAP. SAP® landscapes include not only production but also Quality Assurance (QA) systems as well as test and other staging systems. For appropriate and consistent testing and acceptance of changes in programs and processes, SAP recommends the "homogeneous system copy" approach to provide non-production systems with up-to-date data.
SAP system/instance move
Table splitting requires 2 tools: R3ta, which determines the WHERE conditions used to access subsets of a table. TableSplitter, which splits the WHERE-conditions determined by R3ta into packages with one or more subsets.

The freeware Scribble Papers puts an end to the confusing paper chaos. The tool is also suitable for storing, structuring and quickly finding text documents and text snippets of all kinds in addition to notes.


To ensure that SAP solutions are nevertheless used optimally, decision-makers are well advised to regularly subject IT landscapes and applications to intensive testing. This helps to avoid potential errors and risks during operation, which can quickly lead to immense costs. But providing test data can also prove to be a challenge. Given the increased use of Big Data, storage space and resulting costs are constantly rising. In addition, testing is complicated by the growing complexity of applications and IT architecture. It can therefore be profitable for companies to invest in professional test data management, which offers decisive advantages.

Tools such as "Shortcut for SAP Systems" are extremely useful in SAP system copy.

Primarily for security reasons, no changes to SAP source systems are enabled.

On www.sap-corner.de you will also find useful information about SAP basis.

Rework, a transaction checklist: SU01 Adjust DDIC PW, SM66 Check server instance distribution, SE38 BTCTRNS1 (schedule all jobs out), SM38 Suspend jobs, SICK SAP Consistency check, SM28 Installation rework, SE06 Installastion check, SLICENSE License check, RZ10 Delete profiles, create and import OS level, RZ04, SM63 Create operation modes (optional), SMLG Delete SAP logon groups, SE14 Delete table contents: from system specific tables (emails, monitoring), SE38 RSBTCDEL (delete background jobs), SE16N Match table entries (optional), RZ12 Maintain server groups, SM61 Job server groups, create servers, SM59 Delete RFC connections, , SCC4 / SE03 Edit system: Assign system type, create and name SALE logical system, SCC4 client setting, rename to current SYSNAME, convert BDLS original system, generate SGEN ABAP Load, set up SA36 standard jobs, regenerate STRUST certificates, set/adjust SE61 logon screen, DB02 database connection, maintain PW.
NW BASIS
Zurück zum Seiteninhalt