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

Similar Messages

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.

Repository connect issue after MDM Patch Upgrade

MDM Expert
We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
SAP is asking to create new DB Instance for MDM.
If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
Please help
Thanks
Deelip

Solution provided by sAP

IPad connection issue after iOS 8 upgrade

I Have an iPad 3G - WiFi- and recently upgraded to IOS 8. Every since connection bounces from 3G to "no service" (AT&T provider). I have been able to get reconnected only by choosing "Reset Settings". I previously powered off and restarted with no resolution. Found article that mentioned this same issue but said it only was issue in iphone 6. Anyone else have a similar experience or easier solution? I rely on iPad for work and really need a solution that doesn't involve frequent resets....
Message was edited by: Raven72songs

I have been to Apple store twice now on this issue. We have tried all of the above suggestions-- restore, network reset, re-installing SIM card-- and the problem always returns. The Genius Bar tech told me the IOS update brought out a latent problem hidden in the firmware -- in other words, it is a problem caused by Apple, but not everyone experiences this problem. The tech also told me there was nothing more that could be done, short of buying a new ipad. I asked about going back to the earlier IOS version but she said Apple will not allow that at this point. So it sounds to me like a "forced obsolescence" thing that Apple has inflicted on me: they admit their update brought out a problem, previously unmanifested, which had always been lurking in their firmware-- but their solution is that I need to ditch my ipad 2 and buy a new ipad. I never had this type of issue before the upgrade. the problem is more of a nuisance/inconvenience than anything else, because it can be rectified by powering down every few hours, so it's not worth it to me to spend hundreds on a new ipad. And anyway if this is an example of their customer service I'm not sure I will stay with Apple when it finally is time to buy a new tablet.

Assignment of Source System in quality after transport

Hi Experts,
We have implemented the Inventory management standard flow in Development,
Now to tell you, we have multiple landscape over here,
Depending on the project, and the fesiblility for the client, the tranport layer is been decided,
But for sure we have multiple source system,
By multiple source system, i mean not the other components like R/3, SRM or APO,
but for R/3 itself we have multiple boxes at each layer,
Now when transported to quality,
the standard objects are reflecting after few errors corrected and re transports,
But the source system which it has picked for the BF BX and UM datasource is not that i require according to the transports landing for the R/3 developments,
AT DEVELOPMENT LAYER,
BW development is GDA, which is having the source system connection to development R/3 (GD0),
AT QUALITY
We have BW as EQ3,
For R/3 we have EQ0 and NR0,
All the transports have reached in the respective target quality system,
But the data sources are having source system connection to NR0 and not EQ0,
I want it to be EQ0 as the data lies over there.
How do i resolve this ?
Thanks and should be appricated for your efforts in helping.

Hi Daljeet,
You should set the Source system Conversion option in Transport Connection before Transporting the objects to QA and PRD.
You can do this using the button 'Conversion' next to the button 'Source System Assignment'. Here you can specify the Target source system name after the Transport.
If you want to change all the assignments from NR0 to EQ0, this article will be helpful for you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81
Get the help of your BASIS team also.
Refer this thread.
Re: source system in RSA1 is diiferent to the datasource in infoprovider

Source System Connection Problem - RSAR 371

We are attempting to create source system connections in our newly created NW2004s Dev system (sapdvbd1/BD1). We also have an existing NW2004s Dev system (sapsvbd1/BD1) which already contains the same source system connections. The old Dev system was on a virtual machine but due to performance issues we have built another Dev system on a real server. Is there any way to create these source system connections on both servers until everything has been moved from the old to the new? The same source systems need to exist on both. Thanks.

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

BI Source System connection to ECC

Hi experts,
I have a BI 7.0 fresh install and I'm trying to connect ECC 6.0 client dev100 (golden client) to BI so I can activate BI Content. However, the client 100 goes to the BI folder instead of the SAP folder when I create source system in AWB. Is this normal behavior?
I have another system client dev200 and it goes inside SAP folder when I create source system. I'm just wondering if this has something to do will my error in BI Content activation. Key figures and characteristics are activated but not DataSources, Update rules, and InfoPackage.
Your comments are greatly appreciated. Thank you

Hi JD,
I think the source system connection must have been made in Bi folder. basically even BI folder shall contain BI system but if ECC system connection is made in this folder it shall not make any diffrence. You must be getting the datasources as of ECC only after replication.
Regards,
Wrushali
Request for points deleted. Please do not ask for points in the forum.
Edited by: Vikram Srivastava on Jun 22, 2010 1:56 PM

Source system RFC fails after transport

Hi all
in our QA system any transport containing a process chain causes the RFC connection to the source ECC6 system to fail after too many logon attempts.
This doesn't happen when we send the same transport to production.
Any ideas?
Regards
Hayley

Hi
thanks, but I had already checked out this note. This refers to the post processing of the transport on BW of client 000 logging onto the BW client to carry out changes, not the RFC connection to the BW ECC source system.
The transport goes through ok, and the process chain can be activated, however at this point we always notice that the ECC source system connection fails with an RFC error, as soon as we get the password reset and changed in SM59 it works ok.

Is there a fix for the wifi connectivity issue after ios6 update?

Is there a fix for the wifi connectivity issue after ios6 update?
Cannot connect to any wifi since update to 6.0.1
How do I get update to 6.0.2?
Will that even help?

