Client Tasks
*** SAP’s terms for the sending and receiving clients can be confusing. The “target” client is the client into which data is to be copied. The “source” client is the client which contains the data to be copied. Also, remember that all client copies are destructive and will delete all data before copying in the new data. The only exception is when the SAP_USER profile is used. In this case, only user master data is deleted from the target client before the new user master data is copied. ***
1. Create the target client if necessary.
2. Log on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for the user and “pass” for the password.
3. Go to transaction SCCL for Local Client Copy.
4. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select a profile that matches your needs. Use SAP_ALL or SAP_UAPP to copy all data except change documents, SAP_USER to copy only user master data, or one of the other SAP provided client copy profiles. Type the Source client and Source client user masters in the provided boxes. These two boxes should contain the same client number unless the data is to come from one client and the user master data from a different client. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue.
5. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button.
6. On the Verification popup, check that everything is correct and click the Continue button.
7. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. If the user is SAP* due to a new client, you may receive a date validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY, MM/DD/YYYY, YYYY.MM.DD, YYYY/MM/DD, and YYYY-MM-DD. Click the Save picture-icon.
8. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue.
9. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCCL transaction.
*** SAP’s terms for the sending and receiving clients can be confusing. The “target” client is the client into which data is to be copied. The “source” client is the client which contains the data to be copied. Also, remember that all client copies are destructive and will delete all data before copying in the new data. The only exception is when the SAP_USER profile is used. In this case, only user master data is deleted from the target client before the new user master data is copied. ***
1. Create the target client if necessary.
2. Log on to the target client in the appropriate SAP system. If the target client is new, use “SAP*” for the user and “pass” for the password.
3. Go to transaction SCC9 for Remote Client Copy.
4. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select a profile that matches your needs. Use SAP_ALL or SAP_UAPP to copy all data except change documents, SAP_USER to copy only user master data, or one of the other SAP provided client copy profiles. Since this is a client copy that uses data from a client in another SAP system (or remote client), a Source destination must be provided. This is a RFC connection pointing to a specific client in another SAP system. If there is no RFC connection to the client you wish to copy, you will need to create one. Otherwise, use the dropdown to select the remote source client. To test that your select Source destination RFC connection will work, click the RFC system check button. Once the proper remote source client has been selected, the System name and Source client boxes will fill automatically. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue.
5. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button.
6. On the Verification popup, check that everything is correct and click the Continue button.
7. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. If the user is SAP* due to a new client, you may receive a date validation error if you use the date format of MM-DD-YYYY. Try other variations such as DD.MM.YYYY, MM/DD/YYYY, YYYY.MM.DD, YYYY/MM/DD, and YYYY-MM-DD. Click the Save picture-icon.
8. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue.
9. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCC9 transaction.
Sometimes you need to retain the data residing in a client but refresh the roles, users, and other security components that have changed in DEV client 100. Since role changes don’t transport across the other clients maintained via Central User Administration, a user master client copy can be used on any client in the SAP landscape.
1. Log on to the appropriate client on the appropriate SAP system.
2. If the user master data is coming from a client within the same SAP system, go to transaction SCCL. If the user master data is to be copied from a client in another SAP system, go to transaction SCC9.
3. On the Client Copy – Copy a Client screen, use the Selected profile dropdown to select profile “SAP_USER”. Type in the same client for both the Source client and Source client user masters. This should be the client that contains the user master data you want to copy. If this is a user master copy that uses data from a client in another SAP system (or remote client), a Source destination must be provided. Once all information has been provided, click the Schedule as background job button. If you receive a Change documents will not be copied message in the bottom status bar, click the green √ next to the transaction command field at the very top of the screen to continue.
4. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button.
5. On the Verification popup, check that everything is correct and click the Continue button.
6. On the Start Time popup, if you want the client copy job submitted right away, click the Immediate button. To schedule the copy for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. Click the Save picture-icon.
7. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue.
8. You will receive a client copy confirmation message. You can monitor this copy by using transaction SCC3. You may now leave the SCCL or SCC9 transaction, whichever is appropriate.
1. Log on to any client in the “target” SAP system.
2. Go to transaction SCC3.
3. On the Client Copy/Transport Log Analysis screen, click the All clients button.
4. From the list of Client copy logs, double click on a client to view summary information for all client copies where this client was the target client. Double click on any of these summary lines to see statistics for a particular copy client job.
5. You may now leave the SCC3 transaction.
*** Before adding a new client you should first ask if it will be used in communications with other clients (Central User Administration, source for client copies, etc.) If so, the new client will need to be assigned a Logical System ID that is unique among all the SAP systems in the landscape. It is recommended that all new clients be assigned to a Logical System ID as soon as they are created. ***
1. Log on to any customizable client in the appropriate SAP system.
2. Go to transaction SCC4.
3. On the Display View “Clients”: Overview screen, click the pencil and glasses picture-icon to switch into change mode.
4. On the Display View “Clients”: Overview popup, click the green √ to dismiss the informational message.
5. On the Change View “Clients”: Overview screen, click the New Entries button.
6. On the New Entries: Details of Added Entries screen, fill in Client number and description and the City. Use the Logical system dropdown to assign a logical system ID to the client. Type “USD” in the Std currency box. Select a Client role from the client role dropdown (remember that there can only be one Productive client per SAP system). In the Changes and transports for client-specific objects, Client-independent object changes, Protection: Client copier and comparison tool, and Restrictions when starting CATT and eCATT sections, select the necessary restriction levels from the provided dropdowns. Once all information has been provided, click the Save picture-icon.
7. You will see a Data saved in the status bar at the bottom of the screen. You may now leave the SCC4 transaction.
1. Log on to the client to be deleted.
2. Go to transaction SCC5.
3. On the Delete Client screen, verify that you are deleting the correct client. If you also want the client deleted for T000 (ie the scc4 entry), put a √ in the □ to the left of Delete entry from T000 by clicking the □. Click the Background button.
4. On the Schedule Client Copy in Background screen, use the Background server dropdown to select the background server on which the job is to run. There should only be one server available in the dropdown. Click the Schedule job button.
5. On the Verification popup, check that everything is correct and click the Continue button.
6. On the Start Time popup, if you want the client delete job submitted right away, click the Immediate button. To schedule the delete for a later date and/or time, click the Date/Time button. In the Date/Time section, provide the Scheduled start Date and Time. If you are unsure as to the format of date and time, click on the top-most menu bar System → User profile → Own data. Click on the Defaults tab to see your default date format. Click the Save picture-icon.
7. On the Background Print Parameters popup, select an Output device from the dropdown. Click the green √ to continue.
8. You will receive a client copy confirmation message. Don’t panic, it looks like a client copy confirmation and says nothing about this being a delete job. You can monitor this copy by using transaction SCC3. You may now leave the SCC5 transaction.
When adding a new client to a SAP system, the information listed in
the SCC4 can be confusing. This is a brief explain of the
available client restrictions.
Client role:
The category indicates the role of the client in your R/3
system.
Possible roles are:
* Production client
* Test client
* Training client
* Demo client
* Customizing client
* SAP reference client
This field should be maintained by the customer for
Documentary purposes. Release 3.0 also ensures the following:
If there is a productive client in the target system, no client copy (remote copy) which also selects cross-client customizing objects may be imported into the system. If cross-client settings are imported, inconsistencies may occur in all clients.
In a productive client, customizing settings that can be maintained as "current settings" can be excluded from a client lock or transport links; this means current settings (e.g. exchange rates, posting periods) can always be maintained in a productive client without recording changes. SAP is planning to link further effective functionality to this flag, to enable adequate protection of a productive client in a system with further (test) clients.
Other settings for a client:
Change and transports for Client Dependent Objects
Changes without automatic recording – the client can be customized although the system will not generate change requests.
Automatic recoding of changes – the client can be customized and all changes are generated into change requests.
No changes allowed – no modifications can be made to the client – it is protected or locked. This is the usual configuration for a production client where customization should not be performed.
No transports allowed – changes are allowed but cannot be
transported.
Client-Independent Object Changes
Changes to repository and client-independent customizing allowed – no restrictions on this client for changes and development.
No changes to client-independent customizing objects - allows for development on repository objects but not client-independent customizing.
No changes to repository objects – lets users perform client-independent customizing but no development or modifications to repository objects.
No changes to repository and client-independent customizing objects – this setting prohibits any client-independent modifications and is common on Production systems.
A logical system gives a client a unique “name” which can be referenced by other clients within the SAP landscape. Once you have created a logical system, use the SCC4 transaction to assign the logical system to a client. Normally, you create the logical system before creating a client so that both start out together. Adding a logical system to a client after the client has been in existence and in use to a long time period could cause referencing problems between that client and the rest of the SAP systems.
1. Log on to any customizable client in the appropriate SAP system.
2. Go to transaction SALE.
3. On the Display IMG screen, expand the navigation tree like so:
Application Link Enabling (ALE)
Sending and Receving Systems
Logical Systems
Define Logical System
4. On the Display IMG screen, click the clock picture-icon to the
left of Define Logical System.
5. On the Display IMG popup, click the green √ button to dismiss
the informational message.
1. On the Change View “Logical Systems”: Overview screen, click the New Entries button.
2. On the New Entries: Overview of Added Entries screen, fill in the Log. System and Name. The logical system should match the naming convention already in place: LS<SID><Client Number>, such as “LSDEV100” for DEV Client 100. The description should be uniform as well such as “Logical System for DEV Client 100”. Click the Save picture-icon.
3. On the Prompt for Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench request popup which contains the generated change request number for this system change. Click the green √ to continue.
4. You will receive a Data saved message in the status bar at the bottom of the screen. You may now leave the SALE transaction.
