Multiclient Administration
This section summarizes the most important administration tasks necessary for the smooth operation of a multiclient system.
The following discussion is based on a system/client landscape in which n clients are set up in m systems, where m is kept as small as possible.
Preparing and Planning the Multiple Client System Landscape
When you distribute the n customers among the systems, it is a good idea to first categorize the customers according to their differing requirements, for example, by application solution.
Any decision you make must also be reversible, in case the basic conditions of your setup change. Relocating a complete client from one node in a system landscape to another entails the same amount of time and effort as migrating an installation from one host to another, but it can still be included in your calculations.
Setting Up the System Landscape
You can use the Transport Management System to help you map your scenario to a system/client landscape. To call the Transport Management System, choose 
Tools 
Administration Transports Transport Management System 
(STMS).
Setting Up the New Client
Set up the new client with a template client as a basis, using the functions of the client copy tool. To call these functions, choose Tools Administration Administration Client Administration Client Copy .
To prevent client settings from making changes to Repository objects and cross-client Customizing data, use the client maintenance functions. To call client maintenance, choose Tools Administration Administration Client Administration Client Maintenance (SCC4).
You can set each client so that it is locked for comparison tools; it cannot even be viewed by them. This lock applies regardless of the authorizations held by the user trying to access the data.
Note on assigning authorizations: We recommend that you do not assign the authorizations S_TABU_CLI and S_TABU_CMP, since they allow access to cross-client objects, or read access to other clients for data comparison. This is a redundant measure when you consider the lock protection mentioned above, however it does provide effective double security.
For more information, see BC Client Copy and Transport (BC-CTS-CCO).
Deleting a Client
You can use the client copy tools to delete an obsolete client.
Migrating a Client
You can use the client copy tools to migrate a client from system A to system B.
Change Management (Central Customizing Changes)
We recommend that you use Business Configuration Sets (BC Sets) to make necessary changes to all clients, and then distribute these changes.
Recovery
Make a normal recovery to another backup system, and then migrate the restored client from the backup system to the production system.
For more information, see Recovery Solution.
Comparing Clients
The SAP Web Application Server contains dedicated functions for comparing the Customizing settings of one client with another client or template client:
Cross-System Viewer Compares complex Customizing environments. To call the Cross-System Viewer, choose
Tools Accelerated SAP Customizing Customizing Cross-System Viewer (Transaction SCU0).
To compare individual tables or views, use the comparison function in the standard table maintenance transaction (SM30) or the view/table comparison transaction for any number of tables (SCMP).
Client-Specific Monitoring
The CCMS Monitoring tools also include some options for client-specific online monitoring of certain transactions and clients (see SAP Note 308048 
). These include the following:
Transaction load for each client (number of dialog steps)
Average response time for some or all transactions in a client
Client-specific monitoring:
Choose
Administration System Administration Monitor Performance Workload Analysis (ST03N). At the top left of the navigation screen, choose Expert (other options are Administrator and Service Engineer). Choose TOTAL under Today's Workload. Select a time period (such as this week). Then choose Analysis Views User and Settlement Statistics Settlement Statistics in the bottom left navigation screen.
You have a restricted database space analysis option for each client, as described in SAP Note 118823
.
Background Job Support
You use client-specific services for administering background jobs. You can start and restart background jobs from the logon client only. If you have sufficient administration authorizations you can also monitor jobs in other clients, however, you cannot modify them. No options for monitoring jobs started in other SAP Systems are supported.
The background job administration functions offer a range of interfaces. These interfaces are already used in the context of many SAP solutions. In addition, you can also choose from a range of established external administration tools offered by third-party vendors, which offer cross-client and cross-system job administration. You integrate these external solutions into SAP using the BC-XBP interface.
System Administration
Database and system maintenance functions are supported only at the physical system platform level, and not at the client level. This affects the following:
Database reorganization
Data backup
Release upgrades
Hardware and software maintenance
For more information, see