Connect BW to another Source System

Hello Gurus,
I have a problem. We have to connect a BW Dev System to R3 Dev System, but I want to do some DEMOS to my client so I need to connect the same BW DEV System to another DEV System (IDES). When I finish the DEMO I should connect this BW DEV System to R3 Dev System again.
Somebody knows some procedure to achieve this?
Thanks
Gustavo

I Think you should create a new Source system, and activate the content again in this new source system (RSA5).
Then you do the demos with the data of the new souce system.
Hope it helps.
Sebastián.-

Similar Messages

Configuration Wizard-NW:BI-AS ABAP(Connectivity of BI and Source System): M

Hi friends,
I´m configuring the (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain) in NWA using Configuration Wizard.
But there is the error in step (NW: BI - AS ABAP (Connectivity of BI and Source System): Maintain > Scenario UI: NW_BI_ABAP_DEFAULT > Scenario Process: Abap Server Integration to BI > Configuration Process > Configuration Unit: Initialize > Config Unit BI System: Initialize > Customizing: Assign Logical System to Client > Write Customizing data to Table T000)
Below error log:
*Write Customizing data to Table T000*
Description:
Exception in step "WriteProfile_1223390220410"
Exception details : com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException: Exception during the import of the profile!
State
Step finished with error
Support Information
Type of Action
WriteProfile
Debug Events
WriteProfile:Write Customizing data to Table T000
Library: sap.com/tclmconfig~bs
SourcePath ./com_sap_nw_bi_abap_default_maintain/ext_12064772269223/ext_1206447991146/Process_1207123636083/proc_1196064316796/Process_1204300420808/proc_1204300371034/WriteProfile_1223390220410
Time 2011/11/03 at 15:36:57
Schema content/NetWeaver/Common/Customizing/Clients/T000.xsd
Type : View Maintenance
Input
<TABLE_T000 xmlns:expr="http:/sap.com/ctc/expressions"><T000><MANDT>100</MANDT><LOGSYS>SOLCLNT100</LOGSYS></T000></TABLE_T000>
Schema
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:vma="http://www.sap.com/ctc/vma"
elementFormDefault="qualified"> <xsd:element name="TABLE_T000" type="TABLE_T000"></xsd:element> <xsd:complexType name="TABLE_T000"> <xsd:sequence> <xsd:element name="T000" type="T000"> <xsd:annotation> <xsd:appinfo
source="http://www.sap.com/ctc"> <vma:vmacontext table="T000" isupdate="false"/> </xsd:appinfo> </xsd:annotation> </xsd:element> </xsd:sequence> </xsd:complexType> <xsd:complexType name="T000"> <xsd:sequence> <xsd:element name="MANDT" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="MANDT"/> </xsd:appinfo>
</xsd:annotation> </xsd:element> <xsd:element name="LOGSYS" type="xsd:string"> <xsd:annotation> <xsd:appinfo source="http://www.sap.com/ctc"> <vma:vmaproperty column="LOGSYS"></vma:vmaproperty> </xsd:appinfo> </xsd:annotation> </xsd:element
</xsd:sequence> </xsd:complexType> </xsd:schema>
Destination parameters
user : SOLMAN_ADMIN
password : % secure content %
host : cdsolman
sysnr : 01
client : 100
language : en
Stack Trace
Caused by: com.sap.tc.lm.ctc.cul.api.CULServiceException: Exception during the import of the profile!
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:98)
 at com.sap.tc.lm.ctc.cul.serviceimpl.process.WriteProfileControllerImpl.execute(WriteProfileControllerImpl.java:160)
 ... 16 more
Caused by: com.sap.tc.lm.ctc.cul.cpi.context.ConfigurationBrokerException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='xml_parsing_exception', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key xml_parsing_exception
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:79)
 at com.sap.tc.lm.ctc.cul.serviceimpl.writeProfile.CULServiceWriteProfileImpl.writeProfile(CULServiceWriteProfileImpl.java:95)
 ... 17 more
