Error connecting multiple BW systems to one OLTP system

Hi BW Gurus,
As part of a major project we had to create a copy of our production BW system and thus have two BW systems connected to one production R/3 system. Before we proceed with the production systems, we decided to try it out with our staging systems.
1) Created a copy of STG BW (already connected to STG R/3) and renamed it to TST BW.
2) Transaction BDLS, renamed the logical system ID
3) Made sure all partner profiles were available and active
4) Since there was no connection between TST BW and R/3 STG, tried to activate the source system in TST BW. As per OSS note 886102, tried the restore functionality but we are running into a strange error.
Table RSBASIDOC in the source system already has an entry for STG R/3 and STG BW with IDOC TYP ZSSA015 and Prefix "SA" and now it complains that since this prefix alrady exists, it cannot create another entry with the same prefix for TST BW and STG R/3. It gives us the option to delete the existing entry and create a new one for TST BW. This in turn de-activates the delta between STG BW and STG R/3 and we can successfully initialize with the new system.
This process turned the queue entry in RSA7 red for STG BW and created a new one for TST BW (green). Delta stopped working for STG BW.
How can I have both the systems connected and run delta process simulataneously? I have read OSS note 775568 but this is after the fact that the two systems are already connected.
If I have to start from scratch, can someone please outline the steps involved?
Do I have to restore the source system or is there an alternate way? I cannot see how the delta would work if there is no connection betweeen the two systems.
Do I even need to worry about initializing with the TST BW System or can I just run the delta process and it would automatically add another entry in RSA7.
Any help would be truly appreciated and rewarded!!
Thank You.
Sreedhar

Looks like a much bigger issue than that. We did create the partner profile in WE20 but that didn't help either. It still complains about the prefix. This 2 Character prefix value is actually derived as the concatenation of the first letter of the BW system name and starting alphabet in a sequence. In our example STG BW has prefix of SA and the basic idoc type is ZSSA015. Based on this, TST BW system should have prefix of TA and basic idoc type might be ZSTA016. The program initially looks at RSBASIDOC table for source system and finds value SA and complains that this cannot be used again.
I have seen messages in this forum where people have actually done this and hopefully someone would reply back as to how to resolve this issue.
My main question though is, do we have to restore or activate or do not have to do anything to the source system after the copy of BW systems? None of the above three options seem to work for us right now.
Any ideas?
Thank You
Sreedhar

Similar Messages

Two BW Systems to One OLTP Systems.

Hello experts:
We are in the process of connecting two BW systems one OLTP system. Currently the BW system is connected to one OLTP system.
I have many blogs here about this issue. But I am unable to see any answers on how to set this up. Table RSBASIDOC table(in the OLTP system) has only one entry. How can add another entry in this table to point to two BW Systems.
As alwasy points will be rewarded.
Regards,
N.S

Why it is better to filter in the BW system rather than in R/3 ?
I would like to avoid any changes in BW, because of:
- reducing data traffic
- in the source system we have more data(fields), that can be used as filter in EXIT_SAPLRSAP_001
The data sources are unfortunately the same for the both BW systems, so I cannot differ between them.
What do you think about these solutions:
1. Modification in the source system - to pass logical system of BW into EXIT_SAPLRSAP_001 (the logical system is available just before EXIT_SAPLRSAP_001 is called, but unfortunately is not passed as parameter)
2. Pass some dummy selection parameter from BW just to identify BW system ...
May be any other solutions ?

Two BW system to one OLTP system connection issue.

We are upgrading our BW systems to BI 7.0.
We are planning for a parallel Break-fix path. so we made a copy of our BW dev system(BW1)
BW2 is a copy of BW1 and plan to upgrade it to BI 7.0 .we plan to retire BW1 after upgrade is completed. When we try to restore connection for R/3 sourcesystem(S01), it gives a message with DELETE and DO NOT DELETE option
" The connection EA is used in S01 sourcesystem as a connection BW1 to BW
Do you want to delete this connection in the source system
The connection is restored after it is deleted successfully."
If i select "delete" it deletes connection to BW1 and restores connection to BW2, but if i select "do not delete" it is not creating a connection for BW2.
How do i restore connection for BW2 to S01 without deleting the connection For BW1 to S01.
I need to connect BW1 and BW2 to S011.Please let me know How can we do this?
Thanks
Shaik