Some things to try first:
1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
4. Go into your router security settings and change from WEP to WPA with AES.
5. Renew IP Address: (especially if you are droping internet connection)
    •    Launch Settings app
    •    Tap on Wi-Fi
    •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
    •    In the window that opens, tap on the Renew Lease button
~~~~~~~~~~~~~~~~~~~~~~~~~
iOS 6 Wifi Problems/Fixes
How To: Workaround iPad Wi-Fi Issues
http://www.theipadfan.com/workaround-ipad-wifi-issues/
Another Fix For iOS 6 WiFi Problems
http://tabletcrunch.com/2012/10/27/fix-ios-6-wifi-problems-ssid/
Wifi Doesn't Connect After Waking From Sleep - Sometimes increasing screen brightness prevents the failure to reconnect after waking from sleep. According to Apple, “If brightness is at lowest level, increase it by moving the slider to the right and set auto brightness to off.”
Fix For iOS 6 WiFi Problems?
http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
iOS 6 iPad 3 wi-fi "connection fix" for netgear router
http://www.youtube.com/watch?v=XsWS4ha-dn0
Apple's iOS 6 Wi-Fi problems
http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
~~~~~~~~~~~~~~~~~~~~~~~
How to Fix a Poor Wi-Fi Signal on Your iPad
http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Fix-A-Poor-Wi-Fi-Signal-O n-Your-iPad.htm
iOS Troubleshooting Wi-Fi networks and connections http://support.apple.com/kb/TS1398
iPad: Issues connecting to Wi-Fi networks http://support.apple.com/kb/ts3304
WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
How to Fix: My iPad Won't Connect to WiFi
http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
iOS: Recommended settings for Wi-Fi routers and access points http://support.apple.com/kb/HT4199
How to Quickly Fix iPad 3 Wi-Fi Reception Problems
http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
iPad Wi-Fi Problems: Comprehensive List of Fixes
http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
Connect iPad to Wi-Fi (with troubleshooting info)
http://thehowto.wikidot.com/wifi-connect-ipad
Fix iPad Wifi Connection and Signal Issues http://www.youtube.com/watch?v=uwWtIG5jUxE
Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
Unable to Connect After iOS Update - saw this solution on another post.
https://discussions.apple.com/thread/4010130
Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
~~~~~~~~~~~~~~~
If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
 Cheers, Tom

Bluetooth connection issues after update

Is anyone experiencing bluetooth connection issues after upgrading to iOS 8.1.3? I upgraded to iOS 8.1.3 and now it won't connect to my car bluetooth and my bluetooth speaker will sound like it has static from time to time.

Hi, joshzik.
Thank you for visiting Apple Support Communities.
I understand that you are experiencing issues with various Bluetooth devices and your iPhone. Sometimes pairing the devices again can resolve the issue. However, here are a couple articles that have some helpful troubleshooting steps regarding Bluetooth connectivity and an iOS device.
Get help using your iPhone, iPad, or iPod touch with your car stereo
http://support.apple.com/en-us/HT203412
iOS: Troubleshooting Bluetooth connections
http://support.apple.com/kb/TS4562
-Jason H.

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

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

Source system connection in IDES ECC6.0 Version

Hi experts,
I have ECC 6.0 in our Company, ECC 6.0 version also have BI integrated with ECC6.0 version.
Now my question is that is it possible to connect r/3 with BI in the same server, we have two application server, if yes Please let me know how to achieve it without changing the logical system name.
because if we change logical system name then it gives a error message that logiacal system name has been changed for this system.
any help in this regard would be apprecicated.

Hi,
One server can have several systems but with different client and with different logical system anem. Now if logical name is same, they source system connection is not possible. Logical system name can be changed in t-code SCC4, but please do consult basis person before doing this as this is bit sensitive.
Regards
Pankaj

How to verify the Source systems connectivity with BWQ System.

Hi All,
I have diff source systems. And my requirement is to check the source systems connectivity with BWQ (BW Quality sys). please any body tell me the steps how to check the source system connectivity ?
Thanks & Regards,
Manju

Hi Manjula,
If you encounter problems when establishing a connection to your target server, check the following:
A message box appears while performing one of the following actions:
      Setting connection by choosing Apply to local session.
      Testing connection settings by choosing Test settings.
      Creating SAP TSQL objects
If errors occurred, they are displayed in the respective message box.
   Check developer trace files in ST11.
Test connection:
     For RFC related errors, check the RFC connection via SM59
     For database multi-connect errors, check if you can connect to the target SQL Server with the SQL Server Query Analyzer. Also check if the DBCON entries are correct.
Regards,
RK

Not able to change source system connection

Hi, I have problems changing a source system connection from BW. BW is already connected to source system A, which is closed down, and I'd like to connect BW to source system B, which excists and can be accessed. I have tried to use BDLS, but get the message that System B already excists (new one). I try to delete it (Change view logical System), but am not allowed to do this. I get the message "must not be deleted, first delete from distribution model." And thats where I am stuck. Can anyone guide me on my way?
Regards E!

Comment to the last answer:
When I try to delete in SALE I am told that the source system also excists in the Distribution Model (CUA) and can therefore not be deleted. It must be deleted in the distribution model first. I find CUA at BD64. Looks like this is the connection to Solution Manager. What are the consequences for deleting the Source System here? And will it hlep me to solve my problem, which is that I can't change my connection from Source System A to new Source System B?
Regards E

Source System Connection Issue after BI 7 Upgrade

Similar Messages

Maybe you are looking for