Creating Source systems in two same logical BW systems from single R/3 sys

Hi All,
We are facing an issue while creating Source systems in two same logical BW systems, from single R/3 systems. Our Basis team is telling that if we want to connect the single R/3 system into 2 BW systems with same logical name, we will need to delete the source systems from one BW systems and create in another system. Also they told by doing so it will delete all the transfer rules and PSA table existing in the current BW system, which has the source system connectivity with the R3 system now.
Is this anyway to create the same source systems in two same logical BW systems, from single R/3 systems without deleting the transfer rules?. Also please help us to get anu OSS note or document explaining this in details.
Regards.
Muruganand.K

Hi Muruganand,
I dont think it is possible as connecting one R/3 Source System to two BW Systems.
If you could get the possible solution, please do reply to the post.
Regards,
Kiran

Similar Messages

Unable to open templates from server input form folder and server root folder from some system while the same can be open from others system

Hi,
I am unable to open input scheduled from server root folder and also from input form folder on some system while they can be open from others system.
Please advice.
Thanks in advance

Hi Hengye,
While opening , it dont give any error. When I try to open it , it takes some time to load then nothing happen.However I can open it on other system but not on mine my collegue and user system.
Please advice.
Thanks.

Same logical systems for two environments productive

Hi gurus.
I have a question for ALE
There are two production systems a copy of another, who want to connect both to configure the ALE, but by mistake, both systems were the same logical system when they made the copy. Since this change takes months. At the moment I can not make this change in BDLS because it is a productive environment.
When trying to configure the ALE, I am have problems with the logical system name, although one of the settings I gave it another name when you configure the transaction BD64.
Guys, what I find solution to configure the ALE, without changing the logical system to a productive environments ??????
Regards,
Desiré

Hi Mark, thanks for the replay.
I understand also that the solution is to execute the BDLS to change the logical system and convert all tables to new logical system.
I don´t know how the process copy for both system productive.
The problem is that both environments are connected to BW, and other applications and they opened an OSS note to SAP consulting and and the answer given is that they did not recommend changing the logical system.
I thought if there was another way to configure ALE without having the problem of changing the logical system environments.
Regards,
Desiré

How to connect one ECC 6.0 system to two BW ssytems.

Hello all,
I am trying to connect one ECC 6.0 systems to two different BW systems. The BW systems have two different logic names.
I tried to find an answer in the threads , but could not able to find the steps. they were talking about the notes which fixes for the deltas. but I am not even able to connect the systems at all to implement that notes.
Please give me the steps how to connect to an another BW2 system. The connection between ECC and BW1 ia working fine.
Thanks,

The error message is .
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system LOGTST100 does not accept any of the proposed values.
The last proposed value was BB.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely BB, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.

Getting two same workitems in PO release workflow for 2 level

Hi experts,
I am working in PO Release workflow upto two level of release.
But while triggring my workflow by creating PO I get two same workitem.One of the two has correct Release Code(I have checked that in workflow log) and another has Release Code with no value.If I execute one of them Its working fine.But 2nd one still remains in inbox.I think my workflow has been triggred twice while I am creating a PO.
Can someone suggest, where is the problem?
Thanks,
Manas

Hi,
According to your instruction I have got 5 event trace.
BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
QCYBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
BUS2011     QUOTATIONCREATED     14.02.2008     16:31:57          @AI@     No receiver entered
BUS2012     RELEASESTEPCREATED     14.02.2008     16:31:57     WS99900003     @5B@     SWW_WI_CREATE_VIA_EVENT_IBF
FREBUS2012     CREATED     14.02.2008     16:31:57          @AI@     No receiver entered
I have given you the details of the event traces.
Here I notice RELEASESTEPCREATED event occurs twice.
Can you please suggest why this is happening?
Thanks,
Manas.

Unable to create two SourceSystem with same Logical System

Dear gurus,
The customer has expressed the need to connect a data source with the same Logical System name of the actual DS.
Infact, on the SCC4 the R3 Prod/qua/dev has the same LOGSYS.
The aim is to link the PROD/R3 system to the QUA/BW system.
During the creation of the DS on RSA1, an error message display that BW cannot create the Source because the Logical system is already in use.
All we know that on BI can not be two identical technical name, but if i CANNOT change the LogicalSystem on the SCC4, there is a workaround?
Can i map the new sourcesystem with another LOGSYS name?
Or the only solution is to change the logical?
Thanks in advance
C.C

