Copy a Client into a Stand Alone System

How to copy a client into a stand alone system?

The scenario is I have a 2 system landscape. I want to copy an existing client from DEV to a standalone system for some demo purposes.

There is an option for Client TRANSPORT which will help you perhaps:

A client transport differs from a remote client copy in that it does not use RFC. Like a remote client copy, however, a client transport is used to copy data between different R/3 Systems.

A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Second, the data is imported from the operating systemfiles into the target client.

To perform a client export, proceed as follows:

Log on to the source client. From the R/3 initial screen, choose:

*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport*(r) *Client Export*. Select the data to be copied using a profile.

Indicate the target system to which the client will be copied. (The target system must be defined in TMS as part of the transport domain.)

Begin the client export. As copying is a lengthy process, use scheduled background processing. The client export performed in the source system , exports the client data asynchronously bycalling the transport program tp at the operating system level. This export process will generate up to

3 data files at operating system level:

. RT<>; this file contains client-specific data

. RO<>; this file contains Cross-client data

. RX<>; this file contains SAPscript texts

Depending on the type of data selected through the client transport profile, the client copy command

files added to the buffer of the target system are

KO; this file is for cross-client data

KT; this file is for client-specific data

KX; this file is also for client-specific data

The client export change requests are not imported when an Import all takes place. Therefore, you must import these requests into the target client using TMS. You must import the data in the following order: first cross-client data, then client- specific data.

After the import process has completed, post-import activities are required possible for object generation steps. After completing the import, log on to the target client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport *(r) *ImportEditing*

To display client transport logs, use the Transport Organizer.During client transport, a Repository consistency check can be performed by clicking the RFC system check button in Transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary tables definitions missing in the target system is generated. This will help your recognize in advance formal problems that may occur during the import of the source data.