Client Administration
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
You can use transaction code SCC3 to view the client export and obtained detail information about it
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
There are two ways to perform a system copy
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
- client - enter a client number for example 410 and a name for example Datadisk Client
- city - enter your location
- std currency - enter a default currency for the client (for example USD)
- client role - select an entry from the drop down list for example customizing, it is used for documentation purposes
- changes and transports - select an option this it to do with changes in your system and if you want them recorded for transportation
- cross-client object - allows you to use objects across different clients, if your objects are client dependant then disallow it.
- protection - protect the client from being copied over or taking a client copy, for example in production this would be locked down specially if you have sensitive data
- catt and ecatt - allows or disallows you to run test case scripts
- restriction - displays if a client copy is taking place or if you want to prevent an upgrade to the client.
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
- Client export
- Client import
- Import post-processing
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
| Client Independent Objects (cross-client data) |
|
| Client Dependant Objects (client specific data) |
|
| SAP Scripts (texts and forms) |
|
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
- Transferring data from the production system into a test or QA system to make large datasets available for testing
- Preparing for an upgrade, the replica should be the same as the production
- Synchronizing the configuration in the test and development system with the production system
There are two ways to perform a system copy
- A database copy of the production system
- A client copy of the production client
Client Administration
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
You can use transaction code SCC3 to view the client export and obtained detail information about it
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
There are two ways to perform a system copy
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
- client - enter a client number for example 410 and a name for example Datadisk Client
- city - enter your location
- std currency - enter a default currency for the client (for example USD)
- client role - select an entry from the drop down list for example customizing, it is used for documentation purposes
- changes and transports - select an option this it to do with changes in your system and if you want them recorded for transportation
- cross-client object - allows you to use objects across different clients, if your objects are client dependant then disallow it.
- protection - protect the client from being copied over or taking a client copy, for example in production this would be locked down specially if you have sensitive data
- catt and ecatt - allows or disallows you to run test case scripts
- restriction - displays if a client copy is taking place or if you want to prevent an upgrade to the client.
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
- Client export
- Client import
- Import post-processing
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
| Client Independent Objects (cross-client data) |
|
| Client Dependant Objects (client specific data) |
|
| SAP Scripts (texts and forms) |
|
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
- Transferring data from the production system into a test or QA system to make large datasets available for testing
- Preparing for an upgrade, the replica should be the same as the production
- Synchronizing the configuration in the test and development system with the production system
There are two ways to perform a system copy
- A database copy of the production system
- A client copy of the production client
Client Administration
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
You can use transaction code SCC3 to view the client export and obtained detail information about it
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
There are two ways to perform a system copy
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
- client - enter a client number for example 410 and a name for example Datadisk Client
- city - enter your location
- std currency - enter a default currency for the client (for example USD)
- client role - select an entry from the drop down list for example customizing, it is used for documentation purposes
- changes and transports - select an option this it to do with changes in your system and if you want them recorded for transportation
- cross-client object - allows you to use objects across different clients, if your objects are client dependant then disallow it.
- protection - protect the client from being copied over or taking a client copy, for example in production this would be locked down specially if you have sensitive data
- catt and ecatt - allows or disallows you to run test case scripts
- restriction - displays if a client copy is taking place or if you want to prevent an upgrade to the client.
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
- Client export
- Client import
- Import post-processing
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
| Client Independent Objects (cross-client data) |
|
| Client Dependant Objects (client specific data) |
|
| SAP Scripts (texts and forms) |
|
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
- Transferring data from the production system into a test or QA system to make large datasets available for testing
- Preparing for an upgrade, the replica should be the same as the production
- Synchronizing the configuration in the test and development system with the production system
There are two ways to perform a system copy
- A database copy of the production system
- A client copy of the production client
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
You can use transaction code SCC3 to view the client export and obtained detail information about it
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
There are two ways to perform a system copy
Client Creation
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
- client - enter a client number for example 410 and a name for example Datadisk Client
- city - enter your location
- std currency - enter a default currency for the client (for example USD)
- client role - select an entry from the drop down list for example customizing, it is used for documentation purposes
- changes and transports - select an option this it to do with changes in your system and if you want them recorded for transportation
- cross-client object - allows you to use objects across different clients, if your objects are client dependant then disallow it.
- protection - protect the client from being copied over or taking a client copy, for example in production this would be locked down specially if you have sensitive data
- catt and ecatt - allows or disallows you to run test case scripts
- restriction - displays if a client copy is taking place or if you want to prevent an upgrade to the client.
Client Administration
In this section will will cover client creation, client copy and client transports, if you need a refresher on what a client is then see the SAP Administration client section.
We use transaction code SCC4 to create a new client, if you select the change-display button you will see a new entries button, select this to create a new client, if you get an error stating that the system is not modifiable then use transaction code SE06 (or SE03 set system change option) to change the status to modifiable (also see my Security Administration section)
Before we get to the new client screen SAP will inform you that the table is cross-client (see below for details on cross-client)
The new client screen looks like below, the fields are describe below
- client - enter a client number for example 410 and a name for example Datadisk Client
- city - enter your location
- std currency - enter a default currency for the client (for example USD)
- client role - select an entry from the drop down list for example customizing, it is used for documentation purposes
- changes and transports - select an option this it to do with changes in your system and if you want them recorded for transportation
- cross-client object - allows you to use objects across different clients, if your objects are client dependant then disallow it.
- protection - protect the client from being copied over or taking a client copy, for example in production this would be locked down specially if you have sensitive data
- catt and ecatt - allows or disallows you to run test case scripts
- restriction - displays if a client copy is taking place or if you want to prevent an upgrade to the client.
In a production environment you would lock down the client, where as in a development or testing environment you may be be more relaxed (this is know as opening up a client). The below screenshot is an already created client
Once the client has been created you will see in the main client configuration screen
Although we have created a new client it contains no customizing master or application data, you need to fill the client with data using a client copy, as there is no user master data you have to login as SAP* using the password PASS. You can confirm the client when you login by select the informational box in the bottom right hand corner of the SAP Easy Access window, you should see something like below, the screenshot shows that I am logged in client 410 as user SAP*, sometimes you may have a problem logging using the SAP* account check that the profile parameter login/no_automatic_user_sapstar is set to "0" and restart the instance if you had to change the parameter.
Client Copy
You can use the client function to copy or transport client-specific customizing settings or data from a source client into a target client. This saves you time having to rekey customizing information in again, the client copy does not copy ABAP programs or table structures, you use copy profiles to determine the scope of the data copy which means that you don't need to copy all of the data in a client.
The target client may be or not be in the same system, if it is in the same system this is known as a local client copy, cross-system copies can be executed either as a remote client copy (using a RFC connection) or as a client transport using the TMS.
Be prepared for a copy to take several or more hours (even up to a day for very large clients) to complete, you may have to adjust the system parameter max_wp_run_time for large client copies, this all depends on the dataset and the performance of your system. You should stop all users and backgrounds jobs when performing a copy otherwise there may be inconsistent data in the target client when the copy has finished. It is possible to perform test runs before actually copying the client, this will determine if you have enough resources (memory, disk space, etc) to perform the copy, I will demonstrate this below.
Lets perform a local client copy to our newly created client (410), we use transaction code SCCL whilst logged into the new client, the client copy screen is pretty basic, I will talk about the profile in a moment, the description is populated when you select the profile, you then chose what client you wish to copy and notice the test run button, I always select this when I don't know a client well it will also make sure that you have the permissions to perform a client copy, I will discuss this in more detail in a moment, you can also determine the client size using transaction code SCCL or using report RSSPACECHECK (transaction code SE38)
The profile determines the data that you wish to copy, for example SAP_ALL profile would have the most to copy, I have a screenshot below detailing what each profile copies, try to use the least mount of data otherwise the copy process will take a long time to complete and you may copy data that is not needed
You can either run the client in the background or you can run it immediately, I will leave that up to you to decide, you may see the below informational message appear on your screen select the green tick to continue
Before the copy begins you get a chance to backout, confirm the details and then select continue, if you had selected customizing you would have the option to select what data you wanted copied, in my case it is grayed, also notice in the copy mode section the test mode is selected
Now because we select the test check box, we have an option to confirm that we have the resources to complete a client copy, you have two choices, read the screenshot which explains what choices you have, I generally select the resource check to confirm that we have enough resources.
If you are happy that you have enough resources then repeat the above but do not select the test run check box. If you started the client immediately you can view the processing in the bottom left hand corner, you will see the checks that are being performed
After a while you will see a time dial appear, the complete hand will move around as the copy progresses, this will give to an idea on how long the copy will take
After the client copy has finished you can check the current or previous client copies using transaction code SCC3 which displays the client copy log files, this is handy if you decided to run the client copy in the background.
If you try to run another client on the local system or a remote system (if you are perform a remote copy) while an existing copy is taking place, SAP will inform you that another client copy is running.
A remote client copy is very similar to a local client copy except that you state the remote SAP system, again you can run a test run just to check. Use transaction code SCC9 to perform a remote client copy, the screenshot below is the screen, the only thing that you require is an RFC destination to be configured which I will cover in another section.
If you ever get any errors regarding unable to write to the log directory then check instance parameters DIR_TRANS and DIR_EPS_ROOT and make sure that they point to your transport directory.
Client Transport
A client transport is the second way to copy a client across system, this involves three steps
- Client export
- Client import
- Import post-processing
Lets perform a complete example so that you understand the whole process, however I will select a small profile, just user data without authorization profiles and roles data (lets keep it simple and quick) thus we will use the profile SAP_UONL, you start by logging onto the system that you want to export (in my case client 800), the transaction code SCC8 allows us to create the export, select SAP_UONL as the profile and C11 as the target system as we will import into the same system but a different client, if you are planning to import into a different system then select that system.
We then get a verification screen, notice the first line as we see this verification screen alot, we can tell that this is a client export
The export displays a summary screen, detailing the transports and other import information, please read this to confirm that you are happy, remember the transport number C11K?0005, we will see this later
Once the export has finished, you will see between 3-6 files that have been created in /usr/sap/trans/cofile and /usr/sap/trans/data directories (depends on the profile you selected for the client export), these are the files that can be transported to another SAP system and then imported, in our case we will leave them were they are and use them.
| Client Independent Objects (cross-client data) |
|
| Client Dependant Objects (client specific data) |
|
| SAP Scripts (texts and forms) |
|
If you double-click on the client export, you get details on the mode, the profile used and its export status (successful in our case)
Again we can drill down further by double-clicking again, also you can get the command information that was run in the background by using the file log and main export log button, here you can see if there were any errors or warning during the export.
Now lets see if we can see the new transports, you can do this for both systems just to verify they can be seen (remember to copy the files to the new system), in our case we will logout of client 800 and login to client 410, we then use transaction code STMS, then select the import overview button (lorry icon)
Then we select the C11 system by double-clicking it
At first you may not see anything, just select the refresh button (two blue arrows) and hopefully you will see the transport, in our case its C11KT00005 which is one of the transports we saw above
If you double-click on it you can get more detailed information to confirm its the one we exported, notice the profile SAP_UONL, C11 system and client 800, it sure looks like it.
Lets import the transport, highlight the transport and select request -> import you should see the below screen, enter the target client, (in our case 410) also notice the informational message at the bottom, we must run transaction code SCC7 to finish off the import, this is important as its the post-processing on the import
The system will ask us to authenticate, use a user that allows imports, as this is a new client we only have SAP*
Again an informational message will appear
Now if you refresh the screen you will notice that the icon at the end of line has changed to a lorry, which means import running, so far so good
Keep hitting the refresh button periodically and eventually the import will be complete as the icon changes to a green tick
Notice the yellow triangle, if you double-click you can see why there were any problems, in our case we had some warnings, check these out to make sure you are still happy with the import
Now lets finish off the import and perform the post-processing using transaction code SCC7, there is nothing to fill in here, either start as a background process or start immediately
Again we get the verification screen, however notice the top line now its a post-processing
Once every thing has finished you will see an informational message at the bottom left-hand screen
Again we can use transaction code SCC3 to view the details, we can see the import was successful, it used the SAP_ONL profile and was taken from client 800.
Double-clicking gives us more information, and you have various buttons to get even more detailed information.
By using transaction code SU01 we can see that indeed the users have been imported into client 410
Deleting Clients
Deleting a client is a ether a one or two step process, first you login to the client and use transaction code SCC5, select the client to be deleted, if you select the delete entry from T000 then you don't need to perform the next step (using transaction code SCC4).
The same verification screen appears just to make sure you are certain that you want to delete the client, notice the top line this time its a delete
If you did not select the delete entry from T000 above then you use transaction code SCC4 to complete the removal of the client. Following the deletion all the client configuration and data is now gone.
System Copy
There are a number of reason to take a system copy
- Transferring data from the production system into a test or QA system to make large datasets available for testing
- Preparing for an upgrade, the replica should be the same as the production
- Synchronizing the configuration in the test and development system with the production system
There are two ways to perform a system copy
- A database copy of the production system
- A client copy of the production client
No comments:
Post a Comment