Hi Sven and thanks for the reply.
unfortunately the customer chose to appoint the entire landscape with the same logical system name (policy), so that i cannot make this change on SCC4.
So, i have to link only one SourceSystem (or quality or prod)...but at least, i will make a refresh copy of the quality system
ps: i'm a Basis

XI testing for two SAP R/3 systems with same system id/logical system

Hi
We are currently in the process of upgrading our R/3 4.7 to ECC 6.0 and plan to maintain dual landscape for DEV & QA (4.7 & ECC 6.0) for a period for testing and maintaining existing applications for fixes etc. The second DEV & QA (upgraded to ECC 6.0) are copy of respective systems and these systems are created automatically under technical systems in SLD by auto update (RZ70).
The question is, can we use the same XI system for testing inbound/outbound interfaces for both the systems i.e 4.7 & ECC 6.0 at the same time. I am aware of the fact that XI Technical/Business sytems dependent on unique logical systems, so we cannot create new business system for the upgraded DEV-II ECC 6.0 system.
For your information, we have two slds (one for XID/XIQ and second one for XIP).
What are the options without disturbing & maintaining the current XI system set up?
1) Can we change current Business systems e.g DEV010 to use new technical system i.e DEV-II ECC 6.0 for testing for a period and switch it back to DEV-I 4.7 technical system?
2) or change logitical system name of DEV-II ECC 6.0 and create new business sytem in SLD without interfering the existing setup and modify/create interfaces to use this new business system?
3) Do we need to refresh cache from time to time in XI ?
4) Any other implications
We will be upgrading XI to PI 7.1 after ECC 6. 0 Upgrade.
Any views on this would be highly appreciated.
Regards
Chandu

Hi
Technical System was created in the SLD automatically after RZ70 configuration in the new DEV-II system. We then modified Business System to use the new Technical system and carried out following steps:
1)     Original Idoc metadata was deleted from XID
2)     The port definition was deleted
3)     A new port definition was created for new system
4)     The metadata for each idoc type used was re-created in IDX2 , using METADATA -> CREATE
5)     This brought in all known versions of the idoc segments, including the 7.1 version.
I have already checked the guides suggested for our upgrade and we are thinking of going ahead with fresh installation and migrating the interfaces.
Regards
Chandu

Filter on the same logical table source on two logical tables is not working properly

Hi,
In the RPD, assume that I have a physical table named Employee_fact, created an Alias called D0 Employee Fact
In the BMM I've two logical tables called Employee_fact_Type1 and Employee_fact_Type2
Each of these logical tables has the same Logical table source - D0 Employee
But in each logical table source, I've a filter in where clause
such as, for Employee_fact_Type1 employee_type = 'XXX'
for Employee_fact_Type2 employee_type='YYY'
These two facts are present in the same BMM and each of them are connected to two dimensions
such as
Dept_type1 <- Employee_fact_type_1 -> Tenure_type1
Dept_type2 <- Employee_fact_type_2 -> Tenure_type2
In analysis, When I query the columns from Dept_type1 and Tenure_type1, the database query generated shows the condition employee_type='YYY' instead of employee_type='XXX' .
But, adding the columns from Dept_Type1, Employee_fact_type_1, Tenure_type1 it shows proper filter.
I checked the relationships, presentation layer for the sources of presentation tables and everything looks good.
Can anybody tell me what goes wrong here?

did you set the content level as well?

Same logical system name for two productive systems - BW, PI issues

Dear all,
we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
However as far as I know:
- we cannot connect systems with same logical system name to BW,PI
- we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
How can we overcome the problem?
Please advice.

> However as far as I know:
> - we cannot connect systems with same logical system name to BW,PI
> - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
Right.
> How can we overcome the problem?
Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
Markus

Two R3 servers have the same logical system name?

Can two R3 servers have the same logical system name present in the same network? We plan to clone our production server and let the clone reside in the same network. The clone is identical with the production server with the same SID, hostname, logical system name, but different IP address.

