Start of Content Area

Procedure documentation Transporting Clients Between Systems  Locate the document in its SAP Library structure

 

The client copier can copy a client into another system, which can be on a different platform. You can change the client number.

You are no longer required to transport clients before you can copy them between systems. You can make a remote copy instead. You may still want to use the transport tool for the following reasons:

        There is no LAN connection.

        The data is to be buffered.

So the transport functionality is still supported.

Note

All languages in the source system are transported according to the settings of the transport tool.  All languages are selected by default.

Note

Codepage conversions are performed automatically, as far as technically possible.

Procedure

A client transport comprises three steps

1. Client export (SCC8)

...

       1.      Choose Administration System administration  Administration Client admin. Client transport Client export.

       2.      Select a copy profile.

Up to three transport requests are created, depending on the selected copy profile and the existing data. The transport request for texts is e.g. only created if the source client contains customer texts.

Transport

Description

<sid>KO<no>

cross-client data

<sid>KT<no>

client-specific data

<sid>KX<no>

texts and forms

The data export is performed automatically asynchronously. The output of the export includes the names of the transport requests that are to be imported.

Caution

The data export is asynchronous and still runs if SCC8 has already finished. Do not run any other client copy tool before the data export is finished. You can check the status of the export with the transaction SE01. Display the logs for the request <sid>KT<no>.

2. Import transport requests into the target client (STMS)

Choose one of the transport requests of the client transport in the Transport Management System (TMS). The other transport requests belonging to this client transport are then automatically added in the correct order.

Import these transport requests into the target client.

3. client import postprocessing (SCC7)

You need to perform postprocessing activities to adapt the runtime environment to the current state of the data.

Choose Administration System administration  Administration Client admin. Client transport Import editing.

Note

Client import postprocessing is always necessary and must be performed in the target client after the import of the transport requests.

Caution

It may be technically possible to start the transaction SCC7 in the source client, but you should not do so because it may cause data loss. You should protect the source client from overwriting by the client copy tools by choosing protection level 1 in transaction SCC4.

Caution

Do not use the same client as the source for several copies or client transports at the same time.

Caution

Ensure that the data export has finished before another client copy or client transport, by examining the export log of the transport request.

See also:

Copy profiles

Client Copy Data Types

See note 70547 for further information about the technical background and procedure of client transport.

 

End of Content Area