cancel
Showing results for 
Search instead for 
Did you mean: 

Source system connection issues

Former Member
0 Kudos

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.

Accepted Solutions (0)

Answers (1)

Answers (1)

yogesh8984
Contributor
0 Kudos

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.