Reconnect R/3 source system after BW systemcopy ?

We want to copy our BW 3.0b development system as a BW sandbox system in order to try out the BW 3.5 migration.
Therefore, we performed a system copy of our BW DEV system to a new machine. On the BW-side we ran BDLS to get a new logical name for the system and defined a RFC connection to our R/3 Dev Source System (incl. appropriate RFC users).
On the R/3 side we also defined an additional RFC connection to the "new - just copied" BW-system.
While trying to reconnect our R/3 Devopment source system within the new BW we encountered the problem that the R/3 system recognized that there already exists a connection to a BW (the old BW dev). If we take this option, the old connection is deleted and a new one is defined. However, from the R/3 perspective we want two BWs connected. It seems the problem has to do with the IDOCs and TRFC port definitions, because the IDOC type ZRSBW010 seems to point to the wrong system.
Unfortunately, we are stuck at the moment.
Any kind of help or hints to relevant SAP documents would be much appreciated.
In the OSS we found some notes on this topic (325525 etc.) but we still not sure how to proceed.
However, in general, we think it shouldn't be a problem to have one R/3 connected to several BW's or is it?
Frank Schülke, E.ON Ruhrgas IT, Germany

Frank,
It is possible to connect a copy of your BW dev. system to the same R/3 system. The problem you are experiencing is related to the connection ID from table RSABASIDOC. This is a unique ID in your system (normally the first two characters of your source system name). Tis ID is in RSBASIDOC in yuor BW and R/3 system. When you copy your BW and try to connect it to your R/3 system again, you will get the conflict you already noticed.
The solution is to run SE37 --> RSAP_BIW_DISCONNECT in your new BW system (make a screen shot first of the RSBASIDOC entry!). This will be cleared by the function module. You will notice that the source system is not visible anymore is RSA1. However all the transfer rules etc. are still there (invisible). This would not be the case when you are doing a remove source system in RSA1 as suggested.  Now you can create the source system again via the normal way. Use exactly the same name for the source system mas you made it via the BDLS. During this process the BW and R/3 systems are "negociating" a new unique connection ID for this BW-R/3 connection. This creation of the source system will also make all the related info visible again (like transfer rules).
Note in general: If you get a screen saying the connection ID is already used, ALWAYS choose DO NOT DELETE. After chosing DELETE there is no way of solving the issue other then restoring the system from backup! In this case you would delete everything in your R/3 system regarding the original BW system! When you get the message, check RSBASIDOC in both systems as there will be a conflict.
Regards,
Sander.

