0% found this document useful (0 votes)
59 views

Export: Client Export and Import Tasks Related To Ticket #105311

The document provides instructions for exporting and importing client data between two SAP systems as part of ticket #105311. It describes logging into the source and target systems, running export and import transactions, monitoring logs and space, and checking the status of the export and import activities. Post-import processing such as running transaction SCC1 is also mentioned.

Uploaded by

dev_erp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
59 views

Export: Client Export and Import Tasks Related To Ticket #105311

The document provides instructions for exporting and importing client data between two SAP systems as part of ticket #105311. It describes logging into the source and target systems, running export and import transactions, monitoring logs and space, and checking the status of the export and import activities. Post-import processing such as running transaction SCC1 is also mentioned.

Uploaded by

dev_erp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

Client export and import tasks related to ticket #105311

EXPORT
Log into the source system. In our case it is the production system.(PRD.300QAS.220) ) 2) 3) ') Login to the PRD.300 c!ient and run the transaction scc" #or c!ient e$port. Se!ect the proper pro#i!e.(eg .SAP%ALL) Se!ect the &arget system. In our case the target system is the Qua!ity QAS.220. A#ter that schedu!e it as the (ac)ground *o(.

A#ter the e$port got initiated monitor the #o!!o+ing. ) Login to the ,S !e-e! monitor the space #or !ogs. 2) In our case it is SQL Ser-er. at SQL /nterprise manager monitor the &ransactiona! !og space.

At #i!e system !e-e! chec) the e$port acti-ity in usr0sap0trans0tmp.

IMPORT
) 1or Import run the transaction S&2S in the source c!ient3 in our case it is PRD.300.

2) 4o to Import ,-er-ie+ to see the import Q. 3) Se!ect the system in +hich the import needs to (e done3 in out case it is QAS.

A#ter importing chec) the ,-er-ie+ o# transport !ogs.

) 1or adding to 5u##er in the menu se!ect ,ther re6uest Add.

2) 1or adding the &ransport re6uest to the import 6ueue the #o!!o+ing in#ormation are needed. &ransport re6uest Import Queue &arget 7!ient.

3) A#ter adding to the import Q3 se!ect the re6uest and import (Se!ect Import Re6uest icon 88Don9t se!ect the option Import A!! Re6uest (y mista)e).

Deletin a import re!"est#$ ) &o de!ete a import re6uest3 in the menu choose Re6uesDe!ete. 2) 5e#ore step chose the re6uest to (e de!eted. 3) I# not a(!e to de!ete the re6uest chec) #or tp.e$e(SAP Ser-ices) and r3trans.e$e(SAP Ser-ices) in the &as) manager sti!! running i# so )i!! the process and again try #or de!eting the Import re6uest.

Post Import Processin #$ ) Run the transaction scc:.

You might also like