Caused by: com.sap.tc.lm.ctc.provider.vmaprovider.exceptions.VMAProviderBaseException: Incorrect XML
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:349)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.setXmlValue(VMAUtil.java:250)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeContext(JCOProfileExecutorImpl.java:310)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeChildNode(JCOProfileExecutorImpl.java:183)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.JCOProfileExecutorImpl.executeProfile(JCOProfileExecutorImpl.java:129)
 at com.sap.tc.lm.ctc.provider.vmaprovider.VMAWriteProfile.writeProfile(VMAWriteProfile.java:59)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:144)
 at com.sap.tc.lm.ctc.cul.broker.BrokerWriteProfileImpl.writeProfile(BrokerWriteProfileImpl.java:73)
Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)(:main:, row=1, col=637) -> com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)
 at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
 at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:76)
 at com.sap.tc.lm.ctc.provider.vmaprovider.util.VMAUtil.getDocument(VMAUtil.java:341)
Caused by: com.sap.engine.lib.xml.parser.ParserException: Incorrect encoded sequence detected at character (hex) 0x6f, (bin) 1101111. Check whether the input parsed contains correctly encoded characters. Encoding used is: 'utf-8'(:main:, row:1, col:637)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:209)
 at com.sap.engine.lib.xml.parser.readers.EncodedDataReader.read(EncodedDataReader.java:207)
 at com.sap.engine.lib.xml.parser.helpers.AdvancedXMLStreamReader.read(AdvancedXMLStreamReader.java:143)
All the others steps were finished successfully
Only this step is with error. I don´t know that to do.
Regards,
Ricardo Arriado
Edited by: Ricardo Arriado on Nov 4, 2011 6:24 PM

Hi,
Please double check the JCO user and the authorization.
Or
Apply these two notes, it should resolve ur issue
1493124 CTC: Check table existence before table whitelist
1471762 CTC: Automated Configuration:
Hope this helps u.
Best Regards
Vijay K

Connection Between R/3 Source System to SEM Target System

Hi BW Experts,
We have R/3 Server, BI Server and SEM Server in our organization.
For SEM purpose, they need 0PCA_C10 (PCA Line Item Data). But generally we will load all Actual data from R/3 to BI System then BI System to SEM System.
But we dont need 0PCA_C10 Data in BW System. Because there will be 15 Crore Records in 0PCA_C10 Infocube. We want to update this data from R/3 to SEM directlty.
Is it possible to connect the R/3 Source System to SEM System?? If Yes, please tell me the steps.
Thanks in advance
Regards,
Anjali

No replies..Closing Thread.

Connecting to R/3 source system from BI in ECC6.0

Hi all,
We have installed ECC6.0 system recently with two clients say 500 for R/3 and 600 for BI7.0.
we would like to know how to establish connection between these two clients?from BI7.0 >RSA1>Source Systems-->we do not have any source system assigned here(i.e. SAP folder has nothing under it).
Does anyone has documents on this?please share with me.
Regards,
Murali.

Hi Murali,
Following are the stpes to be performed
1)Before any developments create a user ALEREMOTE through transaction code SU01. This user name is to be created in both the BI system and the R/3 system
Enter the requisite details for the same like address, Logon date, defaults, parameters, roles, profiles, groups, personalization and license data. Remember to assign the SAP_ALL and R_RS_ALL in the profiles
You can create the system-generated password by clicking the wizard button.You can also choose the password of your choice. Its important to note that keep the password same for the user ALEREMOTE common for both the BI and the R/3 system.
2) In the same way create another user BWREMO
3) Define the logical system in BI
Click on SAP reference IMG in SPRO Transaction
For BI 7.0 the procedure is different. It is as follows. Click on SAP Netweaver Business intelligence Links to other source system General connection settings, then click on define logical systems.
For the earlier version BW 3.5 and earlier follow the following steps. Then drop down the BW customizing implementation guide. After that Business Information Warehouse Link to other systems  General connection settings then click on Define logical systems
Click on new entries and enter the logical system name and description
Press the New entries button
Enter the client, city, logical system name, currency, and client role. Select the radio button automatic recording of changes and the rest will remain the same. After that click on save and then back and then save again.
4) Define logical system in SAP R/3 in similar way
5)Go to R/3 connection in BW 3.5 or go to ABAP connection in BI 7.0. Then click create.
6)Now create two RFC destinations for BI, one for direct remote login and the other through the Dialog screen.
7Creating RFC destination for BIW.
a.     Create a RFC destination NB1CLNT500 with the name for logical systems. The other destination would This destination would be used for BW  BW interaction. The same would be for theNB1CLNT500_DIALOG.Now click on connection test and there should not be any error. Now check by clicking the Remote Login button and this will take you to the R/3 system.
8.     Creating RFC destination for Dialog
a.     Create a RFC destination with the name of and NB1CLNT500_DIALOG in BIW with the name for logical systems. This destination would be used for BW  SAP interaction.
9.     The process is finished now.
10.     Now your connectivity is successfully established with the R/3 system.
Please assign points if this helps
Thank you,
Regards,
Senoy

