Client Copy v/s Transport

Hi ,
I want to understand the difference between Client-Copy and Transport.
After I have developed reports in Dev Box , which is the best option out of both ?
Should one do a client copy from Dev to QA or Transport Objects ?
What are typical Advantages and Drawbacks of both?
Can someone share on this ?
Thanks
Sajid

Hi,
you should transport your objects from DEV to QA and PROD.
Client copy is typically used when you want to have your DEV and QA system look like your prodcution system. You then make a client copy from PROD to DEV and QA in order to "clean up" the systems.
Kind regards
/martin

Similar Messages

CLIENT COPY- HOW TO Transport client dependent objects

Hi
We are planning to do Client copy and after reading forums it seems that some objects doesnot get copied over like
Transfer rule
DataSource
Transfer Structure
InfoPackage
Process chain
Process chain variants (PSA processes)
now my understanding is i have to transport this object from System A to B
Release the transport and do the system copy.
Question 1-- what steps i need to make sure while creating a transport.
Q2 Should i click on the object in Transport connection and select (Transport all below, add/remove additional object)
(BECAUSE if i dont do that the boxes TRANSPORT is visible and no check box is in there )
q3 - What should be grouping ? (in dataflow before/afterwards, save for system copy etc. ?? )
q4 What should be Collection Mode - Collect automatically or start manual collection
q5 what should be selected in PACKAGE
q6 i can find Process chains and not PROCESS VARIANTS
q7 i can find Transfer rules but i cannot find TRANSFER STRUCTURE
i just want to make sure how to do these for all objects???
as i have to release the transport before system closes out

thanks
but i still need to create transport and i want to know what options to choose while creating a transport request...
so
1 thing is clear i have to choose SAVE FOR SYSTEM COPY
but following question i still need to do manually and need to know what to select
Q2 Should i click on the object in Transport connection and select (Transport all below, add/remove additional object)
(BECAUSE if i dont do that the boxes TRANSPORT is visible and no check box is in there )
q4 What should be Collection Mode - Collect automatically or start manual collection
q5 what should be selected in PACKAGE
q6 i can find Process chains and not PROCESS VARIANTS while selecting process chains in transport
q7 i can find Transfer rules but i cannot find TRANSFER STRUCTURE

Client copy,customer systems

The delivery class controls the transport of table data when installing or upgrading, in a client copy and when transporting between customer systems. The delivery class is also used in the extended table maintenance. what is client copy and customer systems?

2 possibilities:
client export/import: tcode SCC8 (then important transport with STMS)
remote client copy: SCC9 (after creating RFC connection through SM59)
all docs are available in help.sap.com

Inconsistant transport requests after local client copy

Dear experts,
our IT department just made a local client copy with profile SAP_ALL, by which all the transport requests had been copied, too, including quite a lot of workbench and customizing orders in status changeable. I'm supposed to do some basic setup and cleanup in the new client, but I'm confronted with problems like objects being locked in orders/requests that cannot be changed in the new client, as they belong to the original source client.
How can I get rid of those inconsistencies? I'd preferred the new client without transports and without locked objects. Is it really necessary that I clean up this mess manually? Would it have been better to clean this up before the client copy? Or could we just do the client copy with another profile in order to avoid those problems?
Thanks for your appreciated help
Andreas

Hello,
Transports are NEVER part of a client copy.
In fact all the data of your transports is stored in tables that are client independent (E07* tables).
This means that you can view (not edit) always all transports from all clients in a specific system.
When you want to edit or release a transport the source client is important (in which client was the transport originally created).
This is stored in table E070C for all transports and can not be overruled.
So I recommend that you don't clean anything related to transports after a client copy because this will also impact the other clients !
Success.
Wim

Transport Request number missing after Remote client copy

Hi,
I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
Thanks
Jyothish

> I have done a remote client copy with SAP_ALL .but after completing client copy i can find transport request numbers are not showing (SE10,SE09) for all the functional consultants. Plese help me to solve this issue, suggest me any solution
If you did client specific customzing in those they are of course not found.
Markus

Advantages and Dsadvantages of Remote Client Copy over Client Transport...

Can anybody explain the Advantages and Dsadvantages of Remote Client Copy over Client Transport...
Thanks in Advance

