Client Copy in BI 7.0 and ERP 6.0

Hi
I have done a system copy of both the BI system and it's source ERP system and am following the post copy steps to ensure that the connectivity between the two is maintained.  However before I run BDLS to change the logical system names I would like to change the client numbers on both the BW and ERP client.  Does anyone know what the implications of doing a client copy in both systems is and then running BDLS for these logical system names?  Has anyone tried this and was it successful?  Can you do a successful client copy of BI?
Points awarded.
Thanks
Leigh

Hello,
Have a look at these OSS
SAP Note 446294 CC INFO: Logical system name and client copy
SAP Note 793717 Client copy into the BW client in Netweaver/mySAP ERP
SAP Note 103228 Naming the logical system
SAP Note 886102 System Landscape Copy for SAP BW and NW BI
SAP Note 307018 Convert partner name w.respct to logcl systm name
SAP Note 325525 Copying and renaming systems in a BW environment
SAP Note 325470 Activities after client copy in BW source systems
SAP Note 369758 BDLS: New functions and better performance
SAP Note 1148403 70SP18: BDLS after early replication
SAP Note 932032 BDLS: specific conversion for large tables
SAP Note 1059278 70SP15: Error in transaction BDLS
Also see,
Ex[Execute conversion of logical system names (BDLS) in short time and in parallel - Intermediate|Execute conversion of logical system names (BDLS) in short time and in parallel - Intermediate]
SAP Note 121163 BDLS: Converting logical system names
SAP Note 931029 Transformations are not taken into account (BDLS)
SAP Note 187297 Changing the logical system name in table T000
Thanks
Chandran

