How to perform a system refresh from a production to quality system with TM
This guide describes the procedure to be followed after copying the production system to the quality assurance system using the REALTECH Transport Management. It might also be applied when performing a refresh between other systems, e.g., production to integration or integration to test, etc.
After the system copy, two main steps must be followed. The first step is optional and depends on the desired state of the quality assurance system after the copy.
Additional preliminary steps include:
Deleting all TM specific jobs on the Q-system.
For SAP WAS >= 7.0: Running the report
/RTC/TM_INI
in client 000 of the Q-system to regenerate the RFC destination to the TM server.
1. Step (optional): Retrace all requests "lost" during the system copy into the quality assurance system
Requests imported into the Q-system but not yet into the P-system before the production system's database backup, as well as requests imported between creating the backup and its application to the Q-system, are lost during the system copy. If these requests need to be re-imported into the Q-system, follow the steps below.
On May 1, 2009, a backup of the P-system BW2 was made and imported into the Q-system BW1 on May 8, 2009. The last system copy was made on October 17, 2008.
First, identify the transport requests that were imported into the Q-system but not into the P-system at the time of the backup.
In the TM tools, call the option "Import tracking -> Import tracking: Between two systems"
Placeholder for Screenshot
On the following selection screen, find the transport requests that were imported into the Q-system but not the P-system by the time of the backup creation on May 1, 2009. Use the time of the last system copy (when the last backup was imported into the Q-system) as the starting point, since there was no request delta immediately after that time, making it the reference point.
Placeholder for Screenshot
The result list contains all requests imported into at least one of the two systems within the specified period. Records are marked in different colors, depending on whether they were imported into the first system, the second system, or both. Records may also be marked in red if the import return code is greater than 4 or if it is a foreign system request or imported from SAP TMS.
To simplify further processing, restrict the view to requests only imported into the Q-system (BW1):
Placeholder for Screenshot
The result can be further analyzed as needed:
To re-import all requests, mark the entire list and click "Expand personal queue." Some requests may have been imported into the Q-system that should not be imported into the P-system. If such requests were rejected in the workflow and then deleted, they can be recognized in the result list by the "-" symbol in the "WF" column. To avoid retracing these requests, do not mark them.
Placeholder for Screenshot
After clicking "Expand personal queue," a dialog box appears:
Placeholder for Screenshot
Use the F4 help to assign a target system/target client to each target client of the marked requests. After confirming the assignment, the selected requests are added to the personal queue.
Note: The current content of the personal queue will be deleted.
The personal queue can then be called and started by "Display personal queue."
If there is a period between creating the backup on P and applying it to Q during which requests were imported into Q, these must also be re-imported. Proceed as follows:
In the TM tools, call the option "Import tracking -> Import tracking: Single system"
Placeholder for Screenshot
Use this option to identify all requests imported between creating the backup and its application to Q:
Placeholder for Screenshot
Mark the requests in the result list and import them into the personal queue.
Note:
The procedure described here can only be used for the second system copy after introducing the Transport Management, as all import information since the last system copy is required. This information is only available if the Transport Management has been in use since that time, recording all import activities.
For complete import information, ensure the import scanner /RTC/TM_IMPORT_SCANNER
is scheduled on all involved systems since the last system copy, covering relevant periods. This ensures all externally imported jobs (SAP TMS) are recorded. In both tracking options described above, the periods for the first and last runs of the import scanner can be read:
Placeholder for Screenshot
Jobs not imported by the Transport Management are marked with "E" in the "WF" column.
2. Step: Matching of the import database
After all import post-processings are complete, call the option "After a system copy -> Matching: Import database (target system)" in the TM tools:
Placeholder for Screenshot
This operation transfers all import information from the production system to the quality assurance system up to the backup creation. For the period between the backup creation on P and its application to Q, all import information on the quality assurance system is deleted.
Placeholder for Screenshot
Note:
The sub-item "Adjustment of Import database (target system)" is also found in other categories in the TM tools. It is crucial to use this sub-item in the "After system copy" category, as different actions are triggered in other categories, potentially causing data loss.
After this operation, the import database is matched. All import information necessary for step 1 is irrevocably deleted. Therefore, ensure this step is only performed when no further post-transports are required.
Post-Processings:
Re-schedule import jobs for the Q-system and the import scanner.
If urgent transports need to be imported into the production system during the Q-system's downtime, use the defined workflow. Ensure that the system queues are generated at least once before the requests leave the Q-transport level "Current." This records the requests for later Q-import. After completing the post-processings described above, start the system queue for the Q-system to process these "emergency transports."