Multiple JCO to different ECC systems

Dear Portal Gurus,
We have this need where in we need to point the BP for ESS to point to 2 ECC 6.0 env i.e. DEV and QA ECC.
For the same how do we create JCOs to point to 2 different ECC from the same Portal server.
We are at EP 7 SPS10.
Thanks,
Ashish

Hi ashish,
We can create multiple Jco connections(there is no problem in that).
But if the number of connections are increased then you need to create a connection pool.
see the below link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/1fe23d44d48e5be10000000a114084/frameset.htm
Regards,
Bala

Similar Messages

Cross reference data from 2 different ecc system.

Hi Sdners,
Iam working on a scenario where i have to get data from two different Ecc system,consolidate them and send it back to their respective system.
But some refernce data in both the systems are different and when iam merging data from 2 system i have to maintain either of the reference data.But problem comes when i syndicate it back to ECC ,it cannot accept a new reference data.
Please suggest me some answere how to proceed in such case.
Its urgent.
Points will be rewarded for Genuine answeres.
Thanks in advance,
Regards,
Neethu.

Hi,
First enable keymapping property to YES for the table which you want to do
importing and syndicatig.
Create two remote systems type inbound/outbound .
Import the data from first remote system and map the corresponding fields.
Don't forget to map the remotekey field which is on the destination side.Make clone
of one of the dispaly field and map to the remote key field.
After importing you can see the records from which remote system are imported
using Edit Key Mappings option in DataManager.It shows that remotesystem
name and corresponding remote key.
Do the same for second remote system too.
After merging data in data manager , you can see the merged record and see the
two remote systems names and two remote keys by using Edit Key Mappings
option so the merged record goes back to both remote systems when you syndicate
the records.
Syndicate the data from first remote system by selecting destination properties and
output remote system property under map properties tab as your first remote
system.
Do the mapping for corresponding fields and don't forget to map the value field under
remote key .Then MDM generates remote keys for only records belongs to your
first remote system.You can see this in destination preview.It does n't genarate
remote keys for second remote system.Then check the option Suppress records
without key under map properties tab and execute the syndication.Finally we can
see the accurate records.
Do the same for second remote system too.
Hope it helps
Cheers
Narendra

Same material number Ciffing from different ECC system

Hello Gurus,
I have APO system connected with two ECC system.
If there is a material with the same name in both the system how does the APO system finds the respective system.
Even if I assign BSG for the logical systems, to which system will the transaction data will be transferred after planning?
Thanks,
Siva.

Although I do not have real-time experience working in this kind of scenario from what I understand there will be two product-codes based on the BSG.
Eg. HAMMER@BSG1 will be the Product code for material HAMMER coming from your first ECC system which is mapped to BSG1 and HAMMER@BSG2 will be the product code for material HAMMER comping from the other second ECC system that is mapped to BSG2.
Transaction data will then flow back from APO to respective ECC system based on the BSG mapping. Note in the Distribution Definition you maintain the connected ECC logical system name as well.
Hope this helps.
Thanks,
Somnath

Joining multiple views from different HANA systems

Hi
We are on Business suite on HANA environment ;that means ECC , CRM , BW on different HANA DB / instances.
For reporting ; i would like to combine calculation / analytical views from these different systems.
Any thoughts on approach?
Thanks in advance

If you are looking at something like HANA Live from multiple systems then check following
How to Realize Cross System Reporting Using SAP HANA Live Content
But if you are really looking at multiple HANA systems and remote connectivity options then may be links below helps out. There are bunch of articles on Cross-System reporting/SDA so may be you can do some research.
I have not tried this so can't give real hands-on feedback
SAP NetWeaver BW on SAP HANA & SAP HANA Smart Data Access
Smart Data Access: Connecting multiple SAP HANA... | SAP HANA

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

XI and PI connecting to the same ECC system

I had read this thread XI and PI
Currently, our ECC is connecting to XI. In Integration Engine config of ECC, role of business system is "Application System". In XI, role is "Integration Server". If we need to add a PI and connect to ECC, what should be done or what is the workaround that can make XI and PI connecting to ECC at the same time?
Thanks.

