Source system activate/restore

I have created an R/3 source system in BW. Have checked SM59, WE20, WE21 many times and could log on to the source system. Have also replicated the source system. However, when trying to activate or restore the source system I keep getting:
First, the status message: Update source system application component hierarchy
Second, RSAR error 375: Result of the destination check: Timeout
And the activation is terminated.
My OSS Note 140276 search yielded nothing as well.

Hi Greg,
A. In the R/3 source system delete the entry in RSBASIDOC table for the associated BW sytem. This will delete the obsolete BW system connection.
B. In the associated BW system, RSA1>Source System>Restore will re-establishes the connection for the R/3 source system.
For more info, refer to OSS note:184322 (it's not relevant for your situation, but should help in restoring the connectivity). Hope it helps,
Cheers,
Sree

Similar Messages

  • Source system activate error

    Hi,
    I have created new source system for R/3 quality , when i am activating then getting following error. Kindly suggest how to resolve this error. Thanks in advance.
    BI unknown in source system     RSAR     8     
    BI IDoc type ZSDB018 is not the same as source system IDoc type     RSAR     371     
    EDI: Partner profile not available
    Entry in inbound table not found
    Entry in outbound table not found
    Rgrds
    Rakesh

    Hi,
    Check the source system RFC connection in SM59, if this is ok then check the tcode  WE20 for EDI partner profiles and inbound and out bound Idocs defined.
    In BW Out boud IDOC type should be same in ECC in bound Idoc type, and in ECC out Bound IDOC type should be same in BW in bound IDOC type then the source system activation is possible in RSA1.

  • Source system R33CLNT100 is marked as inactive in BI.

    Dear Experts
    When I do a source system check via RSA1 > Source systems > SAP folder > right-click the R/3 system ID and select Check function,
    the system throws as error as shown :
    "Source system R33CLNT100 is marked as inactive in BI."
    "Procedure
        If you have upgraded to BW 2.0, activate the source system.
        With other errors connected to this source system, choose Restore   the
        source system from the source system tree in the Data Warehousing
        Workbench. This regenerates the source system, merges the relevant
        communication parameters, and replicates the DataSources in BI.
    and
    "BI IDoc type ZZZZ011 is not the same as source system IDoc type ZSSS021     RSAR     371     
    There was a system Refresh from Production R/3 46C to QA system R/3 46C.
    We did the BDLS but the IDOC seems to have got overwritten by R/3 Production's, obviously , due to refresh.
    Any idea how to resolve this?
    It seems like I need to re-create manually the idoc but I am not expert in this area.
    I do know there are standard IDOC aspects for BI 7.
    But how to re-create the relevant IDOC settings or configurations ? Need to do this in both  BI and R/3 ?
    Best regards
    Pascal

    Hi pascal ,
    Seems to be connectivity between the source system and the Bi system it will be restore by basis team only. Couple of tings that you can do at your end will make their work at ease
    i) check the RFC connection between the Source system and the Bi system in Sm59.
    ii)Make sure the user ALERMOTE and SAPCPIC are unlock in ecc side
    Now for configuring the source system by urself follow the below points :
    1. In BW, call TA RSA1.
    2. In the left hand column, choose "Source systems".
    3. In the column Source systems, right click on the respective source system and choose "Restore".
    4. A popup "Create R/3 source system" appears. Enter the passwords for user SAPCPIC. Hit enter.
    5. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
    6. A logon screen of the child system appears. Enter your user and password and hit enter.
    7. A popup "New source system connection" appears. Hit "Continue".
    8. A popup "Check RFC destination" appears. Hit "Check".
    9. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
    10. The popup "Check RFC destination" appears again. Now hit "Use".
    11. A popup "Connection can not be used" appears. Hit "Delete".
    12. A popup "Please log on as an administrator in the following screen." appears. Hit enter.
    13. A logon screen of the child system appears. Enter your user and password and hit enter.
    14. A popup "New source system connection" appears. Hit "Continue".
    15. A popup "Check RFC destination" appears. Hit "Check".
    16. The child system jumps into TA59, displaying the RFC destination pointing to the BW system. Check it by pressing "Remote logon" (nothing happens, i.e. no error message appears!) and "Test connection" (the connection test table will be displayed). Hit F3 twice. The system jumps back.
    17. The popup "Check RFC destination" appears again. Now hit "Use".
    18. A popup "Replicate Metadata?" appears. Hit "Only Activate".
    19. If popup "Do you want to reactivate all transfer structures and DataSources?" appears. Hit "No". If "Display activation log" popup appears - press "No" (that message may appear several times).
    20. Press "Back" if "Analyze application logs" screen appears
    Source -->http://forums.sdn.sap.com/thread.jspa?threadID=1892011
    Thanks,
    Deepak

  • No IDOCS arrived from Source system to BI  for generic extraction

    Hi All,
    While loading data from r\3 generic data source to BI, I am facing the below problem.
    1. Using Full Load:-
    The request from r\3 to psa turns red after a while. The request monitor says:
    Error when updating Idocs in Source System
    Diagnosis
    Errors have been reported in Source System during IDoc update:
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Source System . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.
    Details Tab shows : request green
    Under that Extraction tab shows  red
    missing messages.
    Transfer (IDocs and TRFC): Errors occurred .
    Request IDoc : Application document not posted
    I ran Transaction BD87,BD73 and execute with proper selections.
    Upon checking the idoc in source system Their status is 51 , which says
    Diagnosis
    The control parameters for communication with the BW server are not
    complete. A BW PlugIn upgrade could be the cause of the problem.
    System response
    Procedure
    Depending on the Release of the BW server, proceed as follows:
    BW Server Release 1.2B: Source system: Update InfoSource metadata
    BW Server Release >= 2.0A: Source system: Activate.
    Manually i tried to push the idocs in the BW and source system using TRF but i dint found any records???
    Soruce system connection is fine. Profile parameters are set properly and its active  .. But still am getting the same problem.
    Many thanks, I'll applicate your help.!
    Rakesh

    Hi
    I am also facing the same problem. This happened after restoration of the original system with a copy of the production.
    I am not able to get the IDOC posted in the source R3 system.
    I did a debug and it failed when verifying the table, RSBASIDOC.
    There appeared to be some missing records which need to be inserted.
    I can't find a way to insert the missing record and since then, I am not able to proceed.
    Have you resolved the issue?
    can you share how it can be overcome?
    Thanks a lot

  • Error in Source system (Job is not going in to job log of CRM system)

    Hi,
    We replicated datasources from CRM server in BI 7 server and they get replicated and are in Active version
    All transactiond atasources which are 7.0 version are executing successfully, but the Datasources which are in 3.5 version i.e. Datasource for master data infoobject gives error while executing infopackage.
    The error message is as follows:
    "Diagnosis
         In the source system, there is no transfer structure available for
         InfoSource 0CRM_MKTMETA_ATTR .
    System Response
         The data transfer is terminated.
    Procedure
         In the Administrator Workbench, regenerate from this source system the
         transfer structure for InfoSource 0CRM_MKTMETA_ATTR ."
    Also while executing the infopackage the job log in source system is not able to create the corresponding job.
    Following action are already been taken:
    1. Datasource replication
    2. Confirmed that the Transfer Structure are avialable and are in ACTIVE state.

    Hi
    It seems some changes are taken place at Source System for the Mast.Data DS. Try to Recheck the Same at Source System -- Activate/Retranport the same.
    BI side.
    RSA13Source System Your DS-- Replicate the Data Source -- Try to Run RS_TRANSTRUC_ACTIVATE_ALL(SE38) / Activate Transfer Rules Manually -- Then Full/Re Init -- Delta Uploads
    Hope it helps and clear

  • Error in source system in BI 7.0...

    Hi,
         When creating a source system in Bi 7.0, when i am going to t code- rsa1- client-right click and then check,it's giving an error like:
    EDI-  partner profile not available and then detail for this error is-- a partner profile cannot be found with this key- /DBICLNT300/LS
    THIS INVLOVES THE KEY FIELD OF THE TABLE EDPP1-
    PARNUM-PARTNER NUMBER
    PARTYP-PARTNER TYPE
    Please help me in solving this. Thank You.

    Hello,
    Try a restore on your source system (rightclick -> restore) This way idoc ports and agreements are regenerated between BW and R/3. If this does not solve the problem ceck this:
    Hi,
    Did you do a system copy for BW ?
    Try a restore (rightclick on your source system) in most cases this will solve the problem.
    If not check the notes below:
    184322 Procedure after DB copy of BW source systems
    886102 System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
    325470 Activities after client copy in BW source systems
    325525 Copying and renaming systems in a BW environment
    184754 Procedure after BW database copy
    184447 Building a BW-system landscape
    184971 Notes on BW source system connections
    140276 Error in source system assignment
    524554 Storing destinations in the BW environment
    538052 Maintenance of Myself destination in BW
    Regards, Patrick Rieken

  • Source System inactive in Quality

    Hi Experts,
    I need to load the data from flat file to ods but my source system is inactive in Quality server when i double click on source system it is not showing any active button in quality server, but the same source system is active in development server.
    Please can any one solve my problem.
    Many Thanks in advance
    David

    Hi Srinivas,
    Thanks for your answer, and one of my source system is still inactive for this i follow the below steps,
    1) Run the program in se 38 RS_TRANSTRU_ACTIVATE_ALL
    2) RSA1- source system_ right click on source system - activate..
    but still my source system is inactive so how can i solve my problem... please give me solution.
    Daivd

  • Connect two BW systems to one source system

    Hi Experts!
    I would like to know if I can set up two BW systems connect to one source system.  We copied and built new BW system (BW2) from existing BW system (BW1).  We need to have both system connect to one source system.  When I execut Restore from BW2 - RSA1 - Source System, I'm getting a following prompt:
    "Connection cannot be used. The connection BB is used in the DEV400 source system as a connection BW1400 to BW. Do you want to delete this connection in source system".
    If I select "Delete" then it replace exising connection between BW1 - DEV and creates new connection BW2 - DEV.  If I go back to BW1 and do restore then same thing happens as BW2 connection removed.
    Is there anyway we can set up two BW systems connection to one source system with restore?  Connection works fine since each one can connection with no issues.  Just when I do restore, it removes other connection.
    Thanks.

    Check if it helps:
    Loading two different SAP BW system from one SAP R/3

  • Source System - Restore

    Hi All,
    In RSA1, in Source System menu, when we right click on any source system created, we will see "Restore" from the context menu.
    Can anybody please share what is this used for and what is the difference with the "Activate" process in the same context menu ?
    Thank you.

    Source sytem restore is used to maintain the RFC connections after system copy or refresh of the sytem.
    when you select restore option in the context menu you will have to entert the RFC user name (ALEREMORE or BWREMOTE) for your source sytem and BI sytem.
    once it is done it will check the ports and maintain correct ports for various IDOC types which will be used in inbound and outbound processing of DAta.
    once connection is resoted you can start with replicating the data source using the context menu in BW, it will check for the new data source in sources system side and replicate those in Bw.
    hope this will help.
    Regards
    santosh

  • Not able to activate source system meta data

    Hello,
    For BW 3.5 The connection is working fine between source system and metadata is getting replicated successfully but in inactive mode.
    While activating I get following error.
    Incorrect IDoc type éâÄÃðôð@@@@@@@@@@@@@@@@@@@@@@@ in the ALE definition of the source system     RSAR     373
    Not sure what is wrong I have checked IDoc settings in both the systems they exists and the table RSBASIDOC has all the correct entries.
    Thanks and Regards,
    Milan

    Hi,
    Re-activate the source system in BW. That will recreate all the ALE settings. Make sure that the source system is open for changes and you use a user ID and password with appropriate auths for maintaining ALE settings.
    after that
    Try the restore option. Run check after that.
    Regards,
    San!

  • Error when activate a SAP source system

    Hello Experts,
    I have an issue when I try to create a new SAP source system but I cannot complete this operation because a Timeout error occurs when the system made the destiny verification, the source system can be created but not activated, I already create the RFC connection and they are OK, I add the new logical system of the source system in the configuration (SBIW) in the general settings,and the data source tree is show succesfully and sems to work OK and the data sources seems to be OK too.
    In the RSA1 transaction, go to source systems tree, choose the SAP source system called: "conexion a dev 200" -> right click and choose activate and the error occurs.
    I have a Myself source system already created and activated, I cannot find the source of the problems thata cause the timeout error in the new source system.
    Thank you vey much in advance,
    Niurka

    Yes, I try ti use the create automatically option first but it doesn't work, because says that we system already exists because here exist a myself source system with an RFC to R/# ( I don't know why), so I must use the manually creation option, I put the logical system, and all the requeriments of the screem. The system create the source system but when I try ti activate it, it is impossible to do it....!
    I hope that you can give some tips or solution for this issue,
    Thanks!

  • 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

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

  • Source system restore timeout

    Hi guys,
    I am trying to do a source system restore, but after about an hour it times-out and it doesn't complete the transfer structure restore across to BI.
    Can anyone help on how to get around this?
    Thanks in advance, points will be awarded.

    Can you please explain more on ur question. What is the requirement.

  • 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

Maybe you are looking for