Client Copy - Which source client 000 or 001?

I have a new SAP Netweaver 2004s SR1 ABAP+JAVA system with the following usage types:
SRM App
SRMLac
AS Java
AS ABAP
DI
MI
All the post-installation steps have been completed (including the CTC template configurations for DI and MI). The Java, DI, and MI have been configured against client 001. Now I want to create a new production client. The J2EE_ADMIN and users associated with DI and MI exist in client 001.
I want to create a new production client 010. Should I copy the users (SAP_USER) from client 001 and the customizing data (SAP_CUST) from client 000? Or, can I copy everything from client 001? There is a lot of conflicting information in the SAP Notes in regard to which source client to use.

You should not use a transport of copies for table USR02. Use client copy profile SAP_USER or SAP_UONL (without authorization profiles and roles).
And you should never copy customizing from client 001 to build up a new client. 001 happens to be a ordinary customer client which does not get supplied with changes SAP delivers after the release date. New SAP Netweaver 2004s installations use client 001 to file the user masters needed for the JAVA part. But this does not change the fact that client 001 is a customer client and should not be used as a template.
For local client copies you could use copy profile SAP_UCUS with source client 000 and source client user master 001 in one step. This has the same result as a client copy with SAP_CUST from 000 and SAP_UONL from 001 (i.e. thet authorization profiles and roles come from 000, when you need them from 001 you can either copy the missing individually or use SAP_ PROF in a separate step).

Similar Messages

Local Client Copy and Remote Client Copy in MS - SQL Database

Dear Gurus,
If i need to do the local client copy or remote client what is the procedure i should consider because i'm using MS-SQL 2005 database.Most of the thread using Oracle database.Can u give me the step by step or manual how to make it.
Thanks an advance.
/Shah