Can oracle 8.1.6 connected BI as a source system

Hi Gurus,
Can Oracle 8.1.6 be connected to BI as a source system? and also Access 97 integration to BI>
Regards,
Jaya.

No cross posting
Read the "Rules of Engagement"
Regards
Juan

Connecting MSSQL as new source system

Dear all,
We want to connect a MSSQL server as a new source system in SAP BW 7.0.
Does anybody has a good "How to..." Paper which helps to connect MSSQL step by step to SAP BW?
Thanks a lot.
Regards
Daniel

Follow the below mentioned steps to create a dbconnect source system.
1. Goto RSA1 -> Source systems. Right click and Create
2. Give some name and description and hit enter
3. a. Con Name : Any name (SQLSRV, etc)
b. DBMS : MSS
c. UserName : Any username which is present in the SQL Server. Eg: SA.
If you have to use Windows Authentication, there is a seperate method :
For windows authentication, you will have to add your Admin login of BI Server to the SQL Server Security logins group (For Eg: If BI Server name is BID and the admin login for this server is BIDADM, you need to add BIDADM to Logins/Users group of SQL Server and also for the specific database).
d. Password : Anything.
e. Con Env : MSSQL_SERVER=<sql server name> MSSQL_DBNAME=<database name> OBJECT_SOURCE= DBO.
For Example:
MSSQL_SERVER=ps14apollo MSSQL_DBNAME=PROJECTSERVER_REPORTING OBJECT_SOURCE=DBO
Here ps14apollo is my SQL Server name. Similarly ProjectServer_Reporting is my database name. DBO should be the Object_Source for most of the SQL Server dbs. I think it should work in your case as well.
f. DB RECO = select or let it remain unselected.
g & h Max Connections & OPT Connections = 0, for unlimited connections.
Regards,
F-S

Source system icons changes when connecting SAP BW to mySAP ERP 2004

Hi,
Just an Interesting observation in relation to the creation of source systems in SAP BW to SAP Web AS 6.40 based systems (mySAP ERP 2004, mySAP SRM, etc).
I thought it would be interesting to share!
The behavior is logical but can be a surprise for a BW administrator who is not aware of the new internal SAP BW systems within mySAP ERP 2004.
Scenario:
The customer was connecting a stand-alone BW system to two new systems with latest and greatest mySAP ERP 2004 (ECC 5.00) and mySAP SRM.
Observation:
In the past the SAP R/3 source system would be created with a "SAP R/3 icon" indicating a SAP Source system.
As of mySAP ERP 2004, the source systems will be created in the SAP BW standalone system with the "SAP BW System icon".
Note: This is also the same behavior for new releases of mySAP SRM, and other SAP applications that are based on SAP Web AS 6.40 or greater
Why?:
The standalone SAP BW system is connecting to a system that contains an internal SAP BW system. The standalone SAP BW system determines that it is possible to extract both from the internal BW System and from the Plug-in extractors. It simply denotes that this source system is a SAP BW system and uses the BW Source system icon. (Remember SAP BW is client independent*!).
Note: This behavior will still occur even if you do not use the internal SAP BW system within mySAP ERP! It is there whether you use it or not.
Second Note: You can still use the ERP Content extractors from the mySAP ERP Source System as you did in prior releases.
Another related observation:
I would expect that this case will probably be true even if you only use the internal SAP BW.
Scenario: You use the internal SAP BW in another client in the mySAP ERP system than your ERP processing.
Result: The connection between the BW client and the ERP client source system(s) (i.e. client 001 for ERP, client 100 for BW), both the 'myself' and ERP client source systems, will show up as BW source systems!
Source system 001 and source system 100 will be displayed as SAP BW icons because SAP BW is client independent*
user master and authorizations are client dependent
I hope this was interesting.
Cheers,
Mike.

Hello,
I used my user id to login. I recieved a message :
User already exists in source system I continue:
Anothre window pops up : "Check RFC connection" and it asks
'RFC connection already exists in source system . Do you want to check, use or cancel source system connection'
Here I select Use - but i get an error : Error in source system'.
how can i track down this error.
Kindly inform.
Regards,
Nikekab

Connection between Source Systems and BW

