Deleting a Source System Connection

Hi all,
We made some updates to a QA source system and when we try to do a 'activate and replicate datasources', errors are being thrown out. So, we decided to delete the connection and recreate the connection. I have a few questions:
1) If I right click on the source system in BI and click delete, it is prompting for a transport request to delete transfer structures. What are the steps to follow in deleting the source system? How will I be able to rebuild the transfer structures?
2) I deleted a couple of transfer structures. Can I roll it back? If yes, how
Greatly appreciate your help.
Anita.

instead try to trouble shoot the issue with the source system creation.
i don't beileve you can easily recover a deleted transfer str / rule without recovering from a backup or transporting it again from dev, once the sourcesystem issue is resolved
i believe this source system definition has been there for a while therefore just deleting it outright is not recommended for a lot of reasons,,,,,,,

Similar Messages

  • Error Deleting Source system connection

    hi
    I was trying to delete a source system from BIW. ( Wanted to start afresh).
    But while doing that I get this error:
    "Incorrect input for activating transported shadow ipacks"
    Can someone tell me how to correct this information.

    Hi Murali,
    this problem has been fixed with SP20, BW 3.0B. Please see SAP Note 709581 for details.
    Regards, Klaus

  • Source system connection issues

    Hello BI Experts,
    We had issues with the source system connection - from our BI system (NW 04s) to our R/3 system (ECC 6.0) .
    From RSA1, when we right click on the R3 source sytem and do a "Check", it was erroring out: "Error in source system <Logsysname1>". This Logsysname1 was different one from the actual R/3 system's Logsys name (Logsysname2) .
    To Fix this, we restored the connection by selecting the (R/3) Source system and right click and "Restore".
    After providing the passwords for the RFC users, the system again asked "The Connection <XY> is used in the <Logsysname1> Source system as a connection." And we selected the "Delete" option here. Then in the Logon screen to R/3, we provided the administrator user Id and password.
    Once the source system connection is complete, we checked the connection as mentioned above and the "Source Sytem connection is OK" now.
    (1) But now, in the transaction RSA1, the R/3 system is displayed under "BI" instead of "SAP".
    (2) When we asked our BI consultant to check the dataloads, he encountered an error: "No transfer structure is available for InfoSource <X> in the Source system. Errors in Source system".
    How can we bring the R/3 system under "SAP" now?
    If we delete the R/3 system (which is listed under BI) and recreate under "SAP", will the transfer rules will also get deleted?? How to avoid this issue?
    Please advise.
    John
    SAP Basis.

    Hi,
    Please make sure that you have followed the below steps while creating the Source System
    1.     In the initial screen of the source system, choose Tools ® Administration ® User Maintenance ® Users and create a background user with a password and the authorization profile S_BI-WX_RFC.
    2.     Define the RFC destination parameters for the SAP source system in BW. To do this, choose Tools ® Administration ® Administration ® Network ® RFC Destinations in BW.
    Enter the information taken from the source system on the server name.
    u2022     Application server: pswdf090
    u2022     System ID: IDF
    u2022     System number: 90
    The destination name has to correspond to the logical name of the source system that you entered for the process step Define Logical System in the implementation guide for the source system. For user and password, enter the background user that you created in step 1.
    3.     Define the RFC destination parameters for the SAP BW in the source system. To do this, select Tools ® Administration ® Administration ® Network ® RFC Destinations in the source system. Enter the server name information taken from the BW system.
    The destination name has to correspond to the logical name of the BW system that you entered in the process step Define Logical System in the BW Customizing Implementation Guide. ALE communicates using the name of the SAP Business Information Warehouse that you defined. The defined name represents how the SAP Business Information Warehouse is identified. For the user and password, enter the background user that you defined in the BW Customizing Implementation Guide under Business Information Warehouse ® Links to Other Systems ® Link Between SAP Systems and BW.
    4.     Test both RFC destinations with the functions Test ® Connection and Test ® Authorization.
    If an error occurs during the authorization check, the background user is not permitted in this client and with this password. If an error occurs in the connection test, it means there is a network problem.
    5.     In the BW Administrator Workbench choose SOURCESYSTEMTREE ® Root ® Context Menu (right mouse button) ®Create and select the radio button for the manually creating an SAP source system.
    6.     Enter a description for the source system and the logical name of the source system that you entered for the process step Maintain Logical System in the source system implementation guide.
    If you still have any issues, let us know.
    Regards,
    Yogesh.

  • Not able to change source system connection

    Hi, I have problems changing a source system connection from BW. BW is already connected to source system A, which is closed down, and I'd like to connect BW to source system B, which excists and can be accessed. I have tried to use BDLS, but get the message that System B already excists (new one). I try to delete it (Change view logical System), but am not allowed to do this. I get the message "must not be deleted, first delete from distribution model." And thats where I am stuck. Can anyone guide me on my way?
    Regards E!

    Comment to the last answer:
    When I try to delete in SALE I am told that the source system also excists in the Distribution Model (CUA) and can therefore not be deleted. It must be deleted in the distribution model first. I find CUA at BD64. Looks like this is the connection to Solution Manager. What are the consequences for deleting the Source System here? And will it hlep me to solve my problem, which is that I can't change my connection from Source System A to new Source System B?
    Regards E

  • 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

  • Refresh of BW System without deleting the source system

    Hello experts
    I want to know, is it possible to refresh BW system without deleting the source system.
    That means I just do the renaming via BDLS and reconnect.
    If I do so, do I have a post refresh activities.
    According to OSS note 886102  and 184447, there are 3 scenarios:
    Scenario A: You want to copy the entire system infrastructure connected by the BW source system connections (that means the entire system group).
    Scenario B: You want to copy a single BW system of the group, the sourcesystem is not copied.
    Scenario C: You want to replace a single sourcesystem of a BW-system with another system using a database or client copy (Example: Refresh of the OLTP consolidation system by a copy of the OLTP production system). The BW system is not copied
    Assuming I use Scenario A, can I refresh BW system without deleting the source system.

    Hi:
    The primary source of information is the how to paper on this topic:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    YOu are correct, you can refreh the BI system without deleting the source system.
    Thanks for any points you assign (after all, I wrote the paper!).
    Best Regards -
    Ron Silberstein
    SAP

  • BI Source System connection to ECC

    Hi experts,
    I have a BI 7.0 fresh install and I'm trying to connect ECC 6.0 client dev100 (golden client) to BI so I can activate BI Content. However, the client 100 goes to the BI folder instead of the SAP folder when I create source system in AWB. Is this normal behavior?
    I have another system client dev200 and it goes inside SAP folder when I create source system. I'm just wondering if this has something to do will my error in BI Content activation. Key figures and characteristics are activated but not DataSources, Update rules, and InfoPackage.
    Your comments are greatly appreciated. Thank you

    Hi JD,
    I think the source system connection must have been made in Bi folder. basically even BI folder shall contain BI system but if ECC system connection is made in this folder it shall not make any diffrence. You must be getting the datasources as of ECC only after replication.
    Regards,
    Wrushali
    Request for points deleted. Please do not ask for points in the forum.
    Edited by: Vikram Srivastava on Jun 22, 2010 1:56 PM

  • Deletion of Source system

    Hello,
    I need help in deleting any links that exist for an old R3 system. We have migrated our source R3 system which was called SP1 to another system called SP2. Now we have datasources, DTP and update rules pertaining to the old system that we would like to delete. I tested out an option to delete the source system in the workbench by clicking under  the Source system , choosing the one I wished to delete and right clicking on that and choosing Delete. I got a warning saying that its not possible to delete because the RFC connections are no longer available, which is true. I chose Ignore in the message window that popped up and that led to all the datasources, DTP and infopackages getting deleted. This seems too good to be true that we got rid of all links to the old system . What I am wondering is whether this method causes some other important data to vanish as well. Is there also a better way to delete all links to the old system.
    Regards,
    Jaya

    Hi Jaya
    As you said there is no connectivity with the source system, then you are no more using the Datasources from that source system.
    Ensure that you are not using the datasources in your regulary used Infosources.
    If you are using then they me be set to inactive.
    As you said youa re not at all using that source system you can delete that.
    Regards
    PBI

  • Deleting the Source System

    Hi All,
    Can Anyone the consequences on deleting the source system in BI and steps to re-build once again, as i need to take up the activity. Generally what can be issues that crop up when deletion takes place..
    <removed by moderator>
    Regards,
    Madhav
    Edited by: Siegfried Szameitat on Dec 12, 2008 11:28 AM

    Dear Linturi,
    believe you trying to delete the current R/3 source system and trying for SAP BI my self source system right?
    If yes
    We can very well dete the source system
    The impact would be in th efollowing ways
    You will loose entire datasources,transfer rules and PSA related to that particular source system and it will be Major impcat on you Bi system which is not at all preferable untill unless you are really no more use of the R/3 source system and its configured with any of the bi pass clients.
    Coming to BI Myself souce system : Which is purely realted to the DATA MART Loadings and its also a similar like R/3 source system connection you have to give ALEREMOTE passwords and serve ips.
    Hope this helps u...
    Best Regards,
    VVenkat..

  • What 's result of deleting a source system?

    what happed if I delete source system?
    What's the difference between spurce system

    Hi Shen Peng
    I believe you trying to delete the current R/3 source system and trying for SAP BI my self source system right?
    If yes
    We can very well dete the source system
    The impact would be in th efollowing ways
    -- You will loose entire datasources,transfer rules and PSA related to that particular source system and it will be Major impcat on you Bi system which is not at all preferable untill unless you are really no more use of the R/3 source system and its configured with any of the bi pass clients.
    Coming to BI Myself souce system : Which is purely realted to the DATA MART Loadings and its also a similar like R/3 source system connection you have to give ALEREMOTE passwords and serve ips.
    Hope its help you...!
    Cheers
    K M R
    Assigning points is the only way of saying thanx in SDN***
    >
    Shen Peng wrote:
    > There are two client, 800 is the BW system, has lots of data, 810 is ERP system, not too many data.
    > If I connect to the BW source system to BW, it is the same way with SAP source system?
    >
    > What's the difference between a SAP source system and BW system?

  • RSA1 - Source system connection : Change in logical system name

    Dear friends,
    Can you please tell me how can i change the logical system name for a source system connection.
    There is no change in source system & source system connection check works well, just we have decided that from current logical system name SID_100 should be changed to SIDCLNT100.
    Can i do this by running BDLS in BW for RSBASIDOC table from SID_100 to SIDCLNT100 ?
    thanks
    ashish

    HI Sunny,
    This is not the same problem, may be similar though..i am not getting a way.
    let me describe u in a bit more details.
    Currently, we have a working source system connection to a system SID_CLT.  there is no change in source system.
    now, can i change this system connection technical name from SID_CLT to SIDCLNT*** .. 
    thanks
    ashish

  • Deleting a Source System in BW Prod

    Hi Guys,
    I am trying to delete the assignment of R/3 Production as a Source system in BW Prod but the system is not letting me- informing that:
    Package ZBWD does not exist- choos display object or cancel.
    The reason I am doing this is at present the source system is assigned to Infoobject 0WBS_ELEMT but I want to assign the 0WBS_ELEMT_ATTR & 0WBS_ELEMT_TEXT datasources to the 0WBS_ELEMT_ATTR & 0WBS_ELEMT_TEXT InfoSources.  I would like to un-assign this datasource from 0WBS_ELEMT and assign to the InfoSources stated above. 
    I am trying to bring in WBS Element master data but found in Dev when I bring it in through the infoSources it is available in BW but through the 0WBS_ELEMT infoObject there is no data in the masterdata tables.
    How can I delete this source system assignment in BW Prod?
    Thanks
    Depesh

    hi Depesh,
    i think system won't let you delete source system assignment in prod if it's closed for modification
    (transaction scc4), if you really need to do this directly in prod, please ask basis open awhile,
    have you tried delete the source system assignment in dev and transport to prod ?
    regarding package zbwd not exist, check in prod if package zbwd exist,
    transaction se80, choose 'package', type in zbwd,
    it will display the package or ask to create new if not exist. transport package zbwd from bw dev if it's not exist in prod.
    hope this helps.

  • How to delete a source system in BW?

    Hello All!
       Can anone please  inform me about the procedure to delete a source system or inform me in which document i can find this information. Actually i wish to assing my newly installed BW3.5 system to a new logical system (i.e) its currently assigned to some other logical system where it has ME as default source system.  to change the logical system we need to delete all the source systems in the old logical syste. So please explaing me how to delete the source system Myself(current BWsystem). there is no data and no data sources existing in the system its abosolutly fresh.
    Thanking you for help in advance
    with regards
    Ashwin Kumar Gadi

    Hello Roberto!
        Thanks for ur response. But there bo such delete option  available under the context menu for the source system for the Myself source(current BW). only change buton appears but when we click that it say changes are no posible. Is the any other way to delete it manually.
    with regards
    Ashwin

  • Restoring the source system connection in BW

    Hi all,
    I’ve been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine.  But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
    1.-  Basic type ZS 118 does not exist.
    2.-  The following error in the source system:
    3.-  Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
    The description in each error is:
    Error #1:
    Diagnosis                                  
        IDoc type ZS 118 could not be found.   
    System response                            
    Procedure                                  
       Please enter an IDoc type that exists. 
    Error #3:
    Diagnosis                                                                  
        Incorrect IDoc type ZSAB023 in the ALE definition of the source system.                                                                               
    System response                                                            
        Error when sending data to BW.                                                                               
    Procedure                                                                  
        Enter IDoc type ZS 118 .                                               
    They told me this IDocs are created automatically by the connection. Is that true?
    How can I fix this, so that I can restore my connection and do the data extraction?
    Thanks a lot
    Regards,
    Vic

    Hi Victor Tostado
    1.- Basic type ZS 118 does not exist.
    Type Transaction WE30. Check iDoc types Obj. Name :  RSSEND -> press F7
    a.) Enter 'RSSEND' in the Obj. Name field.  You will see an entry similar to the one below:
              RSSEND                          Data transfer from the source system (template)
                    [-]  E1RSSH               Data transfer IDoc: Header information
                             [+]  E1RSHIE    Data transfer Idoc: Hierarchy header information
                                    E1RSTXT   Data transfer IDoc: Texts
         b.) Enter RSREQUST in the Obj. Name field.  You will see an entry similar to the one below:
                RSREQUST                    Data request to the source system
                     [-]  E1RSRH               Data request IDoc: Header segment
                             [+]  E1RSRHI     Data request IDoc: Hierarchy
                             [+]  E1RSRTX    Data request IDoc: Texts
                             [+]  E1RSRMD   Data request IDoc: Master data
                             [+]  E1RSRIS      Data request IDoc: InfoSource
         c.) Enter RSINFO in the Obj. Name field.  You will see an entry similar to the one below:
                RSINFO                         Info IDoc
                    [-]  E1RSHIN             InfoIDoc: Status segment
                            E1RSPIN            InfoIDoc: Data packet segment
                            E1RSEIN            InfoIDoc: Error segment
    d.) If any of the above do not exist, contact your BASIS Team.
    2.- The following error in the source system:
    Type Transaction SM59. Maintain RFC destinations
    a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
    3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
    Type Transaction WE21. iDoc Processing Ports.
    receivers port is not available go to WE21 -> create port
    a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
    I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
    Enter RSBASIDOC Print out copy of all entries in table.
    II) Type Transaction SM30. Msg Types & Assignment to iDocs
    Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
    Regards
    Sangram Sutar

  • Source system connection in IDES ECC6.0 Version

    Hi experts,
    I have ECC 6.0 in our Company, ECC 6.0 version also have BI integrated with ECC6.0 version.
    Now my question is that is it possible to connect r/3 with BI in the same server, we have two application server, if yes Please let me know how to achieve it without changing the logical system name.
    because if we change logical system name then it gives a error message that logiacal system name has been changed for this system.
    any help in this regard would be apprecicated.

    Hi,
    One server can have several systems but with different client and with different logical system anem. Now if logical name is same, they source system connection is not possible. Logical system name can be changed in t-code SCC4, but please do consult basis person before doing this as this is bit sensitive.
    Regards
    Pankaj

Maybe you are looking for