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

Similar Messages

RSA1: source system missing after restoring broken in midway

Dear expert,
We are doing the ECC system refresh (ECC PRD to QAS)
ECC QAS has connection with BW QAS
So we after we maintain the RFC logon , steps are as following
Logon Q23 as client 0**
Run SU01 and change the password of ALEREMOTE to ‘****’ (must be uppercased)
Run SM59 and delete ABAP connection ABWCLNT0** if it exists.
Logon ABW using Client 0** as user sapsupport
Run SM59 and choose ABAP connection Q23CNLT0**, update the password of ALEREMOTE and perform connectivity test and make sure it is working fine.
After the steps above we continue on ABW with RSA1 (see picture 1) but unfortunately the remote connection is broken and when i logon RSA1 again
The Q23 client DISAPPEAR(see picture 2)!
Could anyone help to explain why ??? and how to fix/create the ECC QAS source system again ?
Thank you so much

Hi Reagan,
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
Message was edited by: Kate Ji i updated the content as above

While connecting the MSSQL (2000, 2005) to BI 7 in rsa1 source system getti

While connecting the MSSQL (2000, 2005) to BI 7 in rsa1 source system getting below error.
(When calling a function within the database interface, a return value which cannot be processed by the calling function was provided.)
Please help me to solve these issues.
Iu2019m able to connect Oracle 10.g as source system and can view the tables and views.
BI 7
Windows 64 bit
Oracle 10 .2
SAP GUI 7.
Advance Thanks,
KARAN
Edited by: Harish Karan on Jun 26, 2008 2:51 PM

Hello All,
I found the solution for my particular situation!
When checking the runtime object for CLU4, an inconsistency in the runtime object popped up:
- the ABAP dictionary contains the field K5N1
- the DB dictionry contains the field name K5N01
This is a known and documented inconsistency, see note 902817 for the description.
BUT: the solution pointed out there is wrong! The note suggests to delete all content from the physical tables and then activate the table in SE14. This is not possible for cluster tables neither in SE14 nor in SE11.
This solution worked for me for both CLU4 and VER_CLUSTR:
- as the tables should be empty normally I dropped them in the database
- unlock the shadow instance with SAPup
- log on on to the shadow instance
- I then made some arbitrary change to the table definition in SE 11 (like adding a field). Make sure to maintain the size class also, otherwise the table won't be activated
- save the changes and activate the tables
- take back the previous change
- save and activate again
- lock the shadow instance
- restart the upgrade phase
Once the upgrade is done, check whether the physical table exists in the DB.
Hope this helps!
Regards,
Matthias.
Edited by: Matthias Dörfel on Nov 18, 2011 3:14 PM

Rsa1 source system deactivation

hello ,
When i was working on rsa1 after creation of source system i right click the source system and pressed "RESTORE" but the object displayed deactivated symbol and trying to activate it but it still remain de activated
please can any one tell me the solution to the problm
on check it gives following error:
"Source system <name> is inactive" ID RSAR
Thank you in advance.

Hello,
Please check your RFC destination whether the source system already exists.
In the source system creation you assign the IP address instead of source system name. Please go through the screens (SM59).
If you have not used IP address you can ignore it.
Thanks
Chandran
Edited by: Chandran Ganesan on Nov 13, 2008 2:30 PM

RSA1 Source System Hierarchy Issue (SRCTYPE of RSBASIDOC)

Dear Experts,
Greetings to you all and thanks in advance for your valuable responses!
I am stuck here with a BW issue again. The issue is:
We have a DS connection, which earlier used to get displayed under DATASERVICES node, but I don't who/what changed what/how and now it gets displayed under External System. No matter what I do, it still stays there and due to this we are having issues in Data Extraction.
This our DEV system and in QA we don't have this issue. I don't know what/where to compare.
Earlier, I had the same display issue (but that was an R/3 system) which was solved by 1087980. Still I tried:
Deleted the entry with RSAP_BIW_DISCONNECT.
Recreated the entry under Data Services node, but it still didn't work. It jumped back to External System.
I have compared the tables and found that the SRCTYPE in RSBASIDOC is responsible for all this it should be 'X' instead of 'B'.
Can we change this manually from SAP level? If yes, then how and if no, then is there any alternative?
Thanks,
Avishek

Hi Avishek,
Check whether the sapnote 1692642 - Data Services source system for 3.x DataSources
is relevant to your system or not.
If relevant , then apply it and recreate the source system.
With Regards
Ashutosh Chaturvedi

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

Cannot see entries in RSA1 sources system list

Hi
As part of the post processing of the system copy from PXX to Xxx I scheduled a test run for the BDLS conversion PxxCLNT100 to XxxCLNT100.But as this was running too long I aborted this by doing "Stop transaction".
Then I started the actual BDLS run (PxxCLNT100 to XxxCLNT100), during which I got the error "The datasource ZBI_MT_xxx_xxxxx" (XxxCLNT100) does not exist in object version A.
As per the threads on SDN I ran the RSA1 tCode. Getting an error immediately "Logical System has been changed for this system".
Checked and changed WE20 partner profiles for XxxCLNT100 from I to A.
Then deleted PxxCLNT100 entry from RSBASIDOC.
Now in RSA1 I do not get the error but now the entire list of source system is no longer seen.
Regards,
Rohan

