BW to R/3 system connection

Hi,
I am having bw 3.5 and ecc5.0 ides system.i want to create source system in bw and connect to r/3 system.plz any one can send me step by step proceddure for to do that,
Thanku

Hi.......
Go to SM59.
In menu->Edit->Create
Name->Some techinca Name ECCSCTNL
Connectivity->f4 and match you requirement.for r/3 and BW it is 3.
Techincal Settings
target Host-> applucation server name of your eccs 5.0
system number-> your eccs system number
Save.
Now->Next Logon/Security
User->ALEREMOTE
Password->your password for aleremote
Save.
Now click on Test Connection.
Check this :
http://help.sap.com/saphelp_nw04/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
Regards,
Debjani......

Similar Messages

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

Can 23" cinema HD Display support Game systems connectivity

I currently have my display connected to my MacBook but space is a factor at my dorm. Can I use my Apple 23" Cinema HD Display to connect my xbox 360? I bought a DVI to HDMI adapter but i get no picture. i also have a xbox VGA cable if i need to go that route. I figure digital to digital should give me a better picture, the an analog to digital. Can my 23" Cinema HD Display support game system connectivity or these older display were meant for Mac's Only?

followup question... Does the 23" cinema HD Display support HDCP? Could that be the cause for a blank screen. the power light is solid. I when to Display settings and lower resolution on the monitor, still no picture?

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.

How to build a form that traps all the IP adresses of the systems connected

HELLO EVERYBODY,
This is Paritosh Sharma,Actually I wanna know How to build a form that traps all the IP adresses of the systems connected.It's really Urgent

6i on the web or client server? Webutil is not certified against 6i so if it's web I'm not sure, but I think it's in D2KWUtil for client-server.

System Connection Test was not fully tested but all web dynpro java app and Transaction iviews working fine.Any problem for this Kind of activity Lets give some idea.

System Connection Tests
You can test the connectivity to the backend application represented by the current system object. Choose the relevant tests.
Note: The test is based on the properties currently defined in the system object. It does not check if the system properties are correct.
System Connection Tests
Test Name
Description
Status
SAP Web AS Connection
Tests the connection to an SAP Web Application Server
ITS Connection
Tests the connection to an SAP ITS server
Connection Test for Connectors
Tests the connection to a backend system using an associated connector
Test
Clear Results
Results
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Checks if the host name of the server can be resolved.
6. Pings the WAS ping service; works only if the service is activated on the ABAP WAS.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name
5. The host name ssprdxi.stylespasapnet.com was resolved successfully.
6. The Web AS ping service was pinged successfully.
7. An HTTP/S connection to was obtained successfully.
ITS Connection
Test Details:
The test consists of the following steps:
1. Checks the validity of system ID in the system object.
2. Checks if the system can be retrieved from the PCD.
3. Check whether the system object has a valid system alias
4. Check whether a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Checks if the host name of the server can be resolved.
7. Checks HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. The system was retrieved.
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name ()
6. The host name ssprdxi.stylespasapnet.com was resolved successfully.
7. An HTTP/S connection to was obtained successfully.
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
regards
Antony

Hi Stefan,
This correct see SAP Note [947081|https://service.sap.com/sap/support/notes/947081]
If the locale for the Web Dynpro iView is changed in the portal (through portal personalization), this is not reflected in the running login session. The user needs to logoff and login again, in order to see the locale change in the Web Dynpro iView.
Regards,
Leo

Permissions Metadata User for System Connection in CE 7.2

Hi,
I want to create a system connection in NWA to an R/3 system with WSIL as service source. The Metadata User has SAP_ALL and SAP_NEW. But when I ping the system, following error is displayed: u201CUser credentials are valid but user does not have valid access rightsu201D
In Log Viewer following exception is listed:
[EXCEPTION]
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (403) Forbidden. The requested URL was:"Connect to http://XXHOST:xxPORT/sap/bc/srt/wsil?sap-client=030, used user to connect: XXUSER, used sap-client: 030"
at com.sap.esi.esp.service.server.query.discovery.WSTransportSettingsResolverSoa.resolveEntity(WSTransportSettingsResolverSoa.java:432)
at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.initialize(WSQueryImpl.java:351)
at com.sap.engine.services.webservices.espbase.query.WSQueryImpl.findWSInterfaces(WSQueryImpl.java:282)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.searchByPhysicalSystem(WSQueryComp.java:744)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.WSQueryComp.search(WSQueryComp.java:372)
at com.sap.esi.esp.wsquery.ui.wsquerycomp.wdp.InternalWSQueryComp.wdInvokeMethod(InternalWSQueryComp.java:458)
at com.sap.tc.webdynpro.progmodel.generation.ExternalControllerPI$ExternalInterfaceInvocationHandler.invoke(ExternalControllerPI.java:339)
If I open the WSIL-URL in browser with the metadata user, the xml-structure with the services is displayed.
We are on CE 7.2 SP3.
Hope, anybody has an idea.
Kind Regards,
Gerhard

Hi
Have you defined the HOST file entry? and , try with user having admin rights.
Best Regards
Satish Kumar

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

Get system connect information in WAD

Dear All,
I need using Javascript get system connect information in WAD,and using the connect information call RFC,How to do it?

by myself

SAP SNC 7.01 System connections documentations

Hello There,
Can someone share or point me to the location where I can find a document on SNC System connection with others systems...ERP, PI/XI and APO?
Thanks,
Kumar

Hi Kumar,
Please check following URLs.
http://help.sap.com/saphelp_SCM700_ehp01/helpdata/en/57/6634418b718739e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_SCM700_ehp01/helpdata/en/46/c2f65196b9453bbc60c975888ce1b5/frameset.htm
http://help.sap.com/saphelp_SCM700_ehp01/helpdata/en/46/c2f65196b9453bbc60c975888ce1b5/frameset.htm
Regards
Datta

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

Source system connection problem in BI

Hi ,
While checking source system connection we are getting below error
" BI IDoc type ZSBP055 is not the same as source system IDoc type ZSBP120"
could please guide on this .
Regards
vamsi

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

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

BW to R/3 system connection

Similar Messages

Maybe you are looking for