Connection to ByDesign with a ODP Source system: Logical port creation on CO_RSDSPX_ODP_IN

Hello,
I am trying to connect my ByDesign Could server to the our BW Server by an ODP Source system.
I tried applying what SAP recommend:
http://help.sap.com/saphelp_nw73/helpdata/en/46/b9297716c94e509fcbe62d3c795e85/content.htm?frameset=/en/c6/afacb707764885a6fb62f511c24f34/frameset.htm
http://help.sap.com/saphelp_nw73/helpdata/en/ca/14c0899cb04f16929b5d88e147fc8f/content.htm
http://help.sap.com/saphelp_nw73/helpdata/en/9e/c7a3591dc74a679bbc9716354e42af/frameset.htm
When trying to create a Logical Port on CO_RSDSPX_ODP_IN from SOA Manager with a WSDL Based configuration (downloaded from a Webservice of our ByD), this error is thrown:
SRT Framework exception: The WSDL document is not compatible with proxy class "CO_RSDSPX_ODP_IN": "Unsupported Operation(s):GetList, CloseSubscription, CloseSubscription, CloseSubscription, CloseSubscription, CloseSubscripti
Do you have any idea ?
Also, i was unable to use any Consumer Service directly ... I am not a Basis and don't understand what configuration needs to be done.
Thank you very much.

Hi,
Did you create consumer proxy for the service you like to consume ?
It looks like your WSDL and Consumer proxy are not the same ?
Or you could create Logical Port Manually, but it will fail on provider side because the message you are sending and the provider of the service are not the same.
Manual Configuration
The system uses a user-specified binding URL to create a logical port. You need to specify a unique name for the logical port.
Thank You
Regards
Gov

Similar Messages

Delta Loads failling after system copy with error in source system(RSM340)

Hi Guru's
We recently performed system copy in BI side.I am facing same issue in couple of chains.Process chains are failing at delta loads with error in source system(ERROR IN SOURCE SYSTEM-message no-RSM340 ).When I go for repeat option ,delta loads are running fine.I did some research regarding RSM340 and I found note:1576331.
But my system is not showing any 'Time Inconsistencies'.So.I was not able to find any clue about it.
Could anybody help me out in this aspect.
Thanks!!!
Kuldeep

Hi,
Check whether the profiles that ran in background have the following authorizations.
The RFC user on BW, receiving data from OLTP system, should have S_BI-WHM_RFC and S_RS_ALL in the user profile.
The RFC user on OLTP, receiving request from BW system, should have S_BI-WX_RFC, S_IDOC_ALL, and, B_ALE_ALL in the user profile.
Regards .

Connect one SAP ECC 6.0 source system to 2 SAP BW system

Hi!
I copied SAP BW system (e.g. BW1 --> BW2).
My source SAP BW system "BW1" was connected to SAP source system "MM5" (tcode RSA1).
Now I would like to connect my new SAP BW system "BW2" also to this SAP source system "MM5".
When I do so I get the following error:
Connection cannot be used.
Connection BA is used in the MM5:400
source system as a connection BW1CLNT001 to BW
Do you want to delete this connection in the source system?
Question:
Can one SAP ECC system be connected to 2 SAP BW system?
If yes, what are the steps to do this?
Thank you!

Thank you very much!
The question still is how to proceed with the following dialog screen/warning?
Connection cannot be used.
Connection BA is used in the MM5:400
source system as a connection BW1CLNT001 to BW
Do you want to delete this connection in the source system?
YES or NO
Thank you!

Virtual Infoprovider with DB2 as source system.

Hi Experts,
Can we create a Virtual / Remote Cube with DB2 as a source system.?
Are there any specific systems that are supported by SAP to create a Virtual infoprovider.
Thanks in advance.
Regards,
Hardik Luthra

Hello
we have the same problem.
the problem is a security-problem that the user SAPServiceSID isn't in the group DB2ADMNS.
After Restart Service and SAP the db2-connect runs fine
regards Siegfried Dörfler / W&W-Informatik

Datasources . problem with the new Source System

Hi friends!
The ECC client were copy and now I have a new source system for this.
If I select source system / verify, the msg is: ok
In can read some data from the new ECC (ie: exchange rates updated), but I can not read any records using the datasources.
The replication in Bi were done, and the data in source system is ok.
-> What is wrong?
Thanks!

Check the profile parameters in WE20,We21... and also check scc4

Source System Logical Name change

Hello,
We are refreshing our R3Qas system with a copy of our R3Prd system. As part of this task our R3Qas logical name is changing from QASC230 to QASC200.
I am at the point in the refresh where I am beginning tasks on the existing BWQas system.
I Right Click on the source system representing the R3Qas system "QAS client 230" technical name: QASC230. I choose 'Restore' I then provide the logon information but the system it jumps to is the Old R3Qas not the new R3Qas.
I know that it is jumping based on the RFC, So I assume I can change that RFC to jump to the new system, what do you think? Also what about the Source System name an technical name, will it always be QAS Client 230 and QASC230 or can that be changed to reflect the new name of QASC200?
Thanks for your advice and assistance!
Nick

Since the BWQ system was already an existing system that was attached to the previous R3Q system, this task was essentially busy work.
The change that occured was that the existing R3Q system (Physical Name: QAS01 Logical Name: R3QASC230) was being replaced with a new R3Q system (A copy of Production was used) (Physical Name: QAS02 Logical Name: R3QASC200).
The actions that I needed to take to connect BWQ to the new R3Q follow:
1. On QAS02 visit TX SE37. and run RSAP_BIW_DISCONNECT, Choose 'Single Test'. For I_BIW_LOGSYS: I provided BWP001 which corresponds to the logical name of our Production BW system. For I_OLTP_LOGSYS: I provided R3PRDC200 which corresponds to the logical name of the QAS02 system (this system). I then Click 'Execute' and 10 seconds later this step is done.
2. On QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide BWP001. For the 'New Logical System Name' provide BWQ001. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the 'Mapping System Name'.
3. Again on QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide R3PRDC200. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (BASIS already did this step so a message appeared to that effect)
4. On the BWQ box visit TX: BDLS. For the 'Old Logical System Name' provide R3QASC230. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the at the prompt and run.
5. On BWQ create new RFC's based on the old ones to point at the new QAS02 system. Modify the old ones with an X in the 'Target Host' so they do not function.
6. Open up the BWQ client in SCC4. (or perhaps try SM30 to modify the table in the next step)
7. On BWQ visit TX: SE16. Tablename: RSLOGSYSDEST. Change the 'Old' reference to the QAS box to the 'New' information. (ie: R3QASC230 became R3QASC200).
8. On BWQ visit TX: WE20. Expand 'Partner Type LS', Select 'R3QASC200', click the classification tabe, change the 'Partn.Status' from I to 'A' and save.
9. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. Click 'Only Activate' when prompted. you will then get a termination message regarding the port description.
10. On BWQ Back at WE20: Expand 'Partner Type LS', Select R3QASC200, double click on RSRQST. Under 'Outbound Options' click the drop down for 'Reciever port' Select the 'new' correct system and 'Save'.
11. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. You will get a prompt to Use or Check, choose 'Use'. When prompted about 'Connection cannot be used' click 'Delete'. Logon again as ADMIN account, Click 'Continue' when you get the 'User exists...' prompt. Click 'Replicate as well' when prompted. you will then get a termination message regarding the port description.
You should be all set now!
Nick

Source System(Logical system) issue

Hi All,
Recently we have done QA refresh & copied with production data.
For 0vendor master data we are extracting data from ECC source system. When I was trying to execute the DTP it is pointing older source system. We tried to create new DTP but when I'm executing still it is showing older system.
By using RSBKDTP_BDLS program I forcefully tried to convert old source system to new source system but we are unable to solve this issue.
Here I'm attaching the issue .Please help on this issue.
Best Regards,
Sammar.K

Hi Ram,
I have compared Production & QA system entry's in RSLOGSYSMAP Table.
in prd system
source       target
qa6            prb01
in qa system
source       target
qa6             qa6
we found in qa it is pointing wrong target.
Regards,
Sammar.K

Connecting macbook pro with tv that only has dvi port

Hi community -
I have a macbook pro and a minidisplay port --> hdmi adapter. I'd like to connect my macbook with a tv that only has a dvi port. Can I use a hdmi --> dvi cable on the minidsiplay port? Will that work? Thanks for your help.

Welcome to Apple Support Communities
You have to get a Mini DisplayPort to DVI adapter and a DVI cable > http://store.apple.com/us/product/MB570Z/B/mini-displayport-to-dvi-adaptor?fnode =51 Unfortunately, you can't use the Mini DisplayPort to HDMI adapter to connect to a TV with DVI

Connecting Websphere MQ with another open source Queuing System

Hi everybody,
i work in a company that has already purshaced Websphere MQ as MOM, and we have some clients that unable to buy it. So is it possible that we find an open source queuing system such as ( openMQ, ActiveMQ ....) able of sending messages to a websphere MQ over a secured channel. I couldnt find any site on the internet that's telling me straightforward that this or that queuing system is able to connect with websphere MQ. So i'm begining to believe that it's impossible to have 2 different queuing systems working together and that it has to happen through an application server. Is that true ?? that every queuing system could only send messages to the same system and if not what open source queuing systems i can use with Websphere MQ ?? I'm really puzzled and hope anyone could help.
Thank You

Thanks. James.
I posted the same message to servicemix user forum.
I have tried including jboss client jars and wl jars in classpath. I started servicemix. It looked OK without errors. However when I publish jms meesage in the destination in jboss (servicemix was supposed to sub the msg from the jboss destination and pub it to wl destination), I got the following errors
C:\incubating-servicemix-3.0-SNAPSHOT\examples\jms-bridge>servicemix servicemix.xml
Apache ServiceMix ESB: 3.0-SNAPSHOT
Loading Apache ServiceMix from file: servicemix.xml
INFO - JBIContainer - Activating component for: [container=ServiceMix,name=#SubscriptionManage
INFO - ComponentMBeanImpl             - Initializing component: #SubscriptionManager#
INFO - DeploymentService              - Restoring service assemblies
INFO - JBIContainer                   - ServiceMix JBI Container (http://servicemix.org/) name: ServiceMix runni
INFO - JBIContainer                   - Activating component for: [container=ServiceMix,name=myJmsReceiver] with
INFO - ComponentMBeanImpl - Initializing component: myJmsReceiver
INFO - JBIContainer - Activating component for: [container=ServiceMix,name=transformer] with s
INFO - ComponentMBeanImpl - Initializing component: transformer
INFO - JBIContainer - Activating component for: [container=ServiceMix,name=transformedSender]
INFO - ComponentMBeanImpl - Initializing component: transformedSender
INFO - JBIContainer - Activating component for: [container=ServiceMix,name=myJmsSender] with s
INFO - ComponentMBeanImpl - Initializing component: myJmsSender
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
ERROR - ServerThread - socket timed out
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
at java.io.FilterInputStream.read(FilterInputStream.java:66)
at org.jboss.serial.io.JBossObjectInputStream.read(JBossObjectInputStream.java:140)
at org.jboss.remoting.transport.socket.ServerThread.readVersion(ServerThread.java:464)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:381)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:498)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:240)
Note: please ignor the transformer which I did not use it in the test. My servicemix.xml is
<?xml version="1.0" encoding="UTF-8" ?>
<beans xmlns:sm="http://servicemix.apache.org/config/1.0" xmlns:foo="http://servicemix.org/demo/pipeline/">

<sm:container id="jbi" embedded="true">
<sm:activationSpecs>
<sm:activationSpec componentName="myJmsReceiver" service="foo:myJmsReceiver" destinationService="foo:jmsSender">
<sm:component>
<bean class="org.apache.servicemix.components.jms.JmsReceiverComponent">
<property name="template">
<bean class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory">
<ref bean="jbossConnectionFactory" />
</property>
<property name="defaultDestination" >
<ref bean="jbossSourceDestination" />
</property>
<property name="pubSubDomain" value="true" />
</bean>
</property>
</bean>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="transformer" service="foo:transformer" destinationService="foo:transformedSender">
<sm:component>
<bean class="org.apache.servicemix.components.xslt.XsltComponent">
<property name="xsltResource" value="classpath:org/apache/servicemix/components/xslt/transform.xsl" />
</bean>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="transformedSender" service="foo:transformedSender">
<sm:component>
<bean class="org.apache.servicemix.components.jms.JmsSenderComponent">
<property name="template">
<bean class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory">
<ref local="jmsFactory" />
</property>
<property name="defaultDestinationName" value="demo.cheese.result" />
<property name="pubSubDomain" value="true" />
</bean>
</property>
</bean>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="myJmsSender" service="foo:jmsSender">
<sm:component>
<bean class="org.apache.servicemix.components.jms.JmsSenderComponent">
<property name="template">
<bean class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory">
<ref bean="weblogicConnectionFactory" />
</property>
<property name="defaultDestination">
<ref bean="weblogicTargetDestination" />
</property>
<property name="pubSubDomain" value="true" />
</bean>
</property>
</bean>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
</sm:container>
<bean id="jmsFactory" class="org.apache.activemq.pool.PooledConnectionFactory">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQConnectionFactory">
<property name="brokerURL" value="vm://localhost?broker.persistent=false" />
</bean>
</property>
</bean>
<bean id="jbossJndiTemplate" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">
org.jnp.interfaces.NamingContextFactory
</prop>
<prop key="java.naming.provider.url">
jnp://L71037263:1099
</prop>
<prop key="java.naming.factory.url.pkgs">
org.jboss.naming:org.jnp.interfaces
</prop>
</props>
</property>
</bean>
<bean id="jbossConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="jbossJndiTemplate"/>
</property>
<property name="jndiName">
<value>ConnectionFactory</value>
</property>
</bean>
<bean id="jbossSourceDestination"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="jbossJndiTemplate"/>
</property>
<property name="jndiName">
<value>topic/testTopic</value>
</property>
</bean>
<bean id="weblogicJndiTemplate" class="org.springframework.jndi.JndiTemplate">
<property name="environment">
<props>
<prop key="java.naming.factory.initial">
weblogic.jndi.WLInitialContextFactory
</prop>
<prop key="java.naming.provider.url">
t3://enic01.ed.ray.com:7001
</prop>
</props>
</property>
</bean>
<bean id="weblogicConnectionFactory"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="weblogicJndiTemplate"/>
</property>
<property name="jndiName">
<value>mil/dcgs/jms/mdf/catalogConnectionFactory</value>
</property>
</bean>
<bean id="weblogicTargetDestination"
class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiTemplate">
<ref bean="weblogicJndiTemplate"/>
</property>
<property name="jndiName">
<value>topic/GMTIDetections</value>
</property>
</bean>
</beans>
Thank you very much if you have any idea on it!!!!!
By the way, I wonder how the servicemix jms bridge works. did I use it correctly?
-

Using ChaRm with 2 Development (source) systems

Good Day;
Before I get into the full description of an issue we are facing. I would like to know if anyone out there is using ChaRM and has 2 development systems defined.
Regards
Don

Thanks Avinash
This is the problem I am having
We have 2 landscapes each with a development and quality system. Also there is a single volume test system. Both landscapes point to a single production system. So it would look like this
DW3           DW4
QW1           QW2
           VW1
            PW1
The DW3 landscape is defined as the production landscape (normal releases) and the DW4 landscape is defined as the emergency landscape. The emergency landscape is synchronized with the production landscape during a normal release.
The migration path for a normal release would be DW3, QW1, VW4, (now synchronizing) DW4, QW2, PW1.
The migration path for an emergency fix would be DW4, QW2, VW4 (if performance testing is required), PW1.
All these systems are defined in the ChaRM landscape
When a task list is generated, you are asked which development system, DW3 or DW4. When the task list is generated, it starts at DW4, QW2, PW1, DW3, QW1, PW1 (We have not defined a volume VW4 system in or test landscape).
As well when a creating a transport, and DW3 is selected, ChaRm generates an error stating the task list is out of sequence,
You will notice that the task list goes to PW1 twice. Is there a way to generate the task list in the correct order. DW3, QW1, DW4, QW2 and PW1.
Regards
Don Newton

How do i connect a pod with an apogee duet into logic

I am running a line 6 pod 2.0 and am new to logic. I was wondering if someone could walk me through connecting it to a apogee duet and record into logic thanks

I have an Ensemble and a X3 Live but I imagine it's similar. I run two lines from the pod into the Apogee device. Then set up two audio tracks, one with Input 1 and the other with Input 2. Arm the tracks to record and you should be set. (You can also do it with a single track, just using one line out.)

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.

Connecting two BW systems to the one R/3 source system

Hi all!
I have to connect two BW Systems to one R3 system. In our last tests we have had problems trying to connect two BW servers simultaneously with R/3 source system because it allows only a logical system name for each R/3 client, and (We guess that we need to define tow diferent logical system name, one for each connection). This has been generating errors when we try to load data from R/3 to BW because, we guess, R/3 does not recognize the BW source system in the ALE connection for someone BW systems at transfer data. In this moment I have one connection active (BW1-R3). The BW2-R3 connection is already inactive. Does anybody know how perform this? we need solve the transfers problem as soon as possible.
Thanks! Judi

Ah...
please don't post twice the same question...in these forums we are always the same !!!
You can close this thread to avoid to look in two different posts...
Bye,
Roberto

BEx Integration with different source systems

Hi All
I know we can create BEx querys on top of an infoprovider. But instead of storing data into BW and creating reports using BEx tools can we integrate BEx with the other source systems. Like Business Objects tool which can be integrated with different sources. My client wants to know whether we can integrate with BEx for the following
Support data source -- SAP BW
Support data source -- Oracle
Support data source -- MS SQL Server
Support data source -- MS Access
Support data source -- MS Excel
Support data source -- ASCII Text files
Support data source -- XML/XSD
Support data source -- Web Services
Support data source -- SAP R/3
Support data source -- BO Universe
Thanks for letting me know your opinions

Hi,
in theory you can. You will still have a virtual provider on top of your Infosource which will be connected to your datasource; thus you'll have to create the structures; you'll have to load master data as well... so not so nice solution if you think that at this stage, the storage will be the less of your costs....
How are you going to deal with R/3 data?? I mean a great advantage of BW is really when you have an R/3 behind...
I'd rather consolidate all these disparate datasources using the Visual compsoer which can get this data out of nearly an datasource and merge them in one single report; in theory again you could implement all BEx functionalities but at which cost and effort??
Weird that a customer is asking such a question because it is usually the other way around: use SAP BW data in another front-end... by the way SAP is going to acquire BO soon....
hope this helps...
Olivier.

BW: Connect to new source system via special transport

Hello everyone!
I have a BW system connected to an R/3 source system. I have made a copy of the source system. Now I want all my models to be connected to both source systems. I heard that this can be achieved via special transport (i.e. place all source system dependant objects into a special transport request to be imported back into my BW system, but with the new source system assignment). Does anyone have any documentation on how to do this?
Best Regards and Merry Xmas!
Luís Andrade.

Hi Luis,
There are two parts,
1) If you want to transport all your objects from current R/3 system to newly created r/3 system then you can create a TR and use it in SCC4 transaction during client copy. In the same fashion you can use RSA1---> transport connection and use the TR for system copy. After that once you release this TR all the objects will move from one system to another.
2) But if you have already moved all the objects in source system but now you want them to replicate in BI then go to SAP BI system select your source system and then from the context menu choose replicate datsources option, it will fetch everything from respective source system in BI.
Regards,
Durgesh.

Connection to ByDesign with a ODP Source system: Logical port creation on CO_RSDSPX_ODP_IN

Similar Messages

Maybe you are looking for