Hi Mark,
Thanks for the suggested blog, I need some time to study this. I do not understand why 'standard' integration server is defined as 'Application System'.
I also need to study the limitation of SPROXY on SAP application server refer to only one XI/PI system. May be the issue of my scenario is not just connecting multiple XI/PI to ECC system.
The scenario:
Maximo MEA 6.2 <-> XI 3.0 <--> ECC (current)
Maximo MEA 7.5 <--> PI 7.x <--> ECC (to be added)
Any input or experience sharing? Thanks.
Regards,
Donald

2 ECC systems with 1 APO system

Hi All,
We have the same data in 2 ECC clients linked up to an APO box. We had to do that to test the new data load and the project did not invest in a new APO box.
We plan to keep all in one Business System Group as we want the same product, location numbers etc in APO. Using separate BSGs and CIF exits to modify product numbers etc is not an option as it will impact all BI reports etc..
I would like to know if it is possible to have such an architecture. If yes, how does the APO system send back the information to ECCs, how does it know where to send, if both ECC systems are specified in publications.
Regards,
Zeeshan.

my basis is very basic but - have you looked at partitioning into separate clients? i suppose you can connect two different ECC systems to two different clients in APO
if you dont want locations to be changed it will turn to be a little difficult i think. if you did not have that issue you could prefix the location based on the ecc system. there are some posts in this forum on that

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

MDM to Multiple ECC System connection using PI

Hello experts,
My scenarios is to Send Customer and vendor records from MDM system to multiple system. In First release we are sending data to two SAP ECC systems. So we are using File to IDoc.
Please help in the right architecture design as source is same but target are different and couple of field value in IDOC depends on target system. So do I need to do two complete scenarios - Separate Mapping, sender agreement, receiver determinations, interface determinations, communication channels etc or I can re-use some parts. If so how shall I approach with 1 source file to two target files with different values.
Thanks!
Regards,
Ahmed

So we are using File to IDoc.
Please help in the right architecture design as source is same but target are different
and couple of field value in IDOC depends on target system. So do I need to do two complete
scenarios -
Separate Mapping, sender agreement, receiver determinations, interface determinations, communication channels etc or I can re-use some parts.
If so how shall I approach with 1 source file to two target files with different values.
if two target structure are different
esr:
one source service interface(a)
two target service interfaces (b,c)
2 operation mappings(ab),(ac)and 2 message mappings (ab),(ac)
id:
in receiver determination , you have to define 2 receivers and sending data by using xpath condition.
need to create 2 receivers communication channels
need to create 2 Receiver agreemnets(because we need to use 2 target service interfaces for different structures)
need to create 1 interface determination.
thanks,

Consideration during Multiple ECC systems with One APO system for PP/DS

Hi All,
We have a scneario that Multiple ECC systems and Third party ERP systems and Legacy systems .What are the points to be considered for this scenario when using with PP/DS?

Hi,
The factors to be considered will greatly depend how the multiple ERP systems are split, if they are split on geographical aspects only (all modules in all ERP systems then no major issues) - the problem will become a little challenging when Multiple ERP are split with different modules in different instances then major thought has to go in your CIF design (the IMs has to properly though of ).
It is not a detailed explanation but just the line of thought.
Regards,
Vineet

Possibility of connecting multiple BW systems to single ECC system

Hi all,
I have a requirement in my company to connect multiple BW systems to single ECC system. Would like to confirm whether this may not be supported by all BW extractors in particular the delta mechanism?
For logistics extractor in ECC side in RSA7 it stores BW System as target which shows they support multiple BW systems as target, but for FI extractors which keeps delta timestamps in BWOM2_TIMEST table, it doesn't store the target system. I'm afraid if we connect multiple BW systems to single ECC system, some of the delta records might go to one BW system and some others go to the other BW system when we execute delta load in both BW systems.
Thank you very much in advance.
regards,
arie

Hi,
You can very well connect multiple BW systems to single ECC system and you will not miss any delta as well. In the source system for each delta data source a delta queue is maintained for each target system.
for e.g. I have two BW systems ABW and BBW connected to AEC system then for 0FI_AP_4 data source we will have DQ1_ABW and DQ2_BBW as two different delta queues (I am not following any naming conventions, actual names will be as per the target system logical name).
The settings maintained in BWOM2_TIMEST table are across the system and they define some global settings e.g. till what time the FI data should be extracted in BW system, for e.g. the time maintained is 2.00 AM then though you do extraction from multiple systems same data will be extracted till next time interval occurs.
In summery you can very well connect multiple BW systems to a single ECC system.
Regards,
Durgesh.