Hi
Check this [Link|http://help.sap.com/saphelp_nw70/helpdata/EN/da/5990df015b5b43a36f6ce7fa1ee8c0/content.htm]will cleare you doubt
Regards
Uday

Can there be more than one port for the same logical system

Can we have more than one TRFC port for tranferring data from one logical system to another?
The requirement is to transfer same basic idoc type from one logical system to another through two different ports. Is it possible?
For eg. some specific data (country specific) for the same basic idoc type can be sent through a separate port and the other data through a different port inorder to distinguish between the two.

Hi Shital,
I don't think so. Because of that what i told you. There would be a dirty trick (back routing) to solve your issue. But its quite difficult and not standard. You create two http receiver services and two http sender services. You route your message depending on payload to the one or the other http receiver channel. The receiver is in both cases: THE XI! Now you have a second message, which you can route to IDoc adapter. But in this case you have different sender and in the receiver determination you can put the sender, so you will be able to use different communication channnels and so different ports / destinations.
Advantage: Your task would run, no performance problem (http: very good, asynchron)
Handicap: You see every message double in the monitoring, the scenario is not easy to understand and it is a big task 4 other people to change it.
Regards,
Udo

Error while creating SOURCE SYSTEM

Hi All,
I have a problem while creating Source System to a Solman syatem configured with BW content. I have configured few some source systems already in the same Solman System.The system shows the following error, previous to this i get the message a "generating connection to the source system"
Error in source system RXX_100
Message no. RSAR502
Diagnosis
With Remote Function Call to system RXX_100 error Screen output without connection to user. ccurred.
Procedure
Remove the cause of the error.
Kindly provide me suggestions and DOCS related to the same.
Suitable points will be awarded for replies.
Expecting your kind reply,
Vineeth

Hi ,
In SCC4 the source client should not set as production when creating the source system connection between two systems.Please check below SAP note
973555 - System must be open for creating/connecting source systems
Thanks,
Shanaka

Same Logical System Name, different Business System

Hi all,
I have a problem regarding SLD and Integration Directory. The client is requiring me to use the same logical system name for two different business systems. It seems that this is not possible in XI. When I tried activating the business system in ID, I'm getting the error, 'Logical system XXX already exists in communication component YYY'. Please help. Thanks!
IX

Hi,
You cannot have same logical name for two business systems....
Why you need it?? How will the SAP system understand which which system the message was sent for?? Some workaround like
1. Create a business system with this logical system
2. Overwrite sender/receiver business system in the receiver agreement for messages sent to 2nd business system..
This may lead to discrepancies....
Regards
Suraj

SLD: Pointing two business systems to the same client...

Hi Guys,
Is there anyway to make two business systems point to the same client(on the same r/3 technical system)? how about a work around?
Thanks,
Harsh

Harsh,
>>Finally all collapse to one client in production.
Even though you will have multiple Business Systems in every envrionment, the final transport will happen from only one environment.
DEV --> QA --> PROD. In this case, objects are moved from dev to qa and then from QA to prod and so, all you will need is the trasnport target created in the QA business systems pointing to the Prod busines system and do the transport.
>While transporting to a new SLD(quality to prod) can I choose one transport target for multiple source business systems?
Take a look at this document for multiple SLD transports. Should answer all doubts,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
Regards,
Bhavesh

Create source system in BW3.5

Hi all
can anybody tell me the procedure for creating source system in BW3.5 using automatic method at this time i create and assign logical system in both BW and R3 system and create Background users in BW system now my confusions are
1 Is this nessory that i create a diffrent user which is not dialog user in BW or R3 and
2 Thing is this nessorry that no pre created RFC connection present in R3
thx

hi,
i m listing down the steps with brief description, check if you r going that way.
1.you have same background user in BW and R/3 with proper autho.
2.you created new source system in RSA13, selecting first option of automatic creation.
3.you fill in all details correctly in popup window "Create R/3 Source System", that comes up.
4.pressing ok, it will ask you to log in as admin in target system. Before loggin in check client no, it may be diff e.g. 000, then change it to yr system client no.
5.next it will give you RFC destinations screen. goto tab "Logon/Security", give password for the user thr. save the changes.
6.you can check the connection by clicking "Test Connection" and try also "Remote Logon". If your password is correct, then it will log you in the system.
7.now everything is setup, so comeback. It will ask you to replicate/activate datasources from the source sytem. Click "Replicate as Well".
pls mark question answered, if you have no further doubts
Now it is finished.
Hope it helps.
Regards,
Purvang

Creating Source systems in two same logical BW systems from single R/3 sys

Similar Messages

Maybe you are looking for