Advantages of Remote client copy over client transport
1. Client-specific data as well as cross-client customizing can be copied to the target client, this is not the same in client transport.
2. The prerequisites for performing a remote client copy are that an RFC connection has to exist whereas client transport do not need RFC connection
3. The copy can be performed in parallel with several processes.
4. Remote client copy automatically performs a consistency check on the tables being copied,for client transport performance check need to be done.
5. A remote client copy is easy to use and does not require file system space on
operating system level whereas Client transport require lot of space as files are created at OS level.
Disadv
1. A remote client copy does not create a file at the operating system level,
so there is no hard copy of the client to be copied. Therefore, the same,
identical client copy cannot be duplicated at a later time.Client transport creates import and export files at Os levels
2. To be able to copy all data during the client copy, the structures of all copied
tables in both systems must be identical.
3. An automatic repository consistency check is performed in Remote client copy and if inconsistencies are detected, the client copy is terminated and an error message is displayed.
4. You cannot copy the remote client data and use it whereas in client transport you can copy the files in a cd (like import files, export files)
Also see notes
47502
557132
Rakesh

What is the defferent between client copy and client transport

what is the defferent between client copy and client transport?
give me the steps that how to make a applications data copy from production to QAS.
thanks
priyan

Hi,
what is the defferent between client copy and client transport?You better google it..!
here is the result..
http://help.sap.com/printdocu/core/print46c/en/data/pdf/bcctscco/bcctscco.pdf
Follow the standard procedure of System Copy from PRD => QAS :
Download guide as per your release:
http://service.sap.com/systemcopy
What is Systemcopy:
http://help.sap.com/saphelp_rc10/helpdata/en/a2/2f0c173a5e43d19585724239ff4de7/frameset.htm
Regards;

Logical System and Client copy

Hi Gurus ,
             I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
Selvan

Hi Manjula ,
              Below i mentioned the full detail about the error .
    RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.
The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection     or perform the following steps manually:     1. Create an RFC destination with the target ZK>source client of client         copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000
4. Start the client copy again.
Kindly advice me
selvan

Client Copy from BWP to BWT

I had a problem with my List Cube Transaction and for that reason, I had a look at the Infoprovider and also the Data Sources.
When tried to execute the infoproviders in LISTCUBE, the following messages are being displayed in BWT system:
1. Error reading the data of InfoProvider ZIP_RC_01
2. There is still no data source assigned to VirtualProvider ZIP_RC_01
But, when executed the same in BWD, then it is working fine.
I have checked the Data Sources in the R/3 Dev system and the DS has no problem. But, when I check the DS in the R/3 Prod (SS in BWT system), the following error message is displayed in the status bar:
"DataSource Z_IP_RC_DS_1 is not defined in the source system"
I thought, as the system says the Source system is not available, hence the problem in LISTCUBE and thought if we transport the DS again and then replicate in BW, then our problem would be resolved.
But, seems that even though the source system says "PRD300", if I look at SM59 it actually points to our QAS system. It says PRD300 because BWT is a copy down from BWP, and that's the source system we use - in other words the logical name is the same, but the actual servers are different.
In any case, the datasource is transported to our QAS enviroment.
So, once we do a client copy from Prod to Test, even the source systems get copied. If yes, then does it really affect in case of replications and transports???
I am really confused in this part...please explain.
Thanks & Regards

Hi,
It looks like the basis team, or whoever performed the Copy from production to QA box hasn't finished all the necessary Steps :
Main transaction to know:
SSC4 -> To create new client
SCCL -> Client copy within local system
SCC9 -> remote client copy
SCC3 -> display client copy log
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c4e4ba111d189750000e8322d00/content.htm
http://www.sap-basis-abap.com/bc/client-copy-from-production-to-quality-server-to.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci552257,00.html
Probably sounds like transaction BDLS hasn't been done.

Remote Client Copy - Ended in Erros