Hello,
I´m trying to connect our SAP BI 7.0 system to SAP R/3.
At the following link, the topics for connecting BW with SAP source systems aren´t mentioned in detail:
http://help.sap.com/saphelp_dm40/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
I already have setup and tested the RFC-connections, so I primarly need a step by step description for the ALE settings (Partner profiles,Port, IDoc types,IDoc segments) in the
context of BW-SAP R/3 connectivity.
Thank you for your postings
Best regards
Mehmet

Hi Srini,
Thank you for you´re answer.
I have checked WE20 and W21. The ports and the partner profiles are created automaticly in BW and R/3 sides, when creating the new source system in RSA1.
The main problem is, that the R/3 can´t send data to BW, although the ALE and RFC configurations are setup properly. After I replicated and activated several data sources in BW succesfully, I´m requesting data from the R/3 system with an infopackage, but after a few hours the follwing failure message occurs in the monitor :
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
In the TRFC (SM58) log in R/3 there appears an status text with the following entry:
"No service for system SAPABC client 123 in the integration directory".
For this entry I have found the SAPnote 940313. In this note,there is described how to send Idocs over Integration Server. Now I think that our R/3 system tries to send Idocs over the Integration server too.
But is there another alternative to send Idocs from R/3 to BW without using the Integration server?
Best regards
Mehmet

Bi content with source system connection

Hello all,
I am in BI 7.0 DEV SEVER, I WAS CONNECTED TO TWO SOURCE SYSTEMS X,Y, IN BOTH SOURCE SYSTEMS I WAS REPLICATED DATASOURCES, THEN I AM GOING TO INSTALL BUSINESS CONETENT FOR ONE CUBE WITH DATA FLOW BEFORE AND AFTER, IT WAS CONNECTING TO SOURCE SYTEM X, BUT I WANT TO USE SOURCE SYSTEM Y.
IS THERE ANY PROBLEM WHEN INSTALLING BUSINESSS CONTENT WITH ONE SOURCE SYSTEM X,EXTRACTION DONE BY OTHER SOURCE SYTEM Y.
OTHERWISE I WANT TO INSTALL BUSINESS CONTENT FROM SOURCE SYSTEM Y,WITH OUT DELETING SOURCE SYTEM X, HOW CAN I CHANGE TO SOURCE SYSTEM Y.

Hi,
you can't install BI content infocube for one source system and do the extraction in another source system.
when you are installing the BI content you can maintain source system assignment for one or more source system like X, Y for both.
if you don't have Y source system means create it or change the exiting source system..
hope this give you an idea
Regards
Harikrishna N

Connecting SAP BW to SAP R/3 : Creating source system manually/automaticall

Hello All,
I have created the RFC connection between R/3 and BW system .The message types also have been defined and partner profiles have been generated.
When I am trying to create SAP source system in RSA1 --> Source system it asks me for the SAP Target server name, system ID and System number. After providing this it asks for ALEREMOTE users password in source system and target system.
Shouldnt this be blank!!!
Should this be provided separately by BASIS or shoudl it be the once we define while creating RFC Connections?
Kindly reply.
Regards,
NIKEKAB

Hello,
I used my user id to login. I recieved a message :
User already exists in source system I continue:
Anothre window pops up : "Check RFC connection" and it asks
'RFC connection already exists in source system . Do you want to check, use or cancel source system connection'
Here I select Use - but i get an error : Error in source system'.
how can i track down this error.
Kindly inform.
Regards,
Nikekab

Source system connection problem