hi,
please let me know what steps you have done - till now so that i can send you the remaining steps.
thanks
shaik

Is it possible to connect multiple R/3 systems to one APO system?

Hi,
Is it possible to connect multiple R/3 systems to one APO system?
Kind regards,
Kris De Smedt.

Hi Kris,
Yes, you can connect multiple R/3 systems to one APO system. All you need to do is to maintain connection parameters of all the R/3 systems with APO. (i.e. RFC Destinations, logical systems, partner profiles etc.)
Regards,
Naveen.

Connecting to Multiple ECC systems via one Gateway system(Dynamic System Selection)

Hi Experts,
We have multiple ECC systems and one Gateway server. We want to connect to these different ECC systems using one GW system.
I have created System Aliases for these ECC system in GW system. For a service, i added 2 system aliases.
Now we are looking for the solution where UI can provide the system alias (it wants to connect) as a parameter while calling oData Service.
Please help.
Regards,
Rohit

Hi Rohit,
we have a similar scenario where we have two system aliases for one service. Both aliases point to the same system, but different clients; it should not make a difference though, having different systems. The feature you are looking for is Multiple Origin Composition (MOC).
There are a couple of things you have to consider:
in the SEGW the entity to be called has to be marked as addressable
the URI of the service needs to include the tag for MOC (;mo) --> http://sapgw.domain.org:8000/sap/opu/odata/sap/ZSOME_SERVICE;mo/entityset
Without the ;mo the call will be routed to your default alias. The ;mo will route the call to both systems. Using MOC will generate an additional key property into your entities --> SAP__ORIGIN. The property is the alias. If you want to route to a specific system you have to provide the SAP__ORIGIN like providing normal key properties in your requests.
This will look like this:
<content type="application/xml">
<m:properties xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices">
    <d:SAP__Origin>SOME_ALIAS</d:SAP__Origin>
    <d:Identifier>SOME_IDENTIFIER</d:Identifier>
    <d:Doublet />
</m:properties>
</content>
The original Entity only consists of the key property "Identifier" and the property "Doublet". "SAP__ORIGN" is added via the ;mo.
Hope it helped...
Holger

Multiple Schema Creation with One Source system Via SLT

Hi all,
we have BW on HANA environment at our company premises, with SLT server installed
So, my Question is that is it possible to create more than one schema in HANA system with one Source system
As an example, lets say, ECC (Client 601) Source System has been connected to HANA via SLT and created Schema called SCHEMA_1 and again i want to create SCHEMA_2 by connecting same ECC (Client 601) source System.
please help me to short this out?
Thanks
Mirana

Hi Mirana,
Yes, it is possible to create more than one schema in HANA system with one Source system.
Please go through the Official SAP LT document for more details @ page number 13
http://www.saphana.com/servlet/JiveServlet/previewBody/1811-102-5-5419/SAP_LT_Replication_Server_for_SAP_HANA_SPS05_Over…

PO No range when we ink two SRM system with One ECC system

Hello Experts,
We have a client requirement to link Two SRM Systems with One ECC system.
In this case what number range we need to maintain in both SRM systems for PO.
-The number range of ECC PO should get update whenver the PO is transferred from any of the two SRM system.
-We have Extended classic scenario.
-Also PO Doc type is going to be same.
Can we handle this by increasing the buffer of the number range in one of the SRM system?
Any idea...pls help urgently.
Best Regards,
Anil
Edited by: anil.s.verma on Oct 1, 2010 4:33 PM

Hello Anil,
Being in Extended Classic Scenario (leading PO being in SRM, R/3 PO number range is concidered as external because PO number is given by SRM), the only solution for you is to:
1- give same number range interval for PO (internal in SRM system 1 and SRM system 2, external number range in R/3), e.g. 3100000000 - 3199999999
2- in SRM system 2, fill in current number with (for example) 3159999999 and let empty (or current value) in SRM system 1
3- assign, in each system for your concerned transaction type, number range as internal in SRM and external in R/3.
In this way, you will avoid overlaping in R/3 between PO numbers coming from SRM system 1 and SRM system 2
Regards.
Laurent.

Connecting Multiple R/3 Systems to one BW System / What is to be considered

