Home » Posts tagged 'scc9'
Tag Archives: scc9
Hope the below information helps.
HOW to do remote client copy ( SCC8 )
1. create the new client in the target system via tcode SCC4
2. log on to the traget client of the traget system with the user SAP* and password PASS
3. for the planned copy run, you must define the RFC connection between the R3 systems as the source client, if this has not already been
4. you should also protect the source client of the source system against changes during the copy. To do this, log on to the source system and
lock the source client : In scc4 (
change mode ), choose the option ” Currently locked Due to client Copy ”
5. you can start the copy in the target system. Execute tcode SCC9
6. using the profile, choose the data to be copied
7. choose the RFC connection. The source system and client are chosen automatically for the RFC connection
8. before the actual copy, test the RFC connection using the RFC system check. In addition to testing the connection, the R3 system releases
9. start the copy in background ( in test mode )
10. check the status of the copy procedure from the target system. You can do this at any time by choosing Client Administration..tcode SCC3
11. start the copy in background ( in final mode )
12. check the status of the copy procedure…SCC3
NOTE : with a remote client copy, only the table data is moved, not the table definitions. If user-specific, client-dependent tables were created in
the source client, they are not automatically copied to the target client, and an error may be caused. It is the responsibility of the user to create
the necessary tables in the target client manually via SE11.
HOW to do client transport : ( SCC9 )
prerequisites : the source and target system must have the same R3 release. The R3 system can not checked the R3 release since there is no
connection between the
1. create the target client in the target system via tcode SCC4
2. log on the source client in the source system with a user with transport authorization ( Not SAP* or DDIC )
3. using the client maintenance tool ( SCC4 ), lock the source client against changes
4. go to the client transport menu by choosing Tools > Administration > Administration > Client Transport > Client Export or transaction SCC9.
When you confirm your
selection, you are notified of which transport requests were created for this task.
KO – Client-independent
KT – client-dependent
KX – texts
5. check the logs created for the copy run via SCC3
To import the transports created into another R3 system :
1. copy the required files to the corresponding subdirectory of the local transport directory of the target system
2. on the operating system level, from the subdirectory bin of the local transport directory of the target system, execute the commands :
tp addtobuffer <request> <target system> client=<client>
tp import <request> <target system> client=<client>
3. the remaining file with the text elements requires different procedure. Log on to the target client of the target system and access the client
administration tool by selecting
Tools > Administration > Client Administration > Client Admin. Choose client Transport > Post-process Import. Select the request
<SID>KT<number of the request> and
execute it online or in background. This procedure copies and generates the client-dependent text elements.
Well, after learn how to do client export and client import, now its time to do hard wok. Doing remote client copy. For easy one, you can follow this procedure :
1. This is remote Client Copy(for that scc9). One system to Another System.
2. Create a RFC in Quality Server Client 300.
(Put target System is Production Server and Mention Client Also)
And then check Connection. – It should be OK.
3.Now run SCC9 from Quality Client 300.
Selected Profile: SAP_ALL
Source destinat: Choose created RFC.
Then please Tick first TEST RUN.
If it goes Successfull then Go for Next.
**** At the time of Client Copy No Other user shuld be login.