Hi.
SAP Help is a very good source for info -> [Link|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/69/c24c4e4ba111d189750000e8322d00/frameset.htm].
I suggest that you read the manual carefully. There are many tipps to improve performance (parallel processes) and tipps and tricks to avoid problems. If you need some notes, they are adviced there.
Also the notes [116787|https://websmp230.sap-ag.de/sap%28bD1kZSZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=116787], [552711|https://websmp230.sap-ag.de/sap%28bD1kZSZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=552711], [67205|https://websmp230.sap-ag.de/sap%28bD1kZSZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=67205] or [489690|https://websmp230.sap-ag.de/sap%28bD1kZSZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=489690] are interesting.
regards,
Martin

Data Load Error after Client copy on Source System

We did a client copy to our QAS source system. After that was complete, I tried to do a couple of full data loads. But they fail. The only errors I see are on the source system when I try to manual update the Idocs. They are:
EDI: Partner Profile not available
Entry in inbound table not found
Is there a step I need to take after the client copy and before the loads? I have a feeling that I'm forgeting something.
Thanks,
Chris

Hi Chris,
Check the following.
1> Go to WE20 check whether you are able to see two logical system in "Partner Type LS" one for Source and one for Myself.
2> If you say Yes for <1> then check in both the logical system, in the classification tab, partner status should be 'active'.
3> Check you have used REMOTE USER in main and in Outbound and inbound Parameters "Post Processing Permitted tab " for each Message type.
4> go to out bound message type and check the "Receiver port" pointing to correct RFC destination for both ( Source and Myself logical system).
If your answer is no for <1> then perform all the steps.
Hope this will help you.
Suneel

Client Copy error during client export / RX file is not getting

Hi Experts,
During the client export process of client copy in order to created two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Hi Experts,
During the client export process of client copy in order to create two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Client Copy error during client export / RX file is not getting generated

Hi Experts,
During the client export process of client copy in order to created two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Hi Experts,
During the client export process of client copy in order to create two tranports requests(<SID>KT* and <SID>KX) for import we need to have the RT and RX files in data file folder and RT and RX in Co-file folder of usr\sap\trans. But I am getting all exceot RX which contains the client specific texts and forms. Hence I couldn't able to generated the second request <SID>KX.
In the transport log it is saying the package 'BCSC' doesn't exitst and some objects are not entered in the object directory.
Please advice me whether I can proceed the import with the available KT* request which conatinas client specific data and hence avoid the KX* request or please let me know whether there is any option to avoid this error while during a fresh export again.
Regards,
Haris

Local client copy requir RFC

hi all
i have create new client 100 on dev. when i logon at 100 and start local copy , it generate error saying that RFC required.
plz quide me how i create RFC for Local client copy . my source client is 000 and target client is 100
regard
Khan

i just click on wizard and give the required field

Can a client be refreshed with client copy?

I created a new client by
doing client copy from client 200 creating client 202
Now I want to refresh client 202 from client 200 (ALL ON SAME SERVER) , can I just re-run the client copy with source client being client 200 to client 202?
If so what am I to expect?
If not, then do I need to first drop client 202 and then do the client copy to re-create the client?
maria

Dear Maria,
Greetings!
To be clear, now your situation is to have a client copy from your Production client 200 to the Quality client 202.
Coming to the status of other clients in Quality system, the data or any other settings of the other clients is NOT going to be changed because of this client copy.
As far as the configuration part, you will have to perform the following functionalities in your Target client (Quality - 202)
1. Transaction SCC9 - Select Profile - Choose the SAP profile as per your need.
2. Enter the RFC destination to the Source system client - Production Client 200 - This RFC destination could be an already existing connection between both the systems or a newly created one.
3. Make an RFC system comparison to be sure that the connection is perfect.
4. Set-up the parallel processing parameters, Menu option Goto - Parallel Process. This option is dependent on the physical memory availability of the Quality server.
5. Execute a TEST RUN, prior to start of the actual client copy to verify Target client feasibilities. In case of any mismatch in table definition or table fields corresponding action has to be performed.
Please remember the following pre-requsities before starting the client copy.
1. Both the Source and Target client is to be locked against access to end users or other users. For a pre-caution lock all the users except SAP*, DDIC, TMSADM, BASIS and other System Admin users in both the clients.
2. No auto-logout parameters or restrictions on workprocess runtime exists as profile parameters in the system.
3. Additional space for a client is available in the database so the the client copy in not interrupted.
Kindly process the client copy in a server session such that network interruptions and other interruptions could be avoided.
Kindly revert in case you need further informations on the same.
Thank you
Regards,
Vineeth

Solution Manager 4.0 client copy

Hi all,
We have installed solution manager 4.0 SP 12. We have also done a client copy from 001 to 100 in order to work exclusively in the client 100. I have also changed the client reference in RSADMINA table and the UME from 001 to 100. Finally, when I wanted to implement Solution Manager Diagnostics, I have run the "Setup Wizard" and it created automatically the RFC destination "WEBADMIN" but with client 001. I tried to check everywhere where the old client is still mentioned in both ABAP and Java parts, but no way. Could you tell me please if I forgot something to do after the client copy? Where can I change definitively the reference of the old client?
Thanks in advance for your action.
Regards,

Did you use client 000 as your source client (001 as the user master)? You should not client copy from source 001 as of solman 4.0.
Reference point 6 of note: 1041351
https://service.sap.com/sap/support/notes/1041351
Thanks.
Edited by: Phil May on Aug 26, 2008 7:07 PM

Regarding client copy and authorizations

hi,
i had installed SAP BW 3.5 on my system.it is a fresh installation.now the probelm is that iam unable to open the administration workbench screen which is the most important of all the BW screens available.when i type the relevant tcode , it is saying "screen cannot be opened on 000 client".so i created one more client 070 (by copying client). and when i log on using 070 client , it is saying you are not authorized to use that screen.
any suggestions?had i missed something in the installation?
regards,
ravi

Hi Ravi,
The procedure to delete is as below.
1.     Log on to the client to be deleted.
2.     Execute SCC5.
3.     Check the delete entry from T000.
4.     Schedule in the background.
Since you said you have deleted already , may be you have not checked the delete entry fron table T000.
In this case Go to table T000 and delete the entries.
After that create a client as below.
A local client copy copies between clients within the same R/3 System.
Both a local and remote client copy must be initiated from the target client using the following steps:
1.     To create an entry for the target client in the client maintenance table, choose SCC4
2.     Log on to the target client as SAP* with the initial password PASS.
3.     Perform the client copy using SCCL.
4.     Select the data to be copied using a profile.
5.     Assign the source client for Customizing data, application data, and user master records.
6.     Begin the client copy.
7.     As copying is a lengthy process, use background processing.
8.     To ensure data consistency, you may not logon to the target client during a client copy.
9.     Lock the users in source client.
Regards,
Bapujee naidu

Client copy etc.

Hello,
Cold anyone please provide me with a step by step procedure for client copy within Netweaver 2004s?
Furthermore I need guidance concerning the rest of the basic setup as well. The actual Netweaver/BI-system is installed. Now the client needs to be created and furthermore settings for RFC etc. needs to be done.
Does anyone have a good description for this?
Thanks,
F C
null

hi FC,
try to set the active client ?
se16, table RSADMIN, field BWMANDT = 1 e.g
following is bit old oss note, valid for bw 3.x, not sure for nw2004s
Copying productive client 000 in the BW System
SAP Note Number: 116432
Symptom
BW is being productively operated in client 000 and is to be moved into
another client.
Additional key words
Cause and prerequisites
Solution
The copy of the productive client 000 is executed in several steps:
a) Locking the system
    During the copy procedure, production in client 000 must not be
   active.
Restart the BW System and lock it so that no logon can take place,
    the same way as for an upgrade.
