Logical System Name after System Copy

Hello,
I have three questions about the logical system name after system copy.
Q1) When I change SID D22 to S11 during system copy,
do I have to change the logical system name of all clients in the target system? The target system is used for test, and the landscape has S11 and Virtial system. The target system S11 does not communicate with the source system D22.
Q2)  If the answer for Q1 is YES, is it correct that the following procedure for changing logical system name?
1.Tr-CD:BD54
   Add new logical system name for all clients in the target system.
2.Tr-CD:SCC4
   As for all clients, select new logical system name with F4 help.
Q3) If the answer for Q1 is YES, do I have to add new RFC connection entries with SM59 for all clients in the target system?
I refer to the guide "Homogeneous and Heterogeneous
System Copy for SAP Systems Based
on SAP Web Application Server
ABAP 6.40 SR1".
thanks,
Keishi

Hi Keishi,
As a good and ideal practice the answer to your first question Q1 is yes. Infact I would say that in case you are using ALE then it is must
For Q2 there has to be an additional step which is most important one. Running BDLS transaction which would allow you to change logical systems in relevant tables from the one of source system to target system.
For Q3  the answer is agaain yes and you can have two approaches>
1. manually recreate all the RFC destinations after sys. copy.
2. Export all the RFC destination data relevant tables before system copy and then reimport them after sys. copy.
Regards.
Ruchit.