Dear All,
I have the following requirements.
We have the following requirement to connect to 2 different R/3 systems (RS1 & RS2) to one BW System (BWS).
In BW , we will build two flows corresponding to project A et B. Both flows are independant.
In BW System (BWS) the flow for project A already exists.
We have to build the flow for project B
1. What is to be considered?
2. Is there any approach to be followed?
3.How to maintain or handle master Data and infoojects issues? This question because all standard Infoobjects will be used by
both.
4. How can i differenciate between data comming from system RS1 & RS2?
5. How to get only data for the corresponding system loaded?
6. What are the points to be considered?
7. What about the authorization?
8. Any Document or how to?
Thanks

Hi Gilo
1. What is to be considered?
Nothing much, different ECC systems will have different logical system names, so creation of source system is not a problem. All the DataSource related tables also have LOGSYS name as a key. So you can identify same datasource from different sources
2. Is there any approach to be followed?
See below
3.How to maintain or handle master Data and infoojects issues? This question because all standard Infoobjects will be used by both.
Master Data need to be compounded with source system id if they are different in different system.
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6399e07211d2acb80000e829fbfe/content.htm
4. How can i differenciate between data comming from system RS1 & RS2?
Refer to ans of 3 for master data. Transaction data as you said would be in different flow altogether.
5. How to get only data for the corresponding system loaded?
You will have different PSA and InfoPackage for DataSources as DataSource is source system specific. So you can have completely independent process chain for each system.
Normally loading delta is not a problem, but loading CO-PA data from both the systems via delta method is not possible.
6. What are the points to be considered?
already discussed.
7. What about the authorization?
Authorization is based on BW objects, not source system. So that will remain same.
8. Any Document or how to?
Need to search
Check this thread
http://forums.sdn.sap.com/thread.jspa?threadID=1792256
Regards
Anindy
Edited by: Anindya Bose on Feb 16, 2012 8:29 PM

How to connect two BW systems to one ECC system?!?

Hi Experts!
We want to connect our ECC system (P11) to multiple SAP BW systems. Therefore we made a system copy of our productive BW System (P81) and create a new second BW System (T81). When I want to restore to connection to the P11 in the T81, Iu2019ll get the following error message:
u201CDie Verbindung CA wird im Quellsystem P11_001 als Verbindung zum BW T81CLNT001 genutzt.
Soll diese Verbindung im Quellsystem gelöscht werden? Nach erfolgreicher Löschung wird der Anschluss wiederholt.u201C
In English this message means something like that: u201EThe connection CA is used as a connection to the BW T81CLNT001 in the source system. Should this connection be deleted in the source system? This connection can be repeated after successful deletion.u201D
Now I ask myself: How can I connect our new BW System to our ECC System, without destroying the old connection to our productive BW system?!?
Have anyone of you an idea how we can handle this issue?
Thanks in advance!
Regards, Alex

Hi
This happens because of RFC settings duplication as your new BW system is copied from Old one.
First you restore the Production system connection by deleting the existing RFC. But this will delete the new connection you have created ( that is what your dialog message is saying)
Basically , before creating new connection you need to delete some table entries manually , then you can connect both the system to your same source system
Please find the link below where I mentioned the table names from where you need to delete duplicate entries manually.
How to delete old source system assignment and assign new source system.
Regards
Anindya
Edited by: Anindya Bose on Oct 13, 2011 9:01 PM

Connecting multiple ECC Clients on same ECC system to BW system(s)

Hello.
We are considering connecting our Dev BW system to multiple clients on the same Dev ECC system. This connection would be for a limited time. We are wondering what the effect would be on the ECC system after we 'disconnect' our BW system from one of the clients.
Another thing we are considering is to create a seperate BW sandbox system and to connect that to a client on our Dev ECC system. The Dev ECC system will, at the same time, have a connection to a client on our existing Dev BW system. For example, having DEVBWcnlt100 -> DEVECCclnt100 and SNDBWclnt200 -> DEVECCclnt200 where DEVECC is a system and DEVBW and SNDBW are systems of their own. Our Sandbox BW system will have a limited life and at some point be taken down and no longer be a valid source system for the DEVECC system. We are concerned about what the impact would be to the DEV ECC system's client independent data once the Sandbox BW system is disconnected and taken down permenantly. Is 'residual' client independent data something we need to be concerned about? Is having two different BW systems connected to ECC clients on the same ECC systems a 'bad practice'? Any and all comments are welcome as we have not yet acted on our ideas yet.
Thanks very much for whatever comments you might provide,
Geoff.