b) Maintenance of table T000
   -   Note the entry of 'logical System' for client 000.
    -   Delete the entry 'logical System' for the client 000. When
       saving, the warning which results from this can be ignored.
    -   Now create the new BW production client.
       Enter the exact contents that you previously deleted from client
       000 in the 'logical System' field.
       Save the entry.
c) Check of tablespace PSAPCLUD (depending on database)
   Please check the number of records of table EDI40 using transaction
SE16.
   Afterwards determine the freespace in tablespace PSAPCLUD using
   transaction DB02.
   Increase tablespace PSAPCLUD so that table EDI40 may be copied.
d) Client copy
    - Log on to the target client as user SAP*
   -   Go to the client copy via either transaction SCCL or via
        Tools -> Administration -> Administration ->
      Client Administration -> Client copy -> Local copy
       Use the profile "SAP_ALL".
       Make sure that all entries are active in the profile in the area
       'Data selection' und 'Copy mode'.
       (only then are number range counters copied)
    -   Choose in each case client 000 as 'source client' and as 'source
      client for user master record'.
    -   Now start the copy procedure in the background.
After completion of the copy procedure:
e) Set the production client
   Enter the chosen production client in the instance profile or
   DEFAULT.PFL as logon client. Maintain the parameter
                       login/system_client
   for this.
   Once production has been initiated, the client may not be altered
   any further.
In all OLTP systems:
f) Maintain the RFC connection in the OLTP systems
Logon to all connected OLTP systems and maintain the RFC connection
    to the BW system.
   For this purpose choose transaction SM59; expand the section
   'R/3 connections'. Below you'll find a destination named
                         <SID>CLNT<client>
   where <SID> is the name of the BW system and <client> is your
   old production client in the BW system.
   Choose 'Change' for maintenance.
   Replace 'Client' by the new production client; save the entry.
   Check the connection using 'Test connection' and 'Remote login'.
In BW system only:
g) Unlock and restart your system.

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 using Client Export... Failed .. Need ur advice

Hi guiys how ru all doin...
I hope some one can help me oout in this issue.iam working on sap
4.6c, windows 2003 server, oracle9.2.0.
we need to take client copy from production client 300 to dev
server using client export method so I have performed client
copy using client export.these are the list of steps which i
performed but still am facing an error.
Checklists /prerequisites before doing client export :
Source client i.e. Client 300 should be locked for all users
except Administrator.
Ensure that NO Users are logged in both NCCSAPPRD and NCCSAPDEV
Server.
Inform Downtime to Users.
At least 2 background work process should be there.
Take Offline Backup of both Production server & Development
server.
Following Jobs rescheduled for next day for Client Export
Process:
1)Collector_for_performance_monitor
2)Customer_evaluati on_information
3)Error reporting
4)Eu_out
5)Vendor_evaluation_information
6)Leave_en titlement
Remove scheduled job from DB:
1)Check opt
2)Analyze tab
Lock all users except administrator
Change database mode from Archive to Non-Archive mode
Logon in NCCSAPPRD in Client 300 the one which is to be Exported
1.Enter Transaction SCC8
2.Select the copy profile and target system NCCSAPDEV Server and
other fields as necessary.
3.Click on "Execute in Background" button.
4.Click on the "Schedule job" button.
5.Verify that all information is correct and click on YES
button.
6.Click on continue at the "Info Client Export" window.
7.Specify the start time and click on SAVE.
8.Specify an output device at the "Background print parameters"
window and click on SAVE.
9.Click on OK at the information window.
Monitor the Client copy using transaction SCC3.
when am going to transaction scc3 in that ->All transport
requests ->Exports -> in that my source client 300 is there when
am double clicking it its showing me list of how many times
client export has been performed in that my date is also there
when iam double clicking it and going to details tab this is wat
the error which its giving....
Log file:
nccsapprd\sapmnt\trans\log\NCPET00968.NCP
Preparation for export
Transport request___: NCPKT00968
System______________: NCP
tp path : tp
Version and Release: 305..15 46D
Execution of the export pre-processing methods for request
NCPKT00968
Start:Sorting and compressing the object list
End:Sorting and compressing the object list
Start:Check for existence of inactive objects
End:Check for existence of inactive objects
End:Check for existence of inactive objects
End:Creating project information
Start:Writing nametab information for key entries
End:Writing nametab information for key entries
Start:Version creation of the objects of the request NCPKT00968
End:Version creation of the objects of the request NCPKT00968
Start:Adjusting the object directory for the objects of the
request NCPKT00968
End:Adapting the object directory for the objects of the request
NCPKT00968
Preparation for export
End date and time : 200708104758
Ended with return code: ===> 0 <===
Mainexport
Transport request___: NCPKT00968
System______________: NCP
tp path : tp
Version and Release: 305..15 46D
SQL error 1652 accessing GLFUNCA: ORA-01652: unable to extend
temp segment by 128 in
SQL error 1652 accessing PPOIX: ORA-01652: unable to extend temp
segment by 128 in
Incorrect export. Request is not imported.
Main export
End date and time : 20070810152923
Ended with return code: ===> 12 <===
This is the error which am getting in the transport log.
I tried to perform 4 times client copy. the first 2 times i got
the same error and the next 2 times it ended with return code
===> 4 <===.
Plzz anyone help me out in this issue as i need to perform it
again and this time i hope with ur help it should be
successful.
Waiting for ur replies
Best regards

