Profile for Client Copy

Hi all,
I have to do a local client copy but i am confused as to what profile to be used. we have two clients 200 & 210 with master data in both. now we want to overwrite 200 client with the config, user-profiles and all but no master data of 210 so that 200 will be cleaned as  far as Master data is concerned and we can upload new Master data. but it shouldn't be overwritten by 20 Master data. Can you please help me with what profile to use? Is SAP_UCUS ok? or do i need to choose some other profile?
Thanks & Regards,
Priya

Hi Priya,
Taking into account that:
Application Data = Master Data + Transaction Data
And that you can not copy Application data without transaction data using client copy, maybe you can to either create a production client (SCCL) or take a export of client (SCC8) before creating transaction data .You can
either use SAP_ALL or SAP_APPL profile for this. See the notes 24853 and 19574 about it..
Nevertheless, It seems to me you want to copy customizing but not application data so best option is probably SAP_CUST.
SAP_CUST
Client-dependent Customizing, including authorization profiles, are
copied. The application data is deleted and the user data is retained.
User Data -> NO
Customizing -> YES
Application Data -> No (deleted)
SAP_UCUS
Corresponds to SAP_CUST with user master data.
User Data -> YES
Customizing -> YES
Application Data -> No (deleted)\
Br,
Javier

Similar Messages

  • Role of copy profiles in client copy.

    Hi All,
    Can anybody give the idea regarding the role & importance of copy profiles in Cilent copy..
    Regards
    Srinivas K

    Hi,
    The client copy profile is the one which decides the kind of data that is going to get copied to the new client.
    So choosing a profile depends on the kind of activity or the purpose for which the new client is been created. Ex :Training client ,testing etc.
    For this we need to know the requirment clearly for what the requster is going to use the client accordingly choose the right profile to copy the client.
    If we have good undersatnding of end users work then Basis persons can come up with a profile to be used in a client copy.
    So classification of data plays important role in choosing a copy profile.Like Application data,Customizing data,User master data etc.
    And also client depedent or independent data...
    And for more details you can go through the above link provided by Deepu.
    As far I know we can not copy the application data alone as it dependents on the customizing .
    So we need to copy both of them together if we need application data.
    Secondly we have be more careful if we are opting for a cross client customizing as this is going to impact not only the target client but also other clients in the system.

  • Which client should be use 000 or 001 for Client Copy

    Hi,
    Which client we can use 000 or 001 for fresh Client Copy.
    Also what is the diff. b/w 000 and 001 client and its uses...
    Please suggest.

    Hi
    Always use client 000, except for solution manager systems.
    Best regards
    550894 - CC-ADMIN: Setting up a new client
    Always use client 000 as a template, and never client 001. (A known exception is the SAP Solution Manager.)
    Do not copy any application data from client 000 because the consistency of data and the number ranges cannot be guaranteed.
    Only client 000 is populated with upgrades, Legal Change Packages, Support Packages, language imports and so on with new Customizing so that it always contains the current sample Customizing. This is why it is also so important that the copy is only carried out after the system is updated. Client 001, on the other hand, is obsolete. It serves only as a sample client and may be deleted at any time.

  • Space requirement for client copy

    Hi,
    I have installed ECC6.0 IDES (ABAP only) with Oracle DB.
    I am trying to perform a client copy with option SAP_CUST
    Source Client: 001
    Target Client: 010
    Can anyone tell me whether I require the same amount of disk space of 001 to perform a successful client copy (to client 010)?
    And, if so, how to check how much space is being used by the client 001( database and application)?
    Best Regards,
    Moulinath
    Edited by: Moulinath Ray on Dec 23, 2008 11:58 AM

    Hi Moulinath,
    The amount of space depends on the amount of data being copied. If you copy the "application data + customising data + user master data", then size will be the same.
    Obviously client independent data is not copied.
    ou can use RSSPACECHECK to see the amount of space being used.
    Kind regards,
    hemanth

  • Methods for client copy

    Dear All,
    I want to make copy of PRD client to DEV client while the database size of PRD is 320 GB.
    Please tell me methods of above queury  and
    how much time will be require for completation of job?
    system info is :
    Window server 2003 64bit.
    SAP ECC 6
    Oracle 10.2.0.4.
    Regards,
    diya

    Dear Sunil,
    DB System    ORA
    Size:         225.35 GB  Total size: 351.56 GB
    Free Size:21.22 GB    Total free size:147.43 GB
    Used:        91 %          Total used:58 %
    Profile            SAP_EXPA
    exported files are :
    RO00031.PRD    420MB
    RT00031.PRD    10.5GB
    RX00031.PRD    463MB
    total size           11.4GB
    Have to applied latest TP, R3trans and R3load patches?
    i did not applies any patch yet while patch version are below
    r3trans version 6.14 (release 700
    r3load version R7.00/V1.4 [UNICODE]
    tp version 372.03.35 (release 700, unicode enabled)
    if i upgrade kernel patch then above versions will automaticlly upgrade. may i upgrade kernel patch.
    Have you performed the database statistics run on all tablespaces?
    You can schedule in DB13 or use brtools
    yes
    Have you checked the tp log? and the import log at OS level?
    sunil...I am moniting the oraarchive folder and only 2 to 3 archive generate in a day. its mean it is running...
    while the logs are exist and size still increasing.
    regards,

  • Standard report for client copy

    Hi All,
    is there any standard report exist to copy all the infotype  data from production client to development client for a perticuler employee?here we r facing the situation that dev client is not updated as production so the errors which we gets in the production to solve them we have to create the same data in development manually and it is very time consumming.so if anybody knows then please tell me .or is there any other way to do the same?
    Thank u.
    Raj.

    Though above solution will work, it will need lot of efforts and more than that extraordinary knowledge of SAP tables. For each problem scenario, the Infotype & Spro tables will vary drastically.
    To send a dev request / transport request and to tell the abaper what needs to be moved can be huge task. Thats where a tool helps

  • Profile for Production Client in production server.

    Dear Tech Masters,
    I have installed SAP ECC 6.0 (Production server). Now I want to create client ( First client after installation), which would be the  production client. I am not sure about the profile for client copy from 000. After a lot googling ...I am confuse whether SAP_ALL or SAP_CUST which one I use for client copy from 000 for production client.
    Please help me asap.
    Edited by: RABI PAL on Jan 2, 2009 7:44 PM

    go with SAP_ALL
    you are using 000 client and ur going to create new client XXX for XXX client you try to use SAP_ALL then you can you DDIC with full authorizations for XXX Client.

  • Local Client Copy

    Hello all, here's a quick question. I am requested to create a Sandbox Client in our Dev box. I already created an entry in TBDLS through SALE and also created an entry in T000 through SCC4. I logged into the target client and went to SCCL. I have done this many times but, no matter how many ever times I do this, I tend to confuse myself with the profiles. Which profile do I choose in SCCL for client copy. Basically, am I only populating the target client with Customizing data from the source client? Or am I also copy the application data. I believe, the normal practice is not to copy the User Master but, create them as we go based on the requirement. I would really appreciate if someone could throw some light on this. By the way, the source client from which the data is requested for the sandbox is a 'Customizing Client'. I think, I have only three options here (may be): SAP_CUST, SAP_CUSV, SAP_CUSX.
    Thank you.

    Hello,
    Although your reference client is a customizing client only I recommend to use the SAP_ALL profile.
    Reason is simple.
    Some of the so called pseudo customizing is stored in tables of type 'A' (application data).
    Example : classification data, release strategy MM, ...
    In case you use a SAP_CUST or another profile that only copies customizing data you will miss the pseudo customizing in your target client and you will need to redo it there.
    I hope this helps.
    Wim

  • Client copy error : SAP_CUST

    Hi
    we just load the SAP and facing the problem in client copy
    We just created client 100 and cliant role custmization but when trying using sccl for client copy it show the SAP_CUST and some rcf error .
    Please suggest.
    Regards,
    Ravi

    Local client copy
    scc4 --create an entry in table t000
    Create a client 100
    Login to client 100 with sap* and password pass.
    sccl and choose profile and user master data
    It shall work.
    What is the error you are getting?Please check the log from scc3?
    hope it works.
    To help you better ,You should post your query correctly.
    Thanks
    Amit

  • How i can create client copy

    how i can create client copy .
         pls tell me step by step procedure to create client.
             and client copy.

    For client copy login to source client with t-code scc4 and create the new client. Provide the details for new clients.
    Create the new logical client for new client.
    check for the the profile parameter
    login/no_automatic_user_sapstar = 0
    login to destination client with sap* and p/w as pass.
    run t-code sccl for local client copy with sap_all.
    Kindly provide the points if issue solve.
    Regards,
    Rohit mehta

  • 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 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

  • Logical  system name to be updated while client copy--URGENT HELP REQUIRED

    Hello All,
       I have a  query regarding the "Logical System name" updation during Client copy.
      When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
      There is  a  std transaction BDLS through whcih w e can change the current Logical system name to  a  new one but this  seems to work fine for System copy but not for Client copy.
      So when i make  a client copy of  SRM masters  for Production system,is there  any other std  way wherein i can change the "Logical system name " for the  backend or  do i have  to write a  CUSTOM program wherein entries  for  the Backend Logical system name in tables like CRMMLSGUID will  be updated  with  the new  Logical system name?
       Any help on this is  appreciated.
    Thanks & Regards,
    Disha.

    Disha,
    Yes, I did it twice and it worked fine.
    The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
    SRM checks this GUID in CRMMLSGUID table.
    If is not the same one, then replication process fails.
    The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
    Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
    The issue is exactly ours: around system/client copy.
    In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
    We have to take some risks sometimes...
    Rgds
    Christophe

  • 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

Maybe you are looking for