Scribd
Upload
478 views2 pages

Step by Step Guide For Client Export Import

This document provides a step-by-step guide for copying a client from a source system to a target system using the client export-import method. The key steps are to prepare by creating a system message, locking users, and ensuring no background jobs or errors exist in the source. Pre-requisites include checking space, authorizations, and that the systems are the same release. The procedure is to log on to the source, select a client profile for export, configure it to export to the target, import the transport requests in the target, and start the import which will automatically import any related requests.

Uploaded by

Yasir Ammar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
478 views2 pages

Step by Step Guide For Client Export Import

This document provides a step-by-step guide for copying a client from a source system to a target system using the client export-import method. The key steps are to prepare by creating a system message, locking users, and ensuring no background jobs or errors exist in the source. Pre-requisites include checking space, authorizations, and that the systems are the same release. The procedure is to log on to the source, select a client profile for export, configure it to export to the target, import the transport requests in the target, and start the import which will automatically import any related requests.

Uploaded by

Yasir Ammar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Step by Step guide for client export import

Steps for client copy using client export-import method


  

PREPARATION

1. System message: To keep the users informed about the client copy and unavailability of
systems, please create a system message in the SAP system (SM02).
2. You must neither work in the source nor in the target client.

So, Lock Users: Only administrator user IDs should be active and all other SAP user IDs should be
locked so that no user intervention can occur at the time of client copy in the source system (SU01).

1. There must not be any background job running or in released status in the SAP system
(SM37).
2. Check for TMS configuration and ensure there are no updated errors in SM13 of the
source client.
3. Make sure that there is enough space in target system tablespaces and Common Transport
directory.
4. To keep the User Master Records and Authorization Profiles same after client copy, take the
export of SAP_USER profile.

PRE-REQUISITES

1. For performing a client copy we must check the size of the client and the availability of space
in the target system for copying that client.
2. Authorization required to copy client, to export and import client as well as to perform the
steps related to transport management system must be assigned to the SAP user performing
the Sap client copy as per SAP recommendations.
3. Source SAP system and Target SAP system should be the same release.
4. Transport tools like tp and R3trans should be working accurately in the SAP systems.
5. No SAP users should be able to log-in to the source as well as target SAP system so that
there is no inconsistency in the SAP system.

PROCEDURE

Log on to source system - source client and make sure that all above steps have been performed.
Then go to tcode SCC8 for Export. Select a client profile according to data to be copied as a
Transport request. Mention the target system into which the client should be copied. Configure this
as a background or dialogue process.
According to the client profile selected and the data available, a maximum of 3 transport requests
will be created and automatically exported to the target system mentioned. The requests are like

<sid>KO<No> - For cross-client data

<sid>KT<No> - For client-specific data

<sid>KX<No> - For client-specific texts

Once the above TRs got created all of them were automatically released and exported to a target
system. This can be checked in SE01 or SCC3.

IMPORT

Log on to the target system(client) and execute the STMS tcode.

STMS > import overview > refresh the buffer to find exported requests →import Queue of the target.

The client → starts import.

In case 3 transport requests are created in export any one of the TR is started then the rest TRs also
get imported into the target client automatically.

You might also like