BW system connecting to multiple ECC systems

Hi,
I am new to BW world & has a question to Gurus
1. Can I connecte a single BW system to source from multiple ECC systems (activley) with out any technical issues ? I am assuming that the multiple ECC systems are pretty much mirror images.
2. If possible what are the areas ( at a high level) I need to double check to make this happen ?
Thanks
Hari

Hi Hari,
Yes, you can connect multiple ECC systems to one BI system in one of my project we had more than 20 ECC systems connected to BI Production system.
How this works is because source system and BI system has got different provisions for that,
1) For connecting different systems you simply need to create RFC connection between them. After the RFC is formed you can load data from any of the systems.
How BI system differentiate similar data coming from these systems?
There is a field called 0SOURCE SYSTEM which is used as Compounding field, or primary key field where ever you have data loading from multiple systems, this field basically contains the 3 char source system ID and is used to differentiate records coming from different source system.
How delta is managed in this scenario?
In source system for each data source, a new delta queue is maintained for each target system.
Regards,
Durgesh.

Creation of sales order in CRM and replicating it to Multiple ECC system.

We have a requirement for creation of sales order in CRM and replicating it to Multiple ECC system.
We have checked the following standard Adapter objects in transaction R3AC1.
BUS_TRANS_MSG
The initial flow contexts does not support target site type as R/3(SMOF_ ERPSITE). So we are not able to replicate the sales order from CRM
to ECC.
2. SALESDOCUMENT
Here the initial flow contexts does not support flow from CRM -> R/3 as we don’t see the target site as CRM.
Please let us know if the standard sap middleware objects don’t support the sales order flow from CRM to multiple ECC or is there any
other adapter object we need to use for this.

Hey Vijay Duvvada,
I hope you are already referred below sap note and which explains scope & how to do -
1084315 - Consulting: Information about the multiple backend scenario
1763516 - How-to: Basic Setup of MEP
As explained by Rohit Sharma data should be start flowing to multiple sites.
please let me know if it does help.
Regards,
Arjun

'SPROXY' - Multiple PI Systems connected to one ECC System for ABAP Proxies

Dear Experts
I am currently facing an issue when I want to connected multiple PI instances to one ECC client for
ABAP Proxy purposes.
In transaction 'SPROXY', in the Enterprise Service Brower, only one PI instance is shown and accessable.
Can this setting be changed to allow multiple PI systems in this Enterprise Service Browser?
Thanks for your ideas.
Mathias

Hi,
Check these replies.
R/3 connected to multiple XI instances
'SPROXY' - Multiple PI Systems connected to one ECC System for ABAP Proxies
Multiple XI Instances
Multiple XI instances or multiple app server
Thanks,
Vijaya.
Edited by: Vijaya Lakshmi Palla on Jun 4, 2008 11:43 AM

ECC connecting to two different PI systems for proxy

Hi All,
We currently have a PI 7.1 system to which many client proxies are configured in the SAP ECC system.
Now that we have installed a new PI 7.3 system we would like to make all new integrations in PI 7.3. Note that the ECC system would remain the same.
(The idea is to migrate interfaces from PI 7.1 to PI 7.3 in a future date)
In the same ECC system we need to configure client proxies to the newly installed PI 7.3.
In SXMB_ADM we can only define one integration server for ECC system. Hence if we want to configure proxy to another PI system, we need to overwrite it.
Since our current ECC system is 6.0, the workaround given by SAP through transaction SAOMANAGER for ECC 7.0 systemsdoes not apply.
Kindly mention the alternative solutions/approaches available to configure ECC proxies to two separate PI systems.
Thanks,
John

Hi John
Have you checked this blog?
Connect SAP Application System to multiple SAP PI Integration Server - Variant n°1
Regards,
Giuseppe

Multiple JCO to different ECC systems

Similar Messages

Maybe you are looking for