The problem you have is, that your TEMP tablespace is too small on the target system, you need to increase it.
Check Note 3155 - Termination due to tablespace overflow
Markus

Client Copy on SAP NetWeaver ABAP Trial

Hi all,
I've installed the ABAP trial from SDN and it works fine. In my leisure time I want to get some basis know-how. I bought the great book from Frank Föse, Sigrid Hagemann and Liane will about the system administration of an ABAP system. Now I want to try the client copy, which is described in chapter 5.2.
I have already created a new client with TCode SCC4. Now I want to copy client 001 to client 100, there I should login to client 100. I tried it with user SAP* and password minisap and password PASS as well, but it doesn't work. Isn't it possible to copy clients in the trial?
Thanks in advance for your help!
Best Regards
Marcel

Hi Marcel,
1 In an empty client there are no user master records. To be able to log on you have to set login/no_automatic_user_sapstar to 0 and restart the instance. That will activate the built-in user sap. In your other clients sap probabely has a user master record and will exist regardless of the parameter setting.
2 The windows share I mentioned is not a subdirectory but a network share. Go to D:\sap in windows explorer, rightclick and select sharing. Share the folder as "sapmnt".
3 You can edit the instance profile file with a text editor to add the login/no_automatic_user_sapstar parameter. If your installation is in D:\sap the path will be:
D:\sap\ SID \SYS\profile\ .
The name of the file you need starts with that SID again. For some reason unknown to me the parameter did not work when it was appended to the file but did when put in the middle.
Jurjen
Edited by: Jurjen Heeck on Mar 9, 2008 8:02 PM

Error After client copy

Hi all,
I did a client copy in ECC IDES with client 800 as source client.As per the logs , copy is successful.The profile usedf is SAP_ALL.After the copy we logged into the new client which was
created and it looked good. Checked the Logs in SCC3 and it said that client copy was finished sucessfully.However now when we go and execute transactions MM01 and VA01, it is giving a error saying
Batch definition level not found.System inconsistency!
Not sure what went wrong, Any suggestions would be Helpful.
Regards,
Chaitanya.

hi...
send the full details of ur client copy....
what is ur target client where u did this client copy .. i mean in prod dev

Client copy using export

can we perform client export for a local client copy(e.g) in DEv system i need a client 500 .i can perform local client copy from 100 but can i do it through export as both clients are in same system.

Hi,
There is an option for Client TRANSPORT which will help you perhaps:
A client transport differs from a remote client copy in that it does not use RFC. Like a remote client copy, however, a client transport is used to copy data between different R/3 Systems.
A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Second, the data is imported from the operating systemfiles into the target client.
To perform a client export, proceed as follows:
Log on to the source client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) Client Transport(r) Client Export. Select the data to be copied using a profile.
Indicate the target system to which the client will be copied. (The target system must be defined in TMS as part of the transport domain.)
Begin the client export. As copying is a lengthy process, use scheduled background processing. The client export performed in the source system <S-SID>, exports the client data asynchronously bycalling the transport program tp at the operating system level. This export process will generate up to
3 data files at operating system level:
. RT< number >; this file contains client-specific data
. RO< number >; this file contains Cross-client data
. RX< number >; this file contains SAPscript texts
Depending on the type of data selected through the client transport profile, the client copy command
files added to the buffer of the target system are
<S-SID>KO<number>; this file is for cross-client data
<S-SID>KT<number>; this file is for client-specific data
<S-SID>KX<number>; this file is also for client-specific data
The client export change requests are not imported when an Import all takes place. Therefore, you must import these requests into the target client using TMS. You must import the data in the following order: first cross-client data, then client- specific data.
After the import process has completed, post-import activities are required possible for object generation steps. After completing the import, log on to the target client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport *(r) ImportEditing
To display client transport logs, use the Transport Organizer.During client transport, a Repository consistency check can be performed by clicking the RFC system check button in Transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary tables definitions missing in the target system is generated. This will help your recognize in advance formal problems that may occur during the import of the source data.
Reward Points if useful
Regards,
Srinivas

Client Copy - Which source client 000 or 001?

Similar Messages

Maybe you are looking for