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.

Similar Messages

  • 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

  • Operating system problem after system recovery

    i have PURCHASED  HP-ENVY-M6-1125DX (IN-USA) IT CAME WITH - WINDOWS8 OS .(BOUGHT IN BEST BYE)
    RECENTLY I UPGRADED TO WINDOWS8.1 PRO PREVIEW. SINCE THIS VERSION OF OS WAS ASKING THE ACTIVATION KEY,
    I HAVE RECOVERED MY LAPTOP TO FACTORY SETTINGS BY USING RECOVERY PARTITION PRESENT IN MY HARDDISK.
    BUT NOW THE OS IS WINDOES 8 BUILD9200, AND THIS OS IS ALSO ASKING FOR ACTIVATION KEY.
    PLEASE HELP US IN SOLVING THIS PROBLEM.

    Hello Mahantesh-uppin,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I understand that you are having issues reactivating your Windows 8 Product Key after a factory recovery. I would recommend that you review and follow the instructions in the HP Support document: Windows 8 Product Activation. This document will walk you through reactivating your Windows 8.
    I hope I have answered your question to your satisfaction. Thank you for posting this issue on the HP Forums. Have a great weekend!
    Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
    Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
    Dunidar
    I work on behalf of HP
    Find out a bit more about me by checking out my profile!
    "Customers don’t expect you to be perfect. They do expect you to fix things when they go wrong." ~ Donald Porter

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

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

  • ODS/PSA Problems after System Copy

    Hello All....i am a basis admin and am having problems with PSA after performing system copy. I have copied R/3 (source system) ans SCM (source system) and BW (3.5)systems from production into test environment in parrallel. I have performed all required BDLS steps on R/3, SCM, and BW as well as maintenance of RSLOGSYSDEST table. All profiles and ports (we20/we21) have been maintained as well. I have modified and tested all RFC connections and have used RSA1 to restore the source system connections and to activate and replicate. When activating ODS objects, the following error is generated...
    There is no PSA for InfoSource 8ZFAP_O01 and souce system PB1CLNT510.
    PB1CLNT510 references former production BW logical sys and correct logical sys should be QB1CLNT510. Apparently BDLS has missed a table or I have skipped a step in my post-clone process of BDLS and WE20/21. I am wondering if there is a re-initialization or logical system conversion step i have missed or is anything else i can do to resolve this issue.
    Maximum points awarded for quick resolution.
    Thanks in Advance
    Chris
    Basis

    Hello Chris,
    This InfoSource is related to a DataSource in which the source system is BW system itself (in your case: QB1CLNT510).
    Try to first activate the DataSource 8ZFAP_O01 using the standard program (SE38): RS_TRANSTRU_ACTIVATE_ALL in which you should input the source system (QB1CLNT510) and the InfoSource 8ZFAP_O01. If you get a green light in the log that appears after the activation completes in which it says that all the structures have been activated, then all you need is to locate the DataSource in RSA15 and right click -> replicate.
    If the log showed you that this DataSource doesn't exist, then you'll need to Activate the source system QB1CLNT510 again.
    I hope this helps. Cheerz,
    Ali

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

  • Exchange profile parameter problem after system copy of XI server

    I'm getting problem after the system copy of XI server. Following is the details. pls help to fix this one:
    XQA is the system copy of XDV server. XQA is installed on rx2n1v1 server and XDV is installed on dbcixdv server. Following is weblink of XQA and XDV.
    XQA: http://rx2n1v1:57400
    XDV: http://dbcixdv:57000
    After the system copy of XQA, i changed all xdv related parameters (hostname/port) in visual admin and configtool of XQA server.
    Now when i run sxmb_ifr tcode in XQA, it should open the link of XQA server ( http://rx2n1v1:57400). But it open the link of XDV server (http://dbcixdv:57000).
    The cause of this problem is the xdv parameter entires (hostname/portnumber of xdv) in exchange profile of  XQA server (http://rx2n1v1:57400/exchangeProfile).
    Now if i change hostname/portnumber of xdv in XQA server (http://rx2n1v1:57400/exchangeProfile), it also make the same change in XDV server  (http://dbcixdv:57000/exchangeProfile).
    Both XQA and XDV are in differnet hardware server. I don't understand why making changes of exchangeprofile in XQA also changed the value of exchangeprofile in XDV.
    Hope it clarify.
    Pls give the solution of this problem.
    Thanks
    Amar

    Arjun,
    http://<SAPHOSTNAME>50000/exchangeProfile
    Yes, I can use above, but changing connection information gives me
    RFC call returned an error code: 399
    Use this one
    http://hostname:50000/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp
    This one, yes I get to the exchange give me an error:  RFC call returned an error code: 399
    http://hostname:50000/dir/start/index.jsp -->Administration -->login with PISUPER -->ExchangeProfile.
    Internal Error
    Internal error; contact your system administrator
    Unable to read configuration data (ExchangeProfile/aii.properties)

  • SMSY - problem after system copy

    Hi,
    I have done a system copy of our solution manager system in order to test installation of EHP1, now EHP1 is installed without issues.
    I need to reconfigure SMSY to only point to our Sandbox for testing, but for some reason it won't let me create the RFC's and no RFC's no info get updated.
    When i try try to generate the RFC's it says "No client specified", but i cant populate the clients without reading the system data, when i try to read the system data i get "No read RFC destination found for system 'XXX'" (for obvious reasons.
    Do i have to run Initial, Basic Setup? or is there any way i can just create the RFC's manually?....
    Regards
    Juan

    Dear Juan,
    you can enter clients manually. If you create a new system in the system landscape, then you should able to enter clients in SMSY in tab "Clients". If this is greyed out for some reason, then you can change the data source to "manual input". Click in the menu: Main Instance => Other object. Enter the sytem ID in "System" field, and select the push button "Set data source to Manual input". Then you should able to enter new clients for this system.
    But I am not quite sure how the process is to reset it from Manual input back to automatic. Maybe SAP can add this.
    Regards,
    Holger

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

  • BI-RFC problems after client copy

    Hi all
    Client copy was done and after that when I tried to load data in BW, it ran for long time and finally showed cancelled in SM37. When I checked the source system in RSA1, it gave two messages.
    1.Incorrect IDoc type ZSAC008 in the ALE definition of the source system RSAR373
    2.Result of the destination check: Password logon no longer possible - too many failed attempts RSAR375.
    In long text of message 1 suggestion was to enter IDoc type ZSAB003. In SM30 for Message Type RSSEND Basic Type ZSAB003 Release field is empty. Is this error because of this?  After client copy is there a way to restore the settings back to how it was set initially in the development server? Basis told ALEREMOTE & BIWREMOTE are not blocked. What is missing here? Thanks a lot in advance. 
    Subin

    There are a few things need to be performed on basis side after copy .
    1. Restore of Logical system.--> check with Baisis team wheather they have performed this action or not after copy.
    2. Check your source system connection, in rs1-- source sytem --check
    3. Change the aleremote or Bwremote passwords.
    4. Try to logon to your sourcesystem ( from SM59 Tcode) Remote logon.
    Hope this helps.
    Regards,
    Reddy
    Edited by: Reddybl on Apr 1, 2010 11:56 AM

  • Delta loads a problem after client copy

    Hi Gurus,
    I did a system copy from R/3 Testing system to BW Testing system. After the system copy, the delta loads were working fine but now from yesterday the delta does not get loaded from R/3. When I try to make it red and start it again, it states the last request has not completed the delta load and it requests again. It seems RSINFO idocs need to be generated and sent to BW side but this is not getting generated and the load is still in yellow status. Finally the load also becomes red after the timeout time.
    I have checked all the connections, they are working fine. There are no entries in TRFC queue and Partner profile is present and is pointing to the correct destination.
    Is there any way to make the delta work again. Please advice as this is urgent and the delta loads are failing.
    Thanks in advance.

    hi,
    I did a system copy from R/3 Testing system to BW Testing system. After the system copy, the delta loads were working fine but now from yesterday the delta does not get loaded from R/3
    How were the delta working fine without reinitialization of the deltas after the system copy.
    The delta timestamp information is stored in SAP base tables. The system copy not only copies the structure but also the data in those tables, the delta enteries in those tables would be of the system from which you copied. You again need to reinitialize the deltas to correct this.
    regards,
    Arvind.

  • Problem after system copy

    Hi
    We have taken a copy of our production syatem to our sandpit.
    The problem is that everything has gones well (BDLS etc) but in our source systems in RSA1 (BW) it correctly has the technical name of the source system but when right clicking and selecting chnage the rfc destination is incorrect (it is the fake one we created).
    You cannot change this field by right clicking and if i try to create a new one then after selecting the source system it says it already exists as the fake one is using it.
    The opnly option i seem to ahve is to delete the incorrect one but it asks if i want to delete all psa tables and transfer rules...this seems a bit too much deletion for me.
    Is there anyway around this??? Can i maybe delete the fake one in SM59??
    Cheers
    Andy

    Hi Andrew,
    did you already follow what described in this useful doc ?
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    Hope it helps!
    Bye,
    Roberto

Maybe you are looking for