The utility report RSCLCCOP is identical to Transaction SCC1 and istherefore a supplement to the client copy. It can be used to transferindividual transport requests directly out fo the source client intothe the current client. The activities are listed in a clearlystructured copy log. For test purposes, you can start the report intest mode, which generates a log as in the production run but does notperform any database update.
If the number or size of the tables is very large, you are recommendedto start this report in the background.
If matchcodes are defined for the table, these are also taken intoaccount for the copy.
A special variant here is the selection option which allows you to listthe tables to be copied in a command file setup beforehand. This canalso be the command file of a correction or transport request, forexample, the one you used to recorded your Customizing activities (seethe 'Transport' options in your Customizing maintenance menu). You cancopy the table entries maintained in the Customizing client to anotherclient.Which requirements must be met? Copying is performed in the newly created client. This must already beknown to the system via the client table T000 and should already becompletely built up by a client copy.
A special variant allows you to select data via a predefined commandfile. This may be the one you used to record your Customizingactivities (see the 'Transport' option in your Customizing maintenancemenus). You can then copy the table entries maintained in theCustomizing client to another client.
The user performing the client copy must be authorized to maintaintables for all clients and the table CCCFLOW (see below). To avoidaccidental damage caused by inappropriate use of the report, theauthorization is checked against the authorization of the client copy.For more information see the documentation on Transaction SCC1. What is the purpose of the test run?
Database updates are not carried out during the test run, but the logicin the RSCLCCOP client copy is processed completely (without a DBupdate), whereby the complete table statistics are output. As describedabove, RSCLCCOP compares the contents of the source client with thoseof the target client.
With the help of the statistics resulting from this, you can determinethe tables whose contents were different from the source client andwere thus changed. Since the number of different entries is alsodisplayed, you are able to see to what extent the table has changed inthe current client.
Finally, a test run PRIOR to the production run enables you todetermine the additional storage requirement in the new client for thetables to be copied. The requirement is displayed in KB at the end ofthe log. |