Hi Friends,
We recently performed a Remote client copy. What we normally do is we restore an latest offline backup of the Prod into an instance built exclusively for performing client copies into our QA system.
So if our actual PROD is ABC ( production ), the replica system is ADC. We restore latest backup onto ADC. Then from ADC we do a client copy onto AQC ( Quality ). We have n number of clients in AQC. When copying into a particular client we are facing this problem of 3 tables not being able to get copied. They are BKPF,LTAK and SOST. It happened twice that the Remote client ended with errors.
It says "Read or conversion error". The detailed error looks like below ;
TAB_COPY_R_CONTINUE LTAK WITH KEY:
I01 0000066362
Read or conversion error system: ADCT500 table: LTAK
ERROR: Internal error when inserting in table: LTAK
Internal error:      1,262,713         65,536 VERIFY_CNT
Process 00001 has copied data 25.02.2010 18:04:16
Read or conversion error system: ADC500 table: BKPF
Process 00002 has copied data 25.02.2010 19:09:00
Start: Recopy errors 25.02.2010 19:09:02
TAB_COPY_R_CONTINUE BKPF WITH KEY:
2100 5100019665 2008
Read or conversion error system: ADC500 table: BKPF
ERROR: Internal error when inserting in table: BKPF
Internal error:      6,948,636      1,777,664 VERIFY_CNT
Read or conversion error system: ADC500 table: LTAK
TAB_COPY_R_CONTINUE SOST WITH KEY:
OTF 34 000000019247
Read or conversion error system: ADC500 table: SOST
ERROR: Internal error when inserting in table: SOST
Internal error:      2,594,254        180,224 VERIFY_CNT
We approached SAP and they asked to do a DB reorg, run update statistics on both source and target and then re run the client copy.
Well DB reorg is a big activity so we just updated the statistics and ran again the "recopying errors" but still it is the same problem.
Can anybody please suggest something. Thank you.
regards
Vinod K

Hi Friends,
My apologies for coming back to you guys so late. I kind of was lost to find a solution for this.
Hi Sanujit,
The database logs dont indicate anything at all about this error or i am not able to locate them.
Rajesh,
There was a table comparison done for these tables properties in both source and target and everything looked ok and confirmed by the application.
At this moment we have anyway decided to go a fresh client copy again as lot of time has already passed and there would be differences in source and target tables.
But anyway could you please tell me the procedure to transport tables between source and target systems?
Hi Anil,
SAP iS ECC 6.0 and Oracle is 10.2.0.4.0
Thanks again for your time and pateince.
Regards
Vinod K

Remote client copy - scc9

Hi All
am performing remote client copy through scc9, created RFC & tested connection,
this server is not in the transport landscape.
when i execute scc9 and select profile SAP_ALL from target system (Production server) it runs for 5-7 mins and ends with message as "The client copy you started has terminated Tables cannot be converted.
should the users on Production server to be locked.
here is the logs in SCC3:
Client in Source System 500
Copy Type                 Remote copy
Profile                   SAP_ALL
Status                    Cancelled. See Log
User                      MODI_SUPER
Start on                  31.08.2009 / 16:47:19
Last Entry on             31.08.2009 / 16:50:00
Last Action:              RFC DDIC System Comparison
Statistics for this Run
- No. of Tables                   0 of     53521
- Copied Lines                    0
Warnings and Errors
Table Name      Component Package
A543                      Table Def. Missing Locally
A544                      Table Def. Missing Locally
A800                      Table Def. Missing Locally
A950                      Table Def. Missing Locally
A960                      Table Def. Missing Locally
A961                      Table Def. Missing Locally
ZCOM                      Table Def. Missing Locally
ZCSKS                     Field missing locally
ZEMAIL                    Table has Incompatible Fields
ZLR_DTL                   Field missing locally
ZMM_RGP_SLNO              Different Field Names
ZPM_CALIBRATION           Field missing locally
ZSDD                      Table not Convertible

Hi Ashun8
Please not be in rush as your SD & MM consultant need to testing some scenarior on sandbox.
As being Basis expert! you should have many comprisions including patch level on both server before initiate the Remote Client Copy.
I will prefer to do the system copy instead the Remote Client copy without downtime on PRD server.
Regards
Anwer Waseem
SAP NetWeaver Basis

Remote client copy fails.

Remote client copy fails.
The error message and info is given below. Help me to proceed.
Client copy
The client copy you started has terminated
Client Copy could not start because of Repository differences
Diagnosis
The table definitions differ between the systems. These differences mean that a copy of the data can cause a data loss and system inconsistencies. Differences occur when further developments were not transported or were copied between different maintenance levels.
Procedure
Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level.
It is observed that some tables are missing in the target system. How do I copy the table structures to the target system?
Thanks in advance