Similar Messages

  • Test System (BQ1) Objects showing up wrong Source System after Transport.

    Hi Experts,
    We are working on IS-U BI7.0 Project. We have finished with our Development and have transported the DataSources, Transformations and DTPs from Development (BD1) into Test (BQ1) Systems.
    We have entered values in the Conversion of Logical Source Systems correctly.
    When we select the DataSource and Click Object Directory Entry from the Extras Menu, we found that the Original Source System is defined as BQ1 instead of BD1 (Development System), which is where the Object is getting Transported from.
    We have implemented an SAP Note:1008633 (Incorrect Source System after Transport (RSTRAN 514) but couldn't resolve the issue.
    We basically want all the Objects in the BQ1 (Test System) showing the Original Source System as BD1 (Development System) but only the DataSources and it's connected Transformations and DTPs are originating from the BQ1 (Test) System itself (The Transformations when Transported from BD1 to BQ1 are Transported with a different Technical Name which is very strange).
    Had anyone faced similar problem and if so, what was the effective solution implemented.
    Any help in this regard is very much appreciated.
    Thanks in Advance.
    Best Regards,
    Chandu.

    It is resolved by our Basis.
    Thanks,
    Chandu

  • Conversion of source system after tranport

    Hi
    Im planning to to transport BI-Obejcts from DEV to QA . Where can i give
    'conversion of sourcesystem after transport' and how can i give them.
    can i give in DEV or QA .please let me know
    kumar

    Hi Ravi,
    Log into your QA system. Go to RSA1 -
    > Transport connection. Click on the icon Source system conversion or just press F8. Click on new entries in the next screen. Here just maintain the source system conversion. For example in Dev if the R/3 source system name is R3DEVCLNT100 and in QA it is R3QACLNT200 then in the original source system field enter R3DEVCLNT100 and in the target source system field enter R3QACLNT200. All the source system dependent objects like datasources, transformations etc which are assigned to R/3 dev system in BW Dev will be assigned to R/3 QA system in BW QA.
    Similarly maintain entries for all other source systems defined in BI. Hope this helps.
    regards,
    Sumit

  • Wrong conversion of source system after transport

    Hello,
    We ve got a a transport problem in our 3-3 Landscape. Connections for extraction are only between same systems ( f.e. dev to dev)
    BI Dev         BI Test       BI Prod
    R3 Dev         R3 Test      R3 Prod
    The conversion of source systems is on the BI test:
    BI Dev becomes BI Test
    R3 Dev becomes R3 Test
    The conversion of source systems is on the BI Prod:
    BI Test becomes BI Prod
    R3 Test becomes R3 Prod.
    With this it tells me the after transport (BI Test to BI Prod) of objects with source system assignement that the R3 Dev System is not known.
    The transport before from the BI Dev to BI Test worked well without any problems.
    We`ve got the BI Test and the BI DEV on the same host.
    Has anybody got an idea what is wrong?
    Thank you folks.

    It must be R3D (dev system)
    Something like following should be maintained in production
    R3DCLNT100 <u>R3PCLNT100</u> [Assuming R3PCLNT100 is your production system]
    Don't forget to assign points,
    -jayant

  • Deletion of source system after an upgrade : consequences ?

    Hello,
    I'm a sap basis guy.
    We have a SAP BI 701 sytem mapped to our 4.7 Non Unicode source system.
    I have now perfromed the unicode migration and upgrade to ECC6 of the source system on another server.
    It means now, that I have two sourtce systems with exactly the same SID, and logical name.
    Sicne the BI connexion in RSA1, is based on the logical system name , I have no ther choice than delete the old
    source system, and recreate it with the same logical name but different connexion parameters (hosts, ...) and differentversion (
    I have talked with the BI team, but thnigs are quite unclear about the consequences of deleting a source system in RSA :
    Do all Transformations/ Transfer Rules between DataSources and targets are deleted ?
    Does it mean that they have to be manually recreated after the new source system has been recreated ?
    Is there any workaround ?
    Thank you in advance for your help.
    Regards.

    Hello,
    If you do not save the source system dependent objects to a transport request before you delete the connection then the objects will be lost , you can avoid this by saving the objects to a transport request and then release the transport before you delete the connection and import it in the new system, the steps in general are below:
    RSA1
    Transport Connection
    Button 'Collection mode'  set to 'start manual collection'
    Press 'Source system assignment' button (it's the one left of the
    'Request BEx' button)
    Select the source systems you want to save the transfer rules for
    Continue
    Button 'Grouping' set to 'Save for system copy'
    At the left border click on 'Object Types'
    Extend tree  'Source system' LSYS
    Double click on 'Select objects'
    Select the source systems you want to collect objects for
    the source system is now displayed in the right box
    Press collecting button ('gather dependent objects')
    this may take a while
    Right click on the root of the tree and select
    Transport all below
    Expand the whole tree and check if there isn't an object which is locked
    by an other open transport request !!
    (the column 'Transport request' has to be empty (BEFORE deleting the corresponding source system
    connection!)
    Best Regards,
    Des

  • Mapping of Quality System (Source System) after the Transport

    Hi,
      We have two quality source systems like 300,400 in sync with the development ,to extract the data .    I am transporting Transfer rule mapping from the development .After the transport to Quality , the changes are reflected in 300 . But I want to change it from 300 to 400 i.e.Transfer rule mapping should be reflected in 400. What is the transaction code used to change this mapping in BW System?
    Thanks for your time.
    Thanks & Regards,
    Raja

    Raja,
    When you transport - you have a transport mapping in your dev system that tells BI which system connects to which system in the QA system for instance
    FLAT_FILE in DEV could be Z_FLATFILE in QA - accordingly the datasources are mapped. Also the transfer rules are source system specific which means that you change the source system - the transfer rules will have to be recreated.
    Instead what I am asking you is to maintain the mappings for client 400 in DEV and then maintain the mappings as 400 - 400 in the qa system and then transport the same. If your dev systems are linked to QA300 and your mapping says QA400 the same will hold good.. however if you have QA300 in dev to be sent to QA as QA300 and then change the source system .. it will not work since this will be seen as a source system change and you cannot change the same. You could try BDLS and try changing the logical client name ( I am not sure if it is BDLS ) or change the RFC connection parameters in SM59 but am not sure if it would work....

  • Change source systems after a production to development copy

    Hi all, does anybody have a detailed document on all changes for source systems to work correctly after a P to D copy.
    Thanks

    Hi,
    Here you will find all the details go through the link below
    http://help.sap.com/saphelp_46c/helpdata/en/2e/d9530294f911d283d40000e829fbbd/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/EN/26/4b0d0930034b73aa3332ddc8c75e9d/content.htm
    It may help you
    Regards,
    Marasa.

  • Quick question on conversion of source system after transport.

    hello all,
    I have transported all my objects from dev to QA in BW (and same in r/3). Now i want to let it all go to production environment. So do I have to go in rsa1 of BW prod system and make a entry in there ?
    In my BWQAS i have an entry in there
    Original source system               Target source system
    R3DCLNT100                               R3QCLNT100.
    So when i make the entry in BW prod environment what should be source system R3D or R3Q?
    Thanks,
    Raj

    It must be R3D (dev system)
    Something like following should be maintained in production
    R3DCLNT100 <u>R3PCLNT100</u> [Assuming R3PCLNT100 is your production system]
    Don't forget to assign points,
    -jayant

  • Can't found source system after successfully created in RSA1

    Dear expert,
    I'm afraid that my orignal post will drown..
    I put here for the new quesiton of my new upcoming issue
    Background:
    We are doing the ECC system refresh (ECC PRD to QAS)
    ECC QAS has connection with BW QAS
    The next step is to restore the Q23(ECC) source system in QBW RSA1
    it is somehow missing, so i try to create it
    I created it by clicking on the icon of "SAP" then it will pop up a "create" tab It takes me quite a long time around half an hour. Finally it shown in the end of RSA1 screen , Q23CLNT0** source system is created successfully.
    BUT the strange thing is i refresh the RSA1 screen , i can't not find the Q23 apears in the folder of SAP!!!
    And i try to recreate , it shows in the end " Q23CLNT0** "already exist (see attached), how could it be , can anyone come to help? thank you! Best regards,kate

    Hi,
      Check in BW tab , it may be mistaken created there .
    if it is so, delete it and recreate in SAP tab.
    Regards
    Yugandhar T R

  • Source System Does Not Exist - Transport Problem

    Hi
    We have the next Landscape in BW 7.0 (Netweaver 2004's)
    LRDCLNT300     is R3 DEV
    LRQCLNT700     is R3 QA
    LBDCLNT100     is BW DEV
    LBQCLNT700     is BW QA
    The connections are
    LBDCLNT100  (BW Dev) use as source system        LRDCLNT300  (R3 Dev)
    LBQCLNT700  (BW QA) use as source system        LRQCLNT700  (R3 QA)
    In RSA1->TOOLS -> Conversion of Logical System Names
    In Conversion of source system after the transport we have these entries
    Source System                    Target System
    LBDCLNT100 (BW Dev)         LBQCLNT700 (BW QA)
    LRDCLNT300 (R3   Dev)         LRQCLNT700 (BW QA)
    But when we transport an order from BW DEV to BW QA show the error "source system LRDCLNT300 does not exist"
    Never made the conversion of source system after the transport.
    Can you help us please.

    Thanks Edwin
         I create a RFC for LRDCLNT300 (R3 Dev) in my BW QA system (Target System).
    I try an order again but it didn't work, also I try to check 7.0 checkbox but I got the message "No entry exists for original source system LBDCLNT100 for 3.x object"
    and I have to uncheck again.
    I still have the same problem the objects are associated to R3 Dev, never make the conversion to R3 QA.

  • Issue in while connecting Source system

    Hi All,
    I mistakenly Ran the function module RSAP_BIW_DISCONNECT in BIW, I suppose to run this FM in Source system side,
    We observed that Source system in RSA1 (BI) has been deleted), and also one record from the table RSBASIDOC (which is from source connection) has been deleted .
    When I try to create he source system in BI, after entering logical system and ALEREMOTE and BWUSER logins, it was asking me to login to source system, after entering the details,
    A pop-up message:
    RFC destination already exists in source system
    Do you want to use this destination, check, or
    cancel source system connection?
    options: USE, CHECK and Cancel, -> We pressed USE
    Then it came back to RSA1 screen and a pop-up message
    Connection BA is used in the ERQXXXX
    source system as a connection BWQXXXX to BW.
    Do you want to delete this connection in the source system?
    Connection Is Restored After It Has Been Deleted Successfully
    Options: Delete, Do not delete.
    When we go for Delete : It is saying that "Error in source system ERQXXXXX"
    Thanks in Advance,
    Teena

    Hi,
    Please find the link which might help you:
    http://help.sap.com/saphelp_nw70/helpdata/EN/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
    Best Regards,
    rajani

  • Inbound idoc  error in the source system

    HI,experts
    I manually configurate the idoc type ,message type ,etc between the BW system and r/3 source system when the automatic program encouters errors. And the communication between BW and source sysyem  seems ok since the source system is activated successfully in BW side.
      But when I check the inbound the idoc in source system  after i triggerred a full load for the datasource 0FI_GL_4,an error occurs in the inbound process in R/3. There is no  control information in the idoc which message type is RSRQST.
    how can i figure this issue out ?could anyone help me ?

    HI,ALL
    Thanks for your replies and documents.
      Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
      How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

  • Add new source system to BI

    Hello,
    Our requirement is to load data from a different R3 client to which we dont have a connection yet.
    The idea is to create a new connection but keep the existing one.
    Is there any automated tool to do this? We would like to avoid the manual creation of all infosources and transformations from the new source system, but to copy them from the existing one.
    We found that there is a tool for replacing the current source system with another one (BDLS), but we just want to create this new one in paralel with the current source.
    Thanks!!
    Pablo

    Hi,
    what you can do is, create a transport request containing all source system related things like the infosource/datasource assignment, transfer rules... and import that transport back into your dev system. Before the import you should maintain the settings for source system after transport accordingly.
    Siggi

  • Restore source system without replication

    Hi,
    Normally one would do a restore of a source system after it has been refreshed with RSA1.
    The "downside" is that it also do a replication of the datasources.
    We want to split the procedure and do the restore of the source system without replication and the replication itself separately. Are there any transactions, FMs, reports, ... to achieve these tasks separately?
    Eddy

    Eddy,
    I found out about that, but i never tried it, it is an interesting program, but i don't know how if it will ask whether a datasource need to be 3.x or 7. I guess if you execute as a background job it will not ask.
    Regards,
    Jorge Diogo

  • Source System mapping for BW configuration transport

    I create a data model mapped to the testing source system i.e DEV201 but the configuration source system is DEV200.
    Now i am about to transport the BW configuration to BW-QAS , I am wondering if I have to assign the data model to the config. source system(DEV200) or i can created a transport request attached to DEV201 ?
    Is there any concern on this ?

    Hi,
    I'm not clear your system landscape. Do system landscape like that:
    BWD (BW development) --> DEV201
    Now you want transport all objects to BW_QAS with connected to DEV200.
    If this is true, you do like this:
    - On BW_QAS: create source system (DEV200). Maintain conversion of source system after transport (Original: DEV201; Target source system: DEV200).
    - After that transport your modeling from BWD to BW_QAS.
    Hope this helps
    BR
    TRUC

Maybe you are looking for