Mastering SAP System Copy: Unlocking the Secrets of Seamless Migrations

Part1 : Say Hello to tools and terminologies 

System Copy Solutions:

- Backup/Restore

- Third-party tools for data unload/load (Not Supported by SAP unless explicitly mentioned in the SAP Notes)

- SAP system copy tools

Homogeneous System Copy:

- Moving or copying an SAP system to a new environment where the source and target systems use the same operating system (OS) and database (DB) system.

- Hardware architecture remains the same or is a certified successor.

- Reasons for a homogeneous system copy include system moves, multiple components stored in one database configurations, setting up additional SAP systems, and changing the SAPSID for company-related reasons or the use of SAP reserved SIDs.

Heterogeneous System Copy:

- Moving or copying an SAP system to a new environment where the source and target systems use different OS or DB systems.

- Involves a change in hardware architecture in many cases.

- Requires a certified person for OS/DB migrations, except when using the database migration option for SUM (DMO), which automates necessary tasks.

- Depending on the method used, it may be necessary to upgrade the DB or OS of the source system first.

refer : Image from TADM70

SAP OS/DB Migration Check Service:

- Consists of OS/DB Migration Check Analysis and Verification sessions.

- Provides standardized procedures for all migrations, avoids planning errors, and offers parameter recommendations for the target system.

- Fee-based service, specific to customer location, and delivered as a remote service.

- Benefits include efficient project implementation and cooperation with experienced migration partners.

ABAP System Copy/Migration Tools:

- SAPINST: Controls the system copy process.

- R3LDCTL: Unloads ABAP Dictionary structures from the DB. When ABAP Dictionary structures are unloaded from the DB, it means that the database objects defined in the ABAP Dictionary, such as tables or views, and their associated metadata are unloaded or extracted from the database. The unloaded ABAP Dictionary structures are typically saved in files with the extension ".STR" (structure files). These structure files contain the necessary information to recreate the ABAP Dictionary structures in the target system during the system copy or migration process.

- R3SZCHK: Computes the size of ABAP tables/indexes.

- R3LOAD: Unloads or loads ABAP table data from or into the DB. It allows for the export of data from ABAP database tables into files, and subsequently, the import of that data into the target system. R3load plays a crucial role in ensuring the successful transfer of ABAP data during system copies or migrations, maintaining the integrity and consistency of the data throughout the process

- SMIGR_CREATE_DDL (ABAP Report): Generates DB-specific DDL statements for nonstandard DB objects of the ABAP Dictionary, mainly SAP Business Warehouse (BW) objects. More non standard object are Custom Tables, Custom Views, Custom Data Types, Custom Function Modules etc.

- RS_BW_POST_MIGRATION (ABAP Report): Posts system copy activities for nonstandard DB objects in the ABAP Dictionary.

Don’t get confused here, Unloading the table data refers to exporting or extracting the actual records and data stored within a database table. This process retrieves the rows of data that exist in the table, including the values for each column which is done by R3LOAD.Unloading the table structure refers to retrieving or exporting the metadata and definition of a database table without including the actual data stored within the table which is done by R3LDCTL.

Support Tools for ABAP System Copies:

- PACKAGE SPLITTER: Splits R3LOAD *.STR and *.EXT files to reduce export and import times.

- TABLE SPLITTER: Creates WHERE conditions to allow multiple R3LOADs on a single table during export and import.

- MIGMON (Migration Monitor): Allows advanced control of R3LOAD processes, supports parallel unload/load processing, and automates dump shipping between source and target systems.

- DISTMON (Distribution Monitor): Runs multiple Migration Monitors distributed over different application servers (no longer supported by SAP refer 855772). You can not download it , and if you have that software you are running at your OWN RISK!

Distribution Monitor is not released for SAP HANA.

- MIGCHECK - PACKAGE CHECKER: Verifies the start of package import.

- MIGCHECK - OBJECT CHECKER: Verifies successful creation or loading of objects in the database.

- MIGCHECK - TABLE CHECKER: Compares exported rows with imported rows for each target DB table.

- MIGTIME (Time Analyzer): Analyzes export and import run-times of R3LOAD processes.

System Copy and Migration Tools for Java:

- JLOAD: Unloads or loads JAVA dictionary structures and table data from or into the DB.

- JSIZECHECK: Computes the size of the JAVA target DB.

OS/DB Migration Verification Session:

The OS/DB Migration Verification session focuses on the following aspects:

- Analysis Session: This session involves analyzing the current system landscape and reviewing the migration project schedule. It helps identify potential issues or challenges and ensures a well-planned migration process.

- Verification Session: This session verifies the successful execution of the system copy tools and checks the consistency and integrity of the migrated system. It ensures that all objects are correctly created or loaded in the database and that the expected number of rows are imported for each target DB table.

Notes:

- The information provided here is based on TADM70 Guide and SAP Notes. It is essential to refer to the official SAP documentation and consult with experts when planning and executing system copies or migrations.

- The specific procedures, tools, and requirements may vary depending on the SAP system landscape, versions, and individual project needs.

- Always follow best practices, guidelines, and recommendations provided by SAP for a successful and smooth system copy or migration process.