Hello Ashraf,
There are repository differences between you source and traget system.
If you want to get the list of repository differences, then run a RFC check before you execute remote clinet copy.
You have to then remove these repository differences before you start with the remote client copy.
to remove the difference you have to:
"Transport all the developments of table structures between the systems using the Transport Organizer and bring your system to the same development level" as mentioned above
I would recommend you to go for Export / Import rather than Remote client copy.
There are several advantages of export import method over remote clinet copy
Regards,
Ammey Kesarkar
<i>'Award points for useful info'</i>

Remote Client copy: Table does not exist in Nametab

Hi!
We executed a client copy between 2 SAP EHP4 systems.
The both systems are SAP ERP EHP4 systems, but with different Support package.
After the client copy we get the following errors:
Table ADDRC_DELI_SERV does not exist in Nametab
Table ADDRC_DELI_SERVT does not exist in Nametab
Question
How can we solve these errors, maybe to transport the tables?
Thank you!

Hi,
I would suggest to synchronize support pack levels between systems and copy it again. You could try to manually define those missing tables, but you need to create them under SAP namespace. later during upgrade you'll probably get some errors. Your issue is why it's not supported by SAP. Have a look at OSS note 70547 with detailed information about client transport.
Cheers

Remote client Copy

Dear All,
I am trying to do Remote client copy from Production to Dev system (two system landscape).Below is my hardware configuration of DEV and PRD system :
SAP - R/3 4.7(NU) , O/S - AIX , DB - ORACLE 9
PRD SYSTEM :
DATABASE Server
CPU - 2 (375 MHZ)
RAM - 3 GB
APPLICATION server
CPU - 2 (375 MHZ)
RAM - 2 GB
Database size of the Prd system is around 95 GB
DEV SYSTEM
CPU - 2 (375 MHZ)
RAM - 2 GB
I am doing test run first so that i can see if any errors come and also to estimate downtime of the PRD Server(as SAP recommends that no user should be login in target and source client while doing client copy).
From the last 24 hrs. it has just completed 2500 tables only. total tables are 27500 something(Non - Unicode system).Its running very slow....
Is there any way to improve the speed of Remote client copy ?
Else I am planing to do Export - Import of client.
Is there any way to estimate downtime of PRD Server while taking Export of client like In how much time Export of Source client will be completed....
Thanks & Regards,
Rohit

Hi Rajesh,
>
. Make sure that it has the same permissions as /usr/sap/trans directory.
>
Do I need to share that directory too
> by default it will be "/usr/sap/trans".
>
> After Export you should revert it to default...
>
I want to go for the process you suggested.
I have a question for this;
1. My DEV server is the domain controller and when I login to my PRD server and run the command df -k (it shows /usr/sap/trans directory mounted to DEV server).
So if I change the location trans directory through STMS (system overview DEV-->Transport tool) will it get updated for PRD or I need to restart the machine DEV or PRD. do I need to do anything else like mounting etc so that PRD server can access the same to save the export file when I will be taking the export of PRD client.
Regards
Rohit

Error while doing client copy

Hi Gurus,
i have to copy my all data(all modules master data) from client 300 to 900 within the system. i have created a client 900 thru scc4, then logged in 900 with user sap* and passwd "pass".then sccl while scheduling this in background...i am getting a error window which as follows..it says for creation of RFC..
RFC Destination for client copy in systems with financials basis (FINBASIS) component.
The system could not find any suitable RFC destination for processing the client 300.
This note also appears if an RFC destination was found but this does not work.
0 RFC destinations: FINBTR@RPDCLNT300
0 Error text: 900
Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection
or perform the following steps manually:
1. Create an RFC destination with the target ZK>source client of client
     copy (in this case 300).
2. Check whether the RFC destination works in transaction SM59.
     To avoid errors when assigning the password or the authorizations of
     the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:
     -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of
         the Financials Basis)
     -   Client: 300
4.     Start the client copy again.
what i have to do..?? in which cleint i have to create RFC ..??pls help me out in this situation.
Thanks & Regards,
ACS

SOLUTION:
Login to client 300
Go to sm59, create rfc connection type 3, give the rfc destination : FINBASIS_300
Logon and security--> give user id and password (of any user in client 300)
create any service type of user:(user should be a service user or communication user so as to avoid password lock situation) in 300
Check Test connection: test ---à authorization test.
Login in to new client: 900
Run the tcode: FINB_TR_DEST
Click on new entries:
Give the client: 300 and destination as FINBASIS_300 and save .
Run Tcode: sccl make client copy

Client Copy v/s Transport

Similar Messages

Maybe you are looking for