Similar Messages

  • Logical system names after system copy

    Hi!
    I installed a new SAP system via System Copy (SAPINST) approach.
    As a consequence the old logical system names have been copied.
    Question:
    What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
    Thank you very much!
    regards
    Jürgen

    Logical System Names
    When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.                               
    A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
    Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
    Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
    You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
    In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
    Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
    Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

  • Change logical system names after system copy

    Hi!
    We successfully installed SAP ECC 6.0 system as system copy.
    All the logical system names of old system have been copied to new system.
    Question
    What is the approach to change the logical system names for new SAP system?
    a) just via tcode SCC4
    b) via BDLS
    c) other tcodes, reports
    Thank you very much!
    regards
    Jürgen

    Hi,
    Go though the system copy guide.
    http://service.sap.com/instguides
    After system copy,
    If you need to change logical system names in the system that results from the copy, change the logical system names as described in SAP Notes 103228 and 544509.
    https://service.sap.com/sap/support/notes/103228
    https://service.sap.com/sap/support/notes/544509
    Before running BDLS to change the logical system name, you have to define the correct logical system name in the new copied system. in tcode BD54.
    - while running BDLS, execute in background.
    Regards,
    Debasis.

  • Logical system names after system copy for SAP ECC 6.0

    Hi!
    We successfully installed SAP ECC 6.0 system as system copy.
    All the logical system names of old system have been copied to new system.
    Question
    What is the approach to change the logical system names for new SAP system?
    a) just via tcode SCC4
    b) via BDLS
    c) other tcodes, reports
    Thank you very much!
    regards
    Jürgen

    I think you can do it through BDLS

  • Incorrect Source System name after System Copy

    Hello Friends,
      When we copied Source system  from Production  to our  Qulaity  system,   the DTP s are still displaying Production Source system.
    We are in BI7.0 SP13 . I have run TC BDLS to convert Old Source system to new Source system.
    But still displaying  Old source system .
    Please help me with this Issue .
    Any advice appreciated .
    Thanks

    Hi,
    Take a look at OSS notes below.
    o 184447 Building a BW-system landscape
    o 121163 BDLS: Converting logical system names
    o 369758 BDLS: New functions and better performance
    o 524554 Storing destinations in the BW environment
    o 325470 Activities after client copy in BW source systems
    o 538052 Maintenance of Myself destination in BW
    o 305527 Details for correct BW Source System Connection
    o 325525 Copying and renaming systems in a BW environment
    o 184971 Notes on BW source system connections
    o 184754 Procedure after BW database copy
    o 305527 Details for correct BW Source System Connection
    o 547314 FAQ: System Copy procedure
    o 140276 Error in source system assignment
    Regards.

  • Logical System Conversion after system refresh failed

    Hello,
    Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the  job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
    02/18/2009 16:09:33 Job started                                                                     00           516          S
    02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
    02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
    02/18/2009 16:10:19 Job finished                                                                    00           517          S
    When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
    Any suggestions on this?
    Thanks,
    Mahesh

    Hi ,
    Rerun the BDLS again as this took very little time.
    When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
    May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
    Thanks.

  • Conversion of source system names after transport

    Hi gurus,
    Please someone can tell me how to configure the "conversion of source system names after transport"  in the BI system as my transport is not working on a new BI System  ?
    Thx in advance

    Hi Firmin,
    You can do this in RSA1 in tools under conversion of logical source system names.
    Here you maintain the development system or the system used for development as the source system.
    You will have to mention the logical name of the development system.
    In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
    Check the folllowing link for more informationn on this.
    [Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
    Hope it helps you ,
    Best regards,
    Sunmit.

  • "Conversion of Source System names after the transport" : O

    Experts:
    Environment : BI 7.0 and SP 12
    <b>Tranports related to transformation rules are failing with inactive status...</b>
    Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
    Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
    Everything looks fine to me with reference to actual techinical names of source/target system...
    My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
    My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
    If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
    OR do i need to create another entry with same source/target system and check the 7.0 box.
    OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
    Finally, please advise the exact steps that need to be taken here...pros and cons
    Your inputs will be of great help....
    Thanks,
    BI
    Message was edited by:
            B I

    Hi,
       Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if  your client is modifiable, if not you need to transport the setting from DEV. Go to
    SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
    you also need to maintain the Source system IDs .
    Hope it helps.

  • Myself Source system problem after System Copy

    Hi All,
    We recently did a system copy (Production -> Dev). After the logical system rename is done, the myself source system is showing up as a External SAP system, in source system tree under SAP instead of BI.  I'm not able to restore/activate it.  Any inputs on this problem is appreciated.
    Thanks & Regards,
    Sree

    Problem was with inconsistency in the RSBASIDOC table. Solved by deleting invalid entry and running BDLS again for this specific table.

  • Changing the system Name after Installing EP

    Hi All,
    I need to change the system name of the server and the IP address of the server after EP is installed. Is it possible to do this? Will the EP work properly?
    Regards
    Arun

    Hi Arun,
    There is many reference in the config of the portal to the server name.
    I doubt you will be able to do it without difficulties.
    If you use KM, you will have trouble with internal links in documents. We had to install an apache server for redirection when we migrated/upgraded from EP6 SP2 to 2004s, because the server's name changed.
    Also, you will need to reinstall the local edit activeX to your users.
    I hope someone can answer you better than me.
    There always the system copy option.
    Brad

  • Conversion of Source system name after transport

    Dear All,
    I need one clarification.
    Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request  to BW Quality system but the source system will be R/3 quality system.
    For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
    My doubt is in Production server how do we maintain the mapping...
    Quality system ---> Production
    or
    Development system---->Production.
    Hope i am clear....
    Thanks &  Regards,
    Anup

    Hello Anup,
    The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
    1. It is done, when you have a single base system and different R/3 (source system)
    2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
    Well, i case that is needed, you may do it via :
    1. Go to RSA1
    2. Go to Tools.
    3. Tools -> Conversion of source system.
    In the right most table column, provide the source system you need to connect with your BW system.
    This will internally connect you with the specified R/3 system.
    Hope it helps!
    Neha.

  • Changing system currency after company copy using CopyExpress

    Hi!
    I have copied the dev database to test and would like to know if it is possible to change the system currency using the GUI (I have found tue way to do so using an SQL querry).
    Thanks!

    SAP will not support any database, which is inconsistent, due to SQL-Queries, which modify datasets or the datastructure of the SAP Business One Database. This includes any update-, delete- or drop-statements executed via SQL-Server Tools or via the the query interface of SAP Business One.
    This is stated in the support contract between SAP and the SAP Business Partner also.
    Check SAP Note: 896891     Support Scope for SAP Business One - DB Integrity
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=896891]
    Also check
    SAP Note: 631504     Do not use Delete, Insert and Update statements     
    [https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=631504]

  • Source System Problem after system refresh in RSA1 trx

    Hi,
    We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
    The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
    BI unknown in source system
    BI IDoc type ZSSB006 is not the same as source system IDoc type
    I performed following steps in R3 Test system after its system refresh:
    1. Created logcal system and created RFC.
    2. Created port in trx we21.
    3. Created partner profile in trx we20.
    4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
    5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
    After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
    I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
    Someone pls help me.
    Regards,
    Chintan

    Hi
           Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
    RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
    Check the the note for further  info...
    Note 886102 - System Landscape Copy for SAP BW and NW BI
    Hope halp you...
    Regards,
    Sureshram

  • Source System Problem after System Refresh

    Hi,
    We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
    The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
    BI unknown in source system
    BI IDoc type ZSSB006 is not the same as source system IDoc type
    I performed following steps in R3 Test system after its system refresh:
    1. Created logcal system and created RFC.
    2. Created port in trx we21.
    3. Created partner profile in trx we20.
    4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
    5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
    After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
    I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
    Someone pls help me.
    Regards,
    Chintan

    Hi Chintan,
    Can you please check IDOC in your Target system. It should be the same type. Better you do the Partner profile steps.
    Also please check have correctly created the idoc in Inbound or Outbound.
    Consider the case like if its exist in BW as Out bound then its connected to Inbound IDOC of R/3 and vice a versa.
    Please elaborate your refresh activites. Normally IDOC setting never get changed in you refresh activites.
    Just check your BW system patch level and search for Notes.
    Regards,
    Mahesh

  • Rescue & Recovery system lost after system restoring

    Hi,
    I have a X61 7673-a22 and my RnR environment is now the latest edition.
    Yesterday I had a factory state restore and I cannot find my RnR within Vista. I downloaded the installation package from the support site but it cannot be installed as my existing RnR environment is newer than the one I downloaded!
    Hmm... as the download site is quite messy, I downloaded the latest one I found, but not necessarily the lastest one provided.
    Without the RnR installed in my Vista I cannot make backups of my new system. Any help or information is appreciated, thank you!
    Message Edited by zkJoker on 04-24-2009 09:06 PM

    S1nfullman wrote:
    As a last ditch effort to solve a problem I was having I did a complete wipe and os x leopard reinstall. That part went fine but when I did the restore from time machine it keeps hanging on the last step of transfering information. It gets stuck on less than a minute remaining transfering files to support applications. I tried to restart it and then restore again but it says the disk is too full so I'm guessing files are there but bringing the system up without restoring doesn't let me access my information. I tried the whole process again and the same thing happens.
    I'm desperate here. My system is unusable and I can't access my files. Any ideas on how I can get past the final hang or what might be wrong?
    no idea. if you can't make the automated migration from TM work I suggest you do an erase and install and migrate what you need from the TM backup by hand.
    see this link on what to restore from your home directory
    http://discussions.apple.com/message.jspa?messageID=6185507
    you'll also have to reinstall your apps.
    I'm running an original MacBook pro.

Maybe you are looking for