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

Similar Messages

  • Source system restore - Source system does not exist

    Hello friends,
    We have a problem. Now we have a new test system QA2. From BW system source system connection was configured for older test source system QA1.
    We needed to route this source system to new system. I tried with changing RFC of QA1 to QA2 details.
    Now, when i check RSA1 source system Check for QA1, i get this error :
    Port 'A000000103 ' of type 'ALE ' does not exist
    No destination exists to source system QA1
    I can see this source system in RSA1 in BW. However, in WE21 port is not available now.
    Please suggest.
    I do not have to lose transfer rules/PSA tables..etc.
    thanks
    ashish

    I get this when i try to restor connection :
    Source system does not exist
    Message no. RSAR175
    Diagnosis
    You have specified that you want to restore source system QA2. This source system is not known in BI.
    System Response
    The source system is not restored.
    Procedure
    Recreate the source system.
    If the source system should be known to BI, the name of source system QA2 may be incorrect. Rename the source system and try the function again.

  • How to load master data from 2 source system without using 0logsys as compo

    Hi Gurus,
    I am working on a project which has 2 source systems.
    Now I have to load master data from 2 source systems without making 0LOGSYS as compunding attribute. Because all the objects which i want to use compunding attribute are reference objects for lot of other info objects. So, i dont want to change the business content objects structure.
    So, please help me out providing logic.
    thanks in advance
    Peter.

    Hi Peter,
    Can you brief me how did you resolved your issue?
    Regards
    Utpal

  • Create source system without cross client config

    The SAP-Help URL given below explains the prerequisites for linking BW to a source system. One of the requirements is that the source client is open for cross client configuration.
    Is there a way to create the source system without having cross client rights in each source client?
    I understand that the client only has to be open while it is being linked to the BW system but I would prefer to avoid opening the client at all.
    Help URL:
    http://help.sap.com/saphelp_nw04/helpdata/en/80/1a61e5e07211d2acb80000e829fbfe/frameset.htm

    Hi ,
    You can perform the following check :-
    1) Check if BI DBMS and Source DBMS are same. If not then you have to Install DB Client for that Source then this error should not come.
    2)Check if DBSL(Data Base shared Library is installed in BI for this Source. If not Kindly Install that in BI server.
    Kindly perform these operations and lets see what happens.
    Regards,
    Amit Kumar trivedi

  • Hello, I have an iPod touch 4 generation. I have a problem that my PC is broken and I later forgot my password. How can I restore the system without a PC. Because I have receipts from the rest because I POD and

    Hello,
    I have an iPod touch 4 generation. I have a problem that my PC is broken and I later forgot my password. How can I restore the system without a PC. Because I have receipts from the rest because I POD and

    You need a computer with iTunes installed to regain use of your iPod.  Unless you have the iPod backup file from the syncing computer all you can do is to restore the iPod to factoery defaults/new iPod.  You will also need to place the iPod in recovery mode is you restore the iPod on other than on its syncing computer.  For reoverymode see:
    iPhone and iPod touch: Unable to update or restore
    Remember the passcode is a security feature.

  • Error after restoring source system in SAP BI side

    Dear all,
    i am getting issue while restoring sap source system through sap bI
    "Connection LA is used in the 'LD1CLNT010'
    source system as a connection 'LB1CLNT400' to BW."
    Do you want to delete this connection in the source system?
    Connection Is Restored After It Has Been Deleted Successfully
    it asked me delete or do not delete
    what to do next

    hi,
    you need to ensure that source system to BW is restored properly .
    check in TABLE RSBASIDOC in BW through transaction se11/se16.every source system entry must be here with repect to BW.
    If source system entry is missing then there are issues.Normally BASIS Team makes entry.restores system
    you cn also check in RSA1-->SOURCE SYSTEM.Here u must find your R3 system name.
    hope it helps
    thanks,
    nilesh

  • Problem restoring source system connection post BW system copy

    Hi.
    I am having problems restoring the R/3 connection in our BW system.
    This is the scenario.
    We need to move our BW production system onto a new system, but keep both BW connected to R/3 production for testing etc until cutover to our new BW system.
    Basis performed a system copy and restore of BW production to the new system and ran BDLS.
    When I try to restore the R/3 connection via RSA1 I am getting the following error at the end-
    "A connection already exists there ......." and the message refers to our current/live BW system. The options are to delete the existing or not delete. I have only chosen "do not delete" and therefore the connection is not restored. My concern is that if I choose "delete" this will damage my existing connection between R/3 and the currently live BW system which is we cannot afford to do.
    In our newly copied BW system we are using the existing R/3 SM59 (from system copy), and in R/3 we have created a new SM59 for our new BW system.
    It seems from the error message information that is complains that BW sent R/3 some sort of ID (value = "WS") and that is already taken by the existing BW system. I tried to find where and what this WS value is referring to and the only thing I have found is that in table RSBASISIDOC "WS" is the suffix for transfer structure for that R/3 system. ??? Not sure if this is related for what.
    Thanks for any help

    Hi ,
    Please check with basis or if you can ,then try to restore the source system in BI/BW.This should correct the  inconsistencies between the two systems which is being caused by different Idoc types
    Also check the table RSBASIDOC in the BI system and compare this to R/3 system ,the "basic type" field should be same.
    A restore should work,it has always worked for me.
    Regards
    Amit

  • Restore source system

    .after the Client copy to the source system I want to  restore the source system what hapens to the objects which already migrated to BI 7.0  and all the transformations and DTP's created.
    Partner profile and IDoc settings

    you may wish to check this note
    Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
    For more insights-
    Client Copy / Source system copy
    Note 184322 - Procedure after DB copy of BW source systems
    Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
    Note 771209 - NW04: System copy (supplementary note)
    Note 89188  - R/3 Source System Copy
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    Hope it Helps
    Chetan
    @CP..

  • Swap R3 source system for BW without recreating transfer rules

    Hi, All,
    I am facing an interesting situation. The team would like to retire an R3 system which is the source to our BW development environment. I need to replace the old R3 source with another one. The BW development environment is also the source of the transport path.
    Is there a quick way to swap out an R3 source system without recreating all the transfer rules/infosources/infopackages which are tie to the old system?
    Thank you in advance for your help.
    Chimei

    Hi,
    In BI 7.0, we are trying to repoint ECC 6 Dev system in place of R/3 Dev.  Ran BDLS which converted some tables but not all and ended with errors.  Does anyone know how to manually correct these entries?  Is there a program to independently correct the tables?
    Regards,
    Ramesh

  • Source System - Deletion issues

    Hi everyone,
    I´m facing an upcoming problem in my BI 7.0 project and I would like to minimize the consequences of the situation as following:
    The Basis team, for some reasons, is going to eliminate in DEV the client (eg. 200) that I have all my connections set with BI and will create another one (eg. 230). The same thing is going to happen with QA environment (300 -> 330). Production will remain the same (400)
    What would be the best way to reconnect all Infoproviders and Infoobjects with this new source system ? Logically, I will have to put everything in a request and sent it later to QA to restore all the connections in this environment. The major work will be done in DEV environment.
    I just want to know if there´s way to reconnect everything not manually. I have both 3.5 (Master Data) and 7.0 (Transactional) Datasources.
    Thanks in advance,
    Fábio

    Hello,
    I believe what you can do is following the steps in the PDF "How To - System Copy in SAP Business Intelligence System Landscapes"  https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
    I did not require a transport either.
    I had a similar action occur when my R3 QAS system got replaced, it had a new Physical and Logical name as well as a new client number.
    I followed Section 3.7 "System refresh of source system without copying the SAP BW system in parallel (LSN "Option 2")"
    We were on R3 4.6c and BW 3.5 at the time.
    Maybe that will help you!
    Nick
    Edited by: Nick Bertz on Jan 12, 2009 4:08 PM

  • Error while creating source system in BI: Modification not possible

    Hi All,
    We are about to move to production, and therefore it's necessary to create in BI the source system related to our ECC (R/3). While trying to perform this action from BI side we received the error message:
    SAP system has status 'not modifiable'. Because of this, and following with known consultants practices we've changed the client to customazing but it still not working although the message at this time is: Changes to repository or cross-client Customazing are not permitted. We have also verified transaction SE06 but it's not possible to change the Cross-Application Component to Modifiable. 
    Did someone face with this same problem before?
    Thanks to all in advance,
    Regards,
    José.-

    Hi Rick,
    I really appreciate your quick response. We followed your recommendation and could create the source system without problems. Thanks once again!
    Best Regards,
    José.-

  • R/3 Source System Check in BW

    Hi ,
    We had a BW client Copy from Production to QA and DEV system. Last week, When I am trying to restore source system connection to R/3 after client copy by creating PORT and PARTNERPROFILES in BW system. I could restore connection in BW Dev but not in QA.When I tried to check the source system in RSA1 then I am getting an error that USER IS LOCKED. The remote logon test is going sucessful and when I replicate I could replicate every thing successful.  I checked the user(ALEREMOTE) in R/3 and the status of the user is not locked.
    Thanks in Advance,
    Varma.

    Hi,
    Did you check the ALEREMOTE in your BW QA?  The best to test out is to go into SM59 of both the system (BW and R3) and try the logon.
    Hope this helps,
    Cheers,
    Gimmo

  • Copy Transferrules from one source system to another

    Hi everybody,
    we're uploading data from nearly 25 sourcesystems (including separate systems and systems with more than one client to extract from) via flat-file. The source-system exports data to a shared file directory and the bw-system reads it from there. Though this results in only <b>one</b> transferrule for all source-systems, it keeps generating problems every time upload is due.
    Somebody had the idea to switch to 'standard' R/3->BW method of data staging, using generic extractors and so on. But this will result in <b>25</b> transferrules which, I'm afraid, have to be set up and maintained seperately. As there's quite some coding in the rules (the transfertructure in fact has 241 fields), flaws are for sure!
    We know the trick of exporting a transferrule, changing the source-system-mapping and re-importing the same transport-request. That can be used to copy to one or two other systems, but not for 25.
    Does anybody know another way to copy a transferrule from one source system to multiple other source systems?
    Looking forward to your answers
    Thanks and Regards
    Robert

    Hi Ralph,
    I don't like that methode. Importing the same transport 15 times, each time changing the source-system mapping and making sure, that source-system gets the changes seems to be a huge source of errors, which will be hard to find.
    What do you think of the following idea to solve the issue a totally different way:
    All transfer-rules directly connected to the source-systems are stripped of all Coding, so there is a plain 1 by 1 transformation including 0logsys.
    The InfoSources attached all lead to one ODS-Object, which has the only purpose to collect the data from the source-system without any transformation. So some fields a filled by a system and other fields maybe not.
    The coding specific for source-systems is moved to transfer- / update-rules from that ODS-Object to the original ODS-Objects / Cubes and the "collecting" ODS-Object is emptied after every loading process.
    This will result in a single point of change. It will be quite a huge program (maybe in startroutine) but it's the one and only point, where changes and corrections have to be made.
    Regards
    Robert

  • Best Way to Change Source System Client

    We initially had a ECC source client for BI as 35.  But over time, we suffered with good test data because the ECC team use client 15 and not 35.  We want to change BI 7 to use client 15.  I have created a new source system in RSA1 for Client 15 but when I try to delete client 35 and /or change the source client on a datasource, all the data mappings are deleted!
    I would really appreciate any advice or information on the best way to change the source R3 client for Bi without losing data mappings.  Point awarded and much respect
    Warm regards
    Lee Lewis

    Hi,
    Yes. There is a way to change the source system without deleting the old system. Please use the T.code BDLS and for more information refer the below link
    Re: Changing a Source System.
    OSS note 886102 will also give more information about this.
    Hope it helps.
    Thanks.

  • Source system moved to differnt folder in RSA1

    Hi,
    We did system refresh from R/3 production to R/3 Quality system.
    After this, as a part of post refresh activities, we did restore source system connection in RSA1 of BI Quality system by
    right click on R/3 Quality system and choosing the option Restore.
    It asked us user id and passwords for aleremote and extremote users ( background users for BW and R/3 quality ).We provided those.
    Then it asked us to provide the userid and password for administrator for R/3 quality system.
    We provided user id and password of DDIC user in R/3 Quality system.
    Then it gave the following message:
    User already exists in source syst. Only continue if profile and password are correct.
    Continue? or Cancel?
    We selected "Continue".
    Then it gave us the screen with following message:
    RFC destination already exists in source system .Do you want to use this destination, check, or cancel source system connection?
    Use ? Check? Cancel?
    We selected "Use"
    Then it gave us the following message :
    Connection BB is used in the R3QCLNT100 source system as a connection BQ1CLNT100 to BW.
    Do you want to delete this connection in the source system? Connection Is Restored After It Has Been Deleted Successfully.
    Delete ? or Do not Delete?
    We selected Delete.
    After this, restore took place successfully but there is one problem.
    After restore, in RSA1, Source system R3QCLNT100 ( source system name for our R/3 quality system ) is shifted from the folder SAP ( source system type for SAP source system ) to Folder BI ( source system type for BI system )
    Please suggest how to shift the source system from BI to SAP Folder.
    Thanks,
    Tarun Brijwani.

    Hi Tarun,
    have you checked RFC connection before you did Restore?
    Might be that you need to adjust RFC settings (TA SM59) for that particular source system.
    Seems to me that IP of your R/3 QAS system is pointing into some BW system. That's why your source system was shifted under BI source systems in TA RSA1.
    BR
    m./

Maybe you are looking for