Hi Gurus,
Data was loading from r3 to BI. But while loading, the job in the source system got cancelled in R3 with error, Job also cancelled due to process termination. See the system log. When I checked for the connection test of the source system I get an error, Result of the destination check: Error when opening an RFC connection (CPIC-CALL: ' ThSAPOCMINIT' : cmRc.
Please suggest possible actions that I need to take.
Thanks

Hi
Please go through the below link on how to create RFC connection
RFC Destination BW could not be created
Why you are loading that much huge data at a time..is you business required like this..?
Can't you split the data and run..?
Regards,
Venkatesh

Source system connection in RSA1

Hi,
I am not able to create a source connection under the SAP source system in RSA1.
Though I create a source connection under SAP source system, it gets automatically created in BI system.
I would like to create it under SAP source ssytem.
Please guide.
Thanks,
Rajiv

hii rajiv,
Check the foll links:
<link farm removed by moderator>
hope it helps,
regards,
raghu.
Edited by: Raghu on Nov 12, 2008 11:38 AM
Edited by: Siegfried Szameitat on Nov 12, 2008 11:46 AM

Problem in creating DB Connect source system

Hi All,
Iam creating a DB Connect source system to a legacy ORACLE database.
Since my legacy database is ORACLE, I have given the TNS name as the connection info.
The source system got created successfully. but the problem is, upon clicking on 'datasource overview', the system has to generate an application component hierarchy. But it is showing the same application component hierarchy which is there for flat file source system, and iam not getting the option to "select Database Tables" where i can create and edit the datasource.
please help me out.
help would be appreciable and carry reward.

Hi,
Create source system first.
you have to select the option "Database system (Data and meta data using SAP DB Connect)".
Now enter the database specific information.
DBMS:
Username:
Pwd:
Conn. Info:
Conn. Info should be the TNS name if it is oracle database.
after giving the relevent information save it, and come back. Source system will be created.
Now right click on source system and select the option " select Database Tables". it will show you the list of tables or views on that database.
select the table/view on which you need to create data source, and click on "edit datasource" there you can generate datasource.
after creating the datasource, replicate it... adn proceed.
any doubts plz ask me.
Message was edited by: suman dara

Connection of 1 source system to 2 Target system

HI ,
We are in the midst of upgrading the hardware for our BW box.
At present old box is as follow:
1)BWQ connected to source QAS
2)BWP connected to source PRD
The new box is called FWP. We are testing on the new FWP by establishing connection of FWP with source system QAS.
This mean, source system QAS is connected to 2 boxes at the same time.
old BWQ-QAS
new FWP-QAS
I would like to know if we perform data load in new FWP, what will the impact be. Will that impact the delta queue in source system QAS? If i trigger load in FWP, does that mean we will loose the delta whn data is triggered in BWQ?
Regards,
Maili

Hi,
Since itu2019s a new box this will not impact to old box, but we need to develop everything from start in new box or you can copy from the Old.
We also have something like it.
Check the below link which will help you.
Re: Replicating data sources during upgrade of Source system
Hope it Helps..
Edited by: Rakesh BI on Apr 26, 2011 10:03 PM

Error: Source system already exists. Message no. RSAR201. Points rewarded.

Error: Source system already exists. Message no. RSAR201
We have installed a BI 7.0 system recently and I am setting up the server to connect to SAP ERP.
In TA SM59 a connection to the SAP ERP has been established. The Remote Logon is OK, (meaning clicking it nothing happens). The Connection Test is OK.
According to the Best Practices paper: B84: BI Connectivity (B84)
http://help.sap.com/bp_biv170/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
I have done the following:
In TA RSA1
1.     Choose Modeling.
2.     Choose Source Systems.
3.     Select SAP in the window on the right.
4.     Choose the Context menu (right mouse click).
5.     Choose Create.
6.     Make the following entries:
Available destination: (The above tested connection)
Background user in source system: RFCUSER (I created the user in ERP according to step 1.4 in B84)
Password for source system: *****
Background user in BI: RFCUSER (I created the user in BI according to step 1.4 in B84)
Password for BI user: *****
8.     In the dialog box Please log on as an administrator in the following screen choose Continue.
9.     Log on to the Source System with your administrator user. Choose the correct client.
10.     On the dialog box New Source System Connection choose Continue.
THEN I GET THE ERROR:
Source system already exists.
Message no. RSAR201
What is wrong? I cannot locate any SAP notes to help on this problem.
Best regards,
Carsten Pold

Hello Carsten,
just some guessing at this point...
a)
Is the connection really new? For example, was there another system connected to that ERP, maybe with the same logical name? Or was any of the two systems copied from another system?
b)
Authorisations issues in this process may result in strange error messages. Make sure that the admin user in step 9 really has SAP_ALL. There are a lot of complex activities that this user must be able to do (ALE management, RFC access etc.). To exclude issues with the RFCUSER users: If possible, give them SAP_ALL, too. Of course only temporarily for testing.
c)
I normally don't use existing RFC destinations. Usually, I let the system create those, too. So maybe it makes a difference if you remove the RFC destinations on both sides and try again. In that case, you will of course have to provide the RFC details when creating the source system connection...
I hope this brings you forward a little...
Regards,
Christian!

Connect BW to another Source System

Similar Messages

Maybe you are looking for