Hi,
Thanks for your help .
@Ashutosh :: RSBASIDOC table has list of all source systems from Pxx system and one entry of XxxCLNT100.
@Arjun :: EDPP1 has list of all source system from Pxx system except PxxCLNT100 and one other system (I had deleted manually).
Also EDPP1 has list of all source systems for Xxx system.
Currently there is BDLS running in the system Xxx for other source system. So will check and update once the BDLS completes.
As i have one more system Ixx in line for which i need to carry out the system copy. Would not prefer to land in the same situation of not finding source systems in RSA1.
Was thinking if I am missing any table in the export step before system copy, which might have caused this mess.
select * from rfcattrib
select * from rfcdes
select * from edpp1
select * from edp13
select * from edp21
select * from rfccmc
select * from rfcdessecu
select * from rfctrust
select * from rfcgo
select * from rzllitab
select * from tpfid
select * from e070l
select * from btcomset
select * from tvarv
select * from rfcdoc
select * from rfcsysacl
select * from rzllitab
select * from rzlliclass
select * from sxroute
select * from rfccheck
select * from tbd51
select * from tbd52
select * from tbd53
select * from tbd54
select * from tbd55
select * from tbd56
select * from bdrgin
select * from bdrgout
select * from tojtb
select * from saplikey
Thank you all,
Rohan

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

RSA1 Source System DBConnect problem with 8i DB

I have just upgraded my BI instance to Oracle 11G. After this, a source system connection to an Oracle 8i database configured using DBConnect does not work. I have read that a connection between 11g instant client and an 8i database is not possible.
After switching back to the Oracle 10G instant client, the source system connection works fine.
I'm just wondering if anybody has encountered this, and if there is any way to have the 11G instant client in place for SAP as a whole but have DBConnect use the 10G client to connect to the 8i DB. Any insight is appreciated. Thanks!

Hello,
Please check your RFC destination whether the source system already exists.
In the source system creation you assign the IP address instead of source system name. Please go through the screens (SM59).
If you have not used IP address you can ignore it.
Thanks
Chandran
Edited by: Chandran Ganesan on Nov 13, 2008 2:30 PM

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

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

Source System Problem after system refresh in RSA1 trx

Hi,
We have R/3 4.7 Test source system created in our SCM 2007 Test System. The source system check was OK.
The R3 Test system was refreshed with Production data few days back and now my source system is not working. When i perform Source System check it says:
BI unknown in source system
BI IDoc type ZSSB006 is not the same as source system IDoc type
I performed following steps in R3 Test system after its system refresh:
1. Created logcal system and created RFC.
2. Created port in trx we21.
3. Created partner profile in trx we20.
4. For the outbound parameter RSSEND, I had to create idoc type that should be same as in my SCM system i.e. ZSSB006.
5. Created idoc type using trx we30 as a copy of RSSEND and added entry in table EDIMSG. Now, i could also create outbound parameter RSSEND with idoc type ZSSB006.
After performing the above steps i also replicated the datasources for the R3 Test source system, but its still showing above error.
I also checked the RSBASIDOC table in SCM test system. It has correct entry for my source system. But there is no such entry in RSBASIDOC table in the R3 test system.
Someone pls help me.
Regards,
Chintan

Hi
Need to restore the All Dalaload connection settings after refresh the system which either R/3 or SCM.
RSA1 -> select the Source system -> Right click -> Restore , It'll ask the connecon paramters like RFC , method of activations. Then check the connection test of the Source system .
Check the the note for further info...
Note 886102 - System Landscape Copy for SAP BW and NW BI
Hope halp you...
Regards,
Sureshram

Creating source system in RSA1

Hi guys,
Im trying to create a source system in the TC RSA1 between R/3 PRO y BW PRO. But at the end of the process it sent me the message Source system already exists. There is no other source system for R/3 created. What can it be?
Thanks a lot
Regards,
Vic

Hi Vic,
Goto sm59 and delete the logical system for the R/3 system and retry the steps again.
Check this doc:
http://help.sap.com/bp_biv135/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
The steps for creating source system (automatic option in RSA1)is as follows:
1.Create remote logons in both the systems.
2.RSA1 -> Source system -> Create source system -> automatic creation
3. Enter the details of the R/3 system and the Remote logon ids of both the system. In case you are using BI 3.5 or greater + R/3 4.7 or greater the password is "case sensitive" hence have all the passwords in CAPS.
4. Now the system would create a remote logon and show up the remote logon screen. In that screen -> "logon and security" -> enter the remote logon id and password and save. Now the remote logon should not work from there.
The connection is established.
Bye
Dinesh

RSA1 - Source system(R3 - BI) restore issue

Similar Messages

Maybe you are looking for