Scribd
Upload
25 views1 page

400 Client Export

1. The document describes the process for exporting and importing client data between SAP systems. For export, up to 3 transport requests are created containing cross-client, client-specific, and client-specific text data. 2. For import, one of the transport requests is selected in the Transport Management System and the other requests are automatically selected. Post-processing must then be done using transaction SCC7. 3. If the transport requests are not yet in the import queue, they can be added using the tp command line utility or imported directly in the specified sequence using tp.

Uploaded by

Mayur Jain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
25 views1 page

400 Client Export

1. The document describes the process for exporting and importing client data between SAP systems. For export, up to 3 transport requests are created containing cross-client, client-specific, and client-specific text data. 2. For import, one of the transport requests is selected in the Transport Management System and the other requests are automatically selected. Post-processing must then be done using transaction SCC7. 3. If the transport requests are not yet in the import queue, they can be added using the tp command line utility or imported directly in the specified sequence using tp.

Uploaded by

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

SAP System

______________________________________________________________

New since Release 4.5: Import by TMS (see below)

Client export:
Up to 3 requests are created, depending on the data selected and available:
1.

"ECPKO00035" for transporting cross-client data, if you have selected this

2.

"ECPKT00035" for transporting client-specific data

3.

"ECPKX00035" for transporting client-specific texts, provided texts are available in this client

When the transport requests have been created successfully, the data is exported
asynchronously by starting the transport program tp at operating system level, and can take
several hours, depending on the data volume. The status of the export can be found using
either Transaction SCC3 or Transaction SE01 and specifying the transport request.
Wait until the data has been successfully exported before you start another client copy or transport
involving the source client.

Client import:
Choose one of the above-named requests to import, in the Transport Management System (transaction
STMS) import overview. Its other transport requests are then selected automatically.
You must post-process with the transaction SCC7 after the import.
When you call the transaction SCC7 in the target system an analysis procedure first determines the
associated transport request and displays its ID "ECPKT00035" with the parameters of this export. Verify
that the correct transport request was selected for import.

If the transport requests are not yet in the import queue in the target system, use the following commands:
./tp pf=TPPARAM addtobuffer <commfile name> <target sys id> u18
Example:
cd /usr/sap/trans/bin
./tp pf=TPPARAM addtobuffer "ECPKT00035" P11 u18
You can also still import the transport requests directly with the tp. Do so in the sequence
"ECPKO00035", "ECPKT00035", "ECPKX00035".
Example:
./tp pf=TPPARAM import "ECPKT00035" P11 client005 u18

______________________________________________________________
SAP AG

You might also like