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

Similar Messages

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(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

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.

BI Source system (critical issue)

Hi Friends,
I am working as a basis consultant.
we have a ECC6 Development server and in the same server we hav installed BI-Cont and using as a BI Dev sever too.
Client - 400 is R/3 Develop server
Client - 300 is BI Develop server
we cofigured 400 client as a source system for bi(300) and lot of develpments are made.
Now we are planning to make this ECC6 DEV as a Production server for BI. (simultaniously R/3 developments also will happen in the same server).
Now i have Created a new client-500 for BI(Production) in the same server and i want to add our R/3 Production server client-900(different server) as a Source system.
1 I maintained RS_MANDT_UNIQUE_SET and set to client 500.
2 I maintained table RSADMINA and set client 500
and BW_user
3 Created RFC between client 500 to PRD server client 900
now when i tried RSA1 Transaction in BI PRD client 500, it says "Logical system name has been changed for this system" "Message no. R3206"
when i see the long text it says
"The logical system name of this system is PRDCLNT500. However, this system was originally created with the logical system name DEVCLNT300. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to DEVCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to DEVCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow."
1 I tried to remove the source system from 300, but it is prompting to delete lot of packages and it is going for a while. so i stopped it.
2 I removed all the RFC Connections between 300-400
3 I deleted the logical system "DEVCLNT300".
Still the same Issue "Logical system name has been changed for this system".
Please help me Resolving this issue, since this issue became so critical.
Thanks in advance
Prakash

Thank you for Replying
I know the landscape we are having will confuse.
In ECC6 DEV Server a new client 500 is created for BI Producion server (not exactly prod but assume like that).
There is seperate R/3 Production server (client-900) and that shud be configured as a source system for the new BI PRD Client 500.
I dont want any data from 300, infact i would delete the 300client (BIdevclt) after i configure everything in client 500.
I did all the BI post installation steps for client 500.( including RS_MANDT_UNIQUE_SET)
but since the 300 client was configured as BW dev in the same server, i am getting an error if i access RSA1 in client 500 "Logical system name has been changed for this system" "Message no. R3206"
I went through the BDLSS transaction, but it talks about converting logical system and i dont want to do that.
Client400 is configured as source system for bi dev 300. I want to delete all the configuration made in 300.
I want to know deleting the souce client manually from BI dev 300 client is the only way to fix this or anything else we could do it for this ERROR.

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

Remote Process Chains Source Systems mapping issues

Hi,
We have a process chain in APO system, which upon success calls another process chain in BW.   We recently implemented SCM5/BI7, and taking the advantage of remote chains functionality to call the BW chain from APO.
However, when we transported the APO process chain from DEV to QA, the source systems in the remote chain are still pointing to DEV systems.   We were expecting to see both APO and BW source systems getting switched from DEV to QA.
We have already verified the logical mappings for Sources Systems are in place under RSA1 | Transport Connect | Conversion.   Also, the source systems seem to map correctly for other objects like data sources etc..   Only issue is with the remote chain.
Is there any other setting which need to be set to make it work.   Any help or guidance will be greatly appreciated.
Thanks in advance,
Ravi Chitluru.

Ravi,
I have a similar situation. Can you explain how to run process chains in APO which can gets data from BW cubes, which in turn gets data from R/3.
In this equation R/3->BW->APO, what are the options like 1)run process chains in BW system to pull data from R/3 into BW and run process chains to load BW data into APO 2)run remote process chains to pull data from R/3 into APO(of course via BW).

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

Source System Connection Issue after BI 7 Upgrade

Hi all,
We have just upgraded from BW 3.1 to BI 7.
After the upgrade, I checked the connection to our R3 4.6 source system.
It is now saying the following message:
Source system XXX is marked as inactive in BI.
Check failed for RFC connection XXX ; check destination
After going through the RFC connection, I tested the connection for this source system. It said OK. While doing the authorization test, it said: "Name or password is incorrect. Please re-enter".
The thing is that our name & password ARE correct definitely.
Is there any issues post upgrade because authorization stuff between R.3 4.6 (PI 2004.1 SP15) and BI 7?
Any ideas?
Thank you
chris

Hi,
as from NW7.0, passwords are case-sensitive.
If you define the passwords in the RFC in uppercase, it will work.
This is a problem when you link an 'old' (not NW 7.0) system to a NW 7.0 (as in this one, passwords are case-sensitive).

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

Source System Creation issue in BI

Hi Everyone,
I have already created RFC Connection in BW and EC(BackGround Users are ALEREMOTE and BWREMOTE). I am able to login using Remote Login from SM59 from BW to ECC and Vice versa. After this , When I try to create a Source System, it asks me to provide the ALEREMOTE and BWREMOTE Passwords along with the Source System Name.
I provide all the details.
Then the System asks me to login as a Administrator into ECC. And Once, I login, it throws up an error RFC Connection failed.
I think I am missing some steps.Please provide your inputs.
Regards,
Samir

Hi Ananda,
Thanks for your response. I did the same. Created Background users and when Try to Create a Source System ,it prompts me to R/3 side and here it is showing as RFC Failed. Remote Logon is working. But when Icreate a source System and provide password details, it fails.
Please advice.Is there any password restrictions for Background users.I maintained it as "init123". Do we need to use Capitals. And once, we provide the initial password, do we need to change it again somewhere?
Thanks and Regards,
Samir

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

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

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

RSA1 Source System Hierarchy Issue (SRCTYPE of RSBASIDOC)

Similar Messages

Maybe you are looking for