SAP Export & Import Client Copy Steps

Share this article :

In source client

1. Run transaction code SCC8. Fill in the Selected Profile and the Target System.

2. Choose Schedule as Background Job. Set as Immediately and click Schedule Job.

3. Click to continue.

4. 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.

• <sid>KO<no> : cross-client data
• <sid>KT<no> : client-specific data
• <sid>KX<no> : texts and forms

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>.

5. Ignore this and continue. Just select the right icon.

6. Background job for SCC8 was successfully scheduled. You can refer the log in transaction code SCC3.

In Target Client

1. Run Transaction code SCC3. Choose Exports.

2. Go to transaction code STMS. Highlight the transport request for client exports and choose the lorry icon to import.

3. Choose Import to continue. 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.

4. After an import, run the client import post processing in transaction code SCC7. You need to perform postprocessing activities to adapt the runtime environment to the current state of the data. Client import post processing is always necessary and must be performed in the target client after the import of the transport requests.

• 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.
• Do not use the same client as the source for several copies or client transports at the same time.
• Ensure that the data export has finished before another client copy or client transport, by examining the export log of the transport request.

Related posts

Automatically Delete SAP User Spool Request
Change SAP Database User Password with BRTOOLS
SM59: User password invalid for identifier /RFC/ (see long text)
PFCG: Assign Authorization Object into Role

    Great Post.

© 2017 ITsiti. All Rights Reserved
Powered by KEEM