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.

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.

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

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

Why should the source system config be open for restore?

Good day everyone,
Every time I do source system restore, I have to open the IMG in the source system. Could someone please explain or provide me with an SAP link that explains the necessity for this step. It is causing me a lot of troubles in production systems.
Thanks.

Thanks for your response.
Funny thing though my has not ran that hot.
Wither watching Videos or play a game like Fallout 3 everything on the laptop is always cool to my touch on the top.
Except sometimes by the vent where the fan and exchaust are it maybe lukewarm, I've had other laptops run much hotter.
But Thanks for the input, I think I'll go ahead and turn it back on though.
Better Safe then Sorry....

Extraction failing after source system and client copy

Hi all,
We refreshed our source QA system with a copy of production. And basically tried to "restore" the connection from our BW QA system. Some of the datasources can be extracted from BW, others fail with an error of "No transfer structure is available for InfoSource 0COSTCENTER_ATTR in the source system".
Trying to do the same thing with RSA3 in the source system, works fine.
The strange thing is it works for some objects but not others.
here's what we did:
1. System copy from R3 Prod to R3 QA
2. Client copy with R3 QA client 300 -> 200
3. Restore connectivity in BW QA to the R3 QA system (Using RSA1 -> Source System -> Restore)
4. Now some objects can be extracted in BW, others fail as I mentioned above.
I have regenerated the transfer structures in BW and R3.
All of these objects that don't work seem to work in RSA3 on the R3 system but not in RSA1 on BW.
All the SAP documentation is geared to copying the R3 source system and then restoring connectivity between BW and R3. I don't think any of it involves copying the client in the R3 source system - which might be causing our problems.
We are using an SAP delivered PDF and note 886102 mainly for direction.
SAP PDF is "How to... System Copy in SAP Business Intelligence System Landscapes".
Does anyone have any ideas?
Thanks,
Kevin

Hi,
can you isolate somehow the kind of DataSource which works and those who don't?
Master data / transactional or client dependent and not, delta or full....
To which R/3 client is your BW connected? when you succeed loading the data, is it coming from the right client?
RSA3: do you run it specifying your BW client in the target sys field? does it make a difference if yes or if not?
Are your RFC connections and partner profiles all right?
Check some IDOCs sent by BW received in R/3 and vice-versa (RSSEND, RSINFO, RSRQST..). Load a hierarchy (via IDOC)... verify that your IDOC have the correct partner settings....
let us know
Olivier.
Message was edited by:
Olivier Cora

Source System In Deactivation Status

Hi,
Iam trying to connect R/3 Source System But it is in
Deactivation status.How to make active?
Kindly help me to sort out the issue.
Regards,
Chakri

Hi Chakri,
1. Check RFC connection in SM59 in both the system.
2. If RFC connection is fine Right click Source system -> Restore.
Also make sure your background of both the system has RFC related profile. This is very important to set the connection.
Regards,
Rohini

Error occured in the source system

hi experts,
can you plz how to resolve this error
incorrect doc type ZSBB003 in the ALE defination of the source system.
system response
error when sending data to bi.

Is the partner system profile incorrect? Please reconcile with table entries in RSBASIDOC. You can ask BASIS for assitance. Case A : Check RFCs via SM59. Configure IDoc settings via WE20 and WE21. If there's an issue with source system, restore & reactivate in RSA1 > Source System. SAP Note 325470 can also assit you for this method. Reference : http://goo.gl/t33d0

RSA1 - Source system connection : No connection to system possible

Hello friends,
I am creating a Source system connection from our BW system. I have already established the working RFC connection to source system which works fine, both side client is open & system is modifiable.
Bit i am getting error : No connection to system possible
No connection to system possible
Message no. RSAR501
Diagnosis
Logical system cannot be accessed.
System Response
Error during the retrieval of the logon data store d in secure storage
Procedure
Use transaction SM59 (for BAPI and SAP source systems) or DBCO (for database source systems) to check the RFC parameters of source system . Also check whether the system can be accessed in the network and whether the necessary application and system programs have been started.
I have already implemented SAP note 1276270 - RSAR 501 for source system restore due to router string /H/ without success.
thanks
ashish

Error during the retrieval of the logon data store d in secure storage
Have you tested the remote login also ?
Regards,
Subhash

Change Source system ID

Hi Experts,
We did a system copy of BW system alone, and when we tried to restore the connection with the source system, i am getting the following message.
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system DEVCLNT030 does not accept any of the proposed values.
The last proposed value was BA.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely BA, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.
BDLS was successfull, and returned no errors.
I checked the source ID in the RSA1 and it exists, how do i change this value.
Thanks in advance
Praveen

Hi Praveen,
Login to ur SAP R/3 or ERP Source System and go to table RSBASIDOC.
Put the R/3 logical System Name and BI logical system name as parameters and see the table values, i am sure the 2 digit unique identifier value will be the one giving u the problem.
This error comes after system copy of source system as ur system still behaves as Production System (the one from which it is copied).
Execute function module RSAP_BIW_DISCONECT in SAp R/3 System with parameters as ur R/3 logical System Name and BI logical system name and option forced delete as X. to delete entry from RSBASIDOC table.
now go to BW system RSA1 > Source System> restore ur system.
Hope it helps
Thanks
CK

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

Restoring the source system connection in BW

Hi all,
Ive 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

RSA1 - Source system(R3 - BI) restore issue

HI Everyone,
I am trying to restore my source system(R3) from BI from RSA1. iam getting some error.
Error:
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system SAPSQ1 does not accept any of the proposed values.
The last proposed value was BA.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely BA, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.
I checked the table RSBASIDOC also. The Target BI logical system is not present. CHecked the partner profile & IDOC Ports also.
RFC connection is also working fine
We recently performed R3 system refresh
please help me resolve this issue since its a critical issue which neds to be resolved immediately
thanks & Regards,
Siva

If you have done system refresh then to restore the connections you have to follow the below note as per your scenario
Note 886102 - System Landscape Copy for SAP NetWeaver BW
Only then the connection can be restored

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 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 restore timeout

Similar Messages

Maybe you are looking for