Similar Messages

  • Client Copy- releases of the export and import systems have to be identical

    Hi All
    I created a new client using the Remote Client Export \ import method (on the same system). The reason being is that I need a 2nd Test Client on the same system with a smaller data set for other testing purposes. As well as needing to re-import the same Testing Client after a future database restores from a different backup, and still needing the same small data set for testing after the restore whipped it out.
    Now that the 2nd Clients data set has been used, I've been asked for a 3rd test client, the same as the 2nd originally was. (No problem I figured) So I created the 3rd Test Client (SCC4) and tried importing the same transport files as created the 2nd Test Client.
    But I'm receiving the error message "Releases of the export and import systrems have to be identical".
    I am on the same system as the originial client export was made from, so the SAP release is the same.
    The only other thing I can think of is that we have imported some customizing transports from the Dev system into the original system since the export was taken.
    Can anyone help? Is there anyway I can get this back?
    Ken

    Solution found: Note 1291394 - ERROR : TA194 When performing multiple imports in the same client.
    I've imported the note, run the report as per instructions and I can happily say the Import is now running. Although it does seem to be taking a lot longer than it did for the original import.
    Ken

  • 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

  • Queary regarding Client Copy

    Hi Experts,
    I have a scenario where in my Source Systems runs on HP-UX,Oracle10G and ECC 6.0 and my Target Systems runs on Windows 2003,Oracle 10G and ECC 6.0 except OS all the SAP and DB versions and Patches are same.
    Could you please tell me can i able to do remote client copy( i am sure with client export/import we can do)? does any body done the same before.
    Please suggest me on this
    Thanks,
    Laxman

    As far as i remember Remote Client Copies between different OS is possible... essentially a client copy is a HUGE transport and as far as the SAP versions are the same it should be ok. (please correct me if I'm wrong)
    Read
    http://help.sap.com/saphelp_nw04s/helpdata/en/69/c24c4e4ba111d189750000e8322d00/frameset.htm
    and
    http://help.sap.com/saphelp_nw04s/helpdata/en/69/c24c684ba111d189750000e8322d00/frameset.htm
    Regards
    Juan

  • 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

  • Error message: no valid initialization after client copy

    Hi,
    We recently did a client copy of our quality BW and R/3 systems from preproduction. In the 'new' clients we have problems with the delta process for 2LIS_13_VDITM. We get an error message that there was no valid initialization in the system, where in fact a valid initialization has taken place (everything from preprodcution was copied).
    The source systems setting where corrected using BDLS, but the entries in R/3 tables roosprmsf / roosprmsc were still pointing to the old system. This has now been corrected.
    One problem remains. There is no entry for 2LIS_13_VDITM in table RSSDLINIT. I suspect that this causes the error message. Can anybody confirm this ? Is there a standard way to add the correct entry (with the package number of the init package) in table RSSDLINIT or realign table RSSDLINIT with table roosprmsf in R/3 ?
    Thanks in advance !

    Hi,
    After system copy. You will ahve delet your whole data and reload every thing.
    In case you are getting dump when you double click infopacakge then delete your data source entry in RSA7 in source system and then go for fresh init load and then continue with delta load. Before goign for fresh init load you will have to first delet the init load entry.
    This must help
    Regards,
    Rohini
    Message was edited by: Rohini Garg

  • Wrong datasources on DEV after client copy

    Hi all,
    a customer just made a cliente copy from PRD to DEV and now all data sources on DEV are pointing to PRD
    and it says that source system doesn't exist.
    1) What was the right way to do the copy so the datasources are still pointing to R/3 DEV (or QAS) after the client copy?.
    2) Is there any easy way to correct the situation without creating all transformations again ?
    Thanks in advance
    JP

    Hi,
    Ok.
    Then you can do same changes at bw dev server.
    You need to change table - RSLOGSYSMAP entries. it may have ECC prod name.
    Remove ecc prod server name, enter ecc dev server name and save it.
    Or ask basis team to maintain ecc dev server and bw dev server technical names entries at table RSLOGSYSMAP at bw server.
    You can maintain from below option as well.
    BW dev server t code - RSA1, Menu Tools--> Conversion of logical system names. on next screen you can change and save entries.
    Source - maintain ecc dev technical name
    Target - BW Dev server technical name
    Thanks

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

  • Client copy with different number of tables.

    Hi,
    I want to do a client copy between Client '100' and Client '200'. There are 121 tables in Client 100 and 101 tables in Client 200. Is the client copy possible. If yes what are the steps.
    Another question is. Is the reverse possible ie copying of client 200 (with 101 tables) to Client 100 (with 121 tables). If yes how. And also i would like to know what will be the state of 20 tables( not available in client 100). What i mean is, will these 20 tables become empty(data erased) or will contain the data as was before the client copy.
    Regards
    Naeem

    Dear Naeem,
    Kindly let us know are you doing local client copy or remote client copy . If you are doing client copy then system is on same PS level . If you are doing local client copy just perform test run and find out the differences .If it is remote client copy ,Its better to perform client export and import .
    Thanks and Regards,
    Arun Kumar

  • In Process Workflow Issue after Client Copy

    Hi
    We have made a client copy on our training system and wish to process workflow that were created on the original client.  Currently, of course, all the workflow instances have the original client.  Is there a way we can change this to the new client?
    Regards
    Ian

    Looks like there is something the basis boys ran to update these instances (and any other non workflow related thinks).  It is all part of the client copy process apparently.
    Cheers
    Ian

  • 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

  • Derivation Rule Problem After A Client Copy

    Hello,
    Has anyone ever encountered a problem with derivation rules after a client copy is performed? After a client copy, we have "some" FM and GM derivation rules (not all of them) that have to be manually copied from the source to the target client (line by line by line by line). I'm thinking that there has to be a way to prevent this since some rules are fine after the clent copy. Your input would be greatly appreciated.
    Will

    I believe that we have resoved our issue. For the derivation rule values that would never copy, we re-created these again starting in DEV and transported the derivation rules throughout the entire landscape (QAS and PRD). Evidently some derivation rules (and the related values stored in the tables) were created directly in Production. During a client copy the values in the tables for the derivation rules that were created directly in our Production environment would not copy to our QAS environment. Those rules were stored in a table named FMFMOAPRD1000122. Note that PRD is in the table name. After re-creating the rule and transporting it through the landscape, the table was named FMFMOADEV1000152 (for example).

  • Create Client copy only with Master data

    hi friends,
    we are going for SAP Re-Implementation.
    we want client copy only with master data without having transactional data
    Is it possible to copy the master data from production to production.
    can we transfer the data using ALE/I DOCS...?
    Is there is any standard BAPI  to transfer data across client....?
    if there is any solution please give me guidance.
    i have searched in SDN and SAP technical  but i can't find the proper solution.
    Thanks in advance.
    regards,
    karunakar

    Hi Karunakar,
    1) Make a client copy ready 2) Use Idoc and moved the master data. I am not sure how much data it is.We did the same before.
    Check these links form Peter.
    [TDMS|http://204.154.71.138/images/whiterhino/fp/tstsym5/testdatamigrationserver.pdf]
    [TDMS Wiki|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b43e2b4d-0b01-0010-c191-cba32880cb95?QuickLink=index&overridelayout=true]
    Regards,
    Madhu.

  • 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 between unicode system and non-unicode system

    Hello,
    we have to build up a new system for japan. It is planned to install a new 4.7Ext200 unicode system and then make a client copy from a non-unicode 4.7Ext200 (language= german, english) system to the unicode system. I don't think that this is possible way, but I can't find information regarding client copies from non-unicode to unicode. I would advice the project to convert the existing non-unicode system to unicode, make a system copy for the new system and then install japan languages. Any information, which can help me.
    Regards,
    Alexander

    Hi,
    without conversion client copy is not possible
    look at following
    Re: Client copy between unicode and Non-unicode
    regards,
    kaushal

Maybe you are looking for