on 02-14-2008 11:00 AM
Dear All,
I need to perform the client export/import in different systems (i.e which are not configure in the same land scape).
i.e i need to export a client data from developement system to our ides server(these systems are not in same land scape).
For this please let me know how can i perform the client export/import in different systems.
Thanks & Regards,
Reddy V
Hi Vreddy,
Before doing client export and client import we need to follow up some important pre-steps.
like 1. we need to check whethere there are any BG jobs are running in the soure system.
2. we need to check no users must log in to source sys.
3.just lock all the users expect BASIS Users
4.check there is enough space in TRANS folder.
and follows the same like go to SCC8 and export and move the TR to respective systems and import using SCC7 and do post installation steps.
please drop points if you find any way to my answer.
With Regards,
Prashanth Gali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Resolved the issue
Regards
Reddy V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Srividya is right .
The most important pre requisite before you do client copy across systems is that you need to have the
1) SP LEVELS same,
2) System release level,
3) Transport request created and imported in both systems should be exactly same
4) any addon , IS components installed on one source should also be present in target.
How you can check this is by tcode SCC9. in SCC9 there is a options RFC system comparison which will tell if your copy will be successful.
You create an RFC destination between your source ,target system, and you can run RFC system comparison.
Thanks
Prasanna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can perform the transport of the client by following 3 steps:
1. Export the client from the source system using TA SCC8. This will create transport requests at the OS level.
2. Import the transport requests in the target system using STMS --> Import Queue Overview --> Extras --> Add
3. Client import post processing in TA SCC7.
You can find the details at:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/69/c24c0f4ba111d189750000e8322d00/frameset.htm
Hope this helps.
Best Regards,
Srividya.R
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To add to this message i am also in the mid of client export process,
I have executed SCC8 , it has generated two files in data and co-files folder but the size of the folder is around 28 mb in data files for those requests, and the logs says EXPORTED SUCCESSFULLY.
should i execute the import process....?
Regards,
SM.
Hi Srividya,
Thank you for your valuable information and sorry for the delay response.
Yesterday I exported the client using T-code SCC8 in our quality system. Export was completed sucessfully in Quality system and It was generated two transport requests.
Then I have added these transport requests to cofiles and datafiles in the target system and i added this requests in import queue using stme t-code and performed the import process. But since last 30 hours it in process.
Please let me know what should i check to know the import process.
Regards,
Reddy V
Hi Srividya,
Request SIDKX000008 imported sucessfully with return code 0. But SIDKT00008 is imported with return code 8.
Please note the log for the request SIDKT00008
Main import
Transport request : UBQKT00008
System : IDE
tp path : tp
Version and release: 370.00.01 700
Table /OSP/T_BM_CTX is not in nametab
Table /OSP/T_BM_CTXT is not in nametab
Table /OSP/T_BM_RLV is not in nametab
Table /OSP/T_BM_RLVT is not in nametab
Table /OSP/T_CON_GRP is not in nametab
Table /OSP/T_CON_GRP_T is not in nametab
Table /OSP/T_CON_VAR is not in nametab
Table /OSP/T_CON_VAR_T is not in nametab
Table /OSP/T_GD_SETNG is not in nametab
Table /OSP/T_GD_SETNGT is not in nametab
Table /OSP/T_GD_VALUE is not in nametab
Table /OSP/T_GD_VALUET is not in nametab
Table /OSP/T_MDR_APPL is not in nametab
Table /OSP/T_MDR_SCN is not in nametab
Table /OSP/T_MDR_SETOP is not in nametab
Table /OSP/T_MDR_SETVL is not in nametab
Table /OSP/T_RAUI_CHR is not in nametab
Table /OSP/T_RAUI_CHRT is not in nametab
Table /OSP/T_RAUI_CPVL is not in nametab
Table /OSP/T_RAUI_CPVT is not in nametab
Table /OSP/T_RAUI_CSER is not in nametab
Table /OSP/T_RAUI_CSET is not in nametab
Table /OSP/T_RAUI_CSTT is not in nametab
Table /OSP/T_RAUI_RFC is not in nametab
Table /OSP/T_RAUI_RFCT is not in nametab
Table /OSP/T_RAUI_TPBH is not in nametab
Table /OSP/T_RAUI_TPBT is not in nametab
Table /OSP/T_RAUI_TRG is not in nametab
Table /OSP/T_RAUI_TRGT is not in nametab
Table /OSP/T_VAR_MAP is not in nametab
Table AGR_HIER_BOR is not in nametab
Table CCRCC_CHCK_ON is not in nametab
Table CCRCC_DET is not in nametab ETC..............
Table TMVMTT is not in nametab
Main import
End date and time : 20080428204921
Ended with return code: ===> 8 <===
######################################
Please help me how to fix this issue.
Regards,
Reddy V.
Hello,
Did you import these two requests seperately ?
If you import them together, the system will take care of such issues.
Check the importing section:
http://help.sap.com/saphelp_47x200/helpdata/en/69/c24c824ba111d189750000e8322d00/frameset.htm
Regards,
Siddhesh
Hi,
As Siddhesh says, the problem will be solved if you import the two together.
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.
Best Regards,
Srividya.R
Hi Srividya,
I imported the transport request requests properly in the target system. But these transport requests are imported with return code 8.
Please confirm these error belongs to supportpacks.Earlier i checked the support packs these are diff. in source system and Target system.
Regards,
Reddy V.
Hi Reddy,
Usually the client imports are done when the source and target systems are at same SP levels. If they are at different levels, the structure, field lengths and other attributes of some objects may vary and result in an error (which seems to be the case with you as the logs mention the tables where the error has occurred.)
Aligning the support packages before you import the client is advisable.
Best Regards,
Srividya.R
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.