We are considering connecting our Dev BW system to multiple clients on the same Dev ECC system. This connection would be for a limited time. We are wondering what the effect would be on the ECC system after we 'disconnect' our BW system from one of the clients.
No impact on the BW system. The only thing that you will have to take care of is that any process chains which fetch data from this DEV ECC system should not be put on periodic cycle because after disconnecting the ECC system, these would start failing.
Another thing we are considering is to create a seperate BW sandbox system and to connect that to a client on our Dev ECC system. The Dev ECC system will, at the same time, have a connection to a client on our existing Dev BW system. For example, having DEVBWcnlt100 -> DEVECCclnt100 and SNDBWclnt200 -> DEVECCclnt200 where DEVECC is a system and DEVBW and SNDBW are systems of their own. Our Sandbox BW system will have a limited life and at some point be taken down and no longer be a valid source system for the DEVECC system. We are concerned about what the impact would be to the DEV ECC system's client independent data once the Sandbox BW system is disconnected and taken down permenantly. Is 'residual' client independent data something we need to be concerned about?
Again no impact on ECC system. As for the client connected earlier to sandbox system, just clear all the queues in RSA7, LBWQ
Is having two different BW systems connected to ECC clients on the same ECC systems a 'bad practice'?
No its not at all a bad practice

Connect two BW systems to one source system

Hi Experts!
I would like to know if I can set up two BW systems connect to one source system. We copied and built new BW system (BW2) from existing BW system (BW1). We need to have both system connect to one source system. When I execut Restore from BW2 - RSA1 - Source System, I'm getting a following prompt:
"Connection cannot be used. The connection BB is used in the DEV400 source system as a connection BW1400 to BW. Do you want to delete this connection in source system".
If I select "Delete" then it replace exising connection between BW1 - DEV and creates new connection BW2 - DEV. If I go back to BW1 and do restore then same thing happens as BW2 connection removed.
Is there anyway we can set up two BW systems connection to one source system with restore? Connection works fine since each one can connection with no issues. Just when I do restore, it removes other connection.
Thanks.

Check if it helps:
Loading two different SAP BW system from one SAP R/3

No of Target systems to One source system via TDMS

Hello,
Wondering if any one in this group have worked on a scenario, where there is 1 source / ECC, and 5-6 target systems/clients.
The reason for asking this question : I have an RFC connection set between the source and target 1, and there is another RFC set from Source to Target 2.
Now, I have 4-5 projects created in TDMS/controller, and when I want to delete a project ( which is configured with source and target 1), I had to deactivate the package in the project, that inturn deactivated the RFC connections of Source and Target 1.
Now, when I am trying to create a landscape between source 1 to target 2, and when I clicked on the distribute RFC connections, it throws an error.
ERROR DETAILS:
Destination MBT_DD1_ED2_130_00_MBT deactivated or bad state - Connection check not allowed. Message no. CNVMBTRFC123 Diagnosis Connection check for a destination is not allowed. The reason can be that the destination is deactivated, no connection check explicitely choosen, or destination state doesn´t allow the check. Destination is deactivated In table cnvmbtdest in field deactivated you find the information about deactivation state. Keep in mind that for each remote system the state can be different for the destinations. Viewing deactiavation state see heading 'Get destination and deactivaten state'. No connection check explicitely choosen When calling the function for checking the connection we have an import parameter no_connection_check. If this parameter is set then no connection check will be done. Destination state doesn´t allow the check In table cnvmbtdeststate you find the state for a destination (also called connection state). If there is no entry then it can be assumed that the destination is OK. If there is an entry then all states with exception of O (connection OK) and the initial entry indicating that there is something not OK with the destination and no connection check will be done untill the issue is fixed. For destinations in the control system you find the destination state in the control system and for destinations in the remote system accordingly in these systems. Viewing destination state state see heading 'Get destination and deactivation state'.
Wondering if someone can help in fixing this. Thanks,

Thanks Anita,
Will go through the note and will revert back, incase of any further issues.
Also, I want to know why I am not able to delete a project, and when trying to delete a project, that doesn't have a package in it, gives an error. something that says, 500 sap internal error, screen output without connection to user ( termination : RABAX_STATE)
Also, based on my earlier msg, I was trying to go through the tcode " SET_RFC_STATE".
Surprisingly, I see all the Projects that I created with the earlier source/target/RFC connections.
Is there a way to get rid of these projects/ packages which are not in USE.
Thanks,

Two SNC system and one execution system

Hi Experts
Can there be possibilty of Two snc system to co exist with one execution system ECC?
IF yes can you folks please throw some light on the same?
This situation is arising because:
the Lime table in the existing system has really grown huge and the archiving is not helping becuase there are new records that are added to the system every day which are more than the archiving records
because of this huge data the upgrade is not possible and we are planning for a new setup, now to mitigate the risk we were tryin if two SNC system can coexist with one EEC system.
Now to add to the problem is there are certain business scenarios because of which we need to put in data in lime table every day
so reduction in data input is not possible.
As the data in LIME is only stock of the customer coming every day and if we just transaction data , even if we go away with all the data is not an issue with us as customer reports his existing stock on daily basis to us.
We have even thought of truncating all the tables available in in lime objects in SARA, we are thinking of this becuase system might act erratic when we setup new system and slow try moving few customer from existing to new system. as a pilot.
Supposing if we go ahead with it ,wht could be the issues ?
Thanks for all your help and suggestions
Regards
Manas Malhotra

Hi Manas
Two SNC systems can coexist together.
You need to define seperate Business System Groups,RFC settings,Logical System definition
Also you need to have seperate Identification for your master data, create your own definition in BADI
Example:If you are sending same material XXX to two SCM systems how to diferrentiate ???
Because BADi methods EXIT_/SAPAPO/SAPLCIF_LOC_001 & EXIT_/SAPAPO/SAPLCIF_PROD_001
differentiate when two ERP systems are connected to one SNC system by prefix and sufix, now you need to have your own code to differentiate
Also big time care should be taken in defining the distrubution models (bd64) and even in XI/PI like
Example: we have two TM systems coexisting with one ERP, so we used conditoned based mapping
Itu2019s a condition based mapping.
1) When TransportationRequestSUITERequest/TransportationRequest/ShipToLocation/InternalID = BP1 or BP2 or BP3 u2026 the receiver is I5YCLNT100
2) When TransportationRequestSUITERequest/TransportationRequest/ShipToLocation/InternalID = BP4 or BP5u2026the Receiver is I5XCLNT100.
Also care should be taken on master data/FICO settings which both systems use in common. like using Ztypes instead of using standard one like order type, message type. It should be easy when you troubleshoot back!!!
The inbound message parameters should be taken care w.r.t business needs
Good to have a matrix mapping like what business process coexit in both systems and which doesnot and then try to see what settings need to be tailored???
Best Regards
Vinod

Mulitple SAP Systems to one ADS system

Hi
It is possible to connect more tham one ERP system to a single ADS Instance?
Thanks

Not sure whether you are looking for /people/andreas.deutesfeld/blog/2009/04/27/ads-hub--central-installation-of-adobe-document-services

Multiple BW instances on one BO system

Hello experts,
The infrastructure setup of my project is to have 2 separate BW instances (testing and training) to be connected to the same BO system.
When setting up a BOJ connection (from Universe Designer), we need to specify the Application Server (ie. IP address of the BW instance). So it seems BOJ connection is BW instance-specific. However, we don't want to create separate sets of Connections (and hence, Universes & Queries) for each BW instance.
Is there any way for one Connection (and hence, Universe & Query) to be shared across 2 BW instances?
If this is not possible, is it possible to copy the Connection (plus Universe & Query) for BW instance #1 to a another Connection for BW instance #2? This is to simplify the effort of setting up BO for the second BW instance.
Thanks in advance for any suggestions.
Linda

Hi Ingo,
Thanks for the information. I too have same scenario to work out.
Is there any possibility of automatic Source/server name conversion from system A to System B while copying all the Universes and Queries.
For Example: In BI we have an option to datasource server name change convention while transporting from one system to another system through out the landscape.
As you said in your reply, in life cycle manager, do we need to edit connection for each & every universe or any option for one and all universes.
Any documentation on this is appreciable...
Please provide me information.
Thanks in Advance.
Regards,
Ravi Kanth

Error connecting multiple BW systems to one OLTP system

Similar Messages

Maybe you are looking for