One ECC Connected to multiple CRM systems

Hello,
We have a scenario where we have single R/3 system (ECC) connected to multiple CRM systems. I would be obliged if someone can send me some documentation on tht.
Also if we are creating an order in ECC, two queues are generated which I think is wrong. Can someone give me some advice on this.
Thanks & Regards
Priyanka

Hello Pratik,
I would define two different systems in ECC. In such a case, if say I create one material in R/3 (ECC) then should it generate two diffrent queues for flow to CRM.
Also if say the CRM Release etc for the two systems connected to one R/3 are not the same, then how do i take care of the entries in the ECC Config tables for replication i.e CRMFILTAB, CRMCONSUM, CRMPAROLTP etc.
And how does the ECC system identify what settings it has to take for what CRM system and what queues have to be generated? What are the queues to be registered in CRM and ECC in such a case.
Would be obliged if you can give me a more detailed advice.
Rgds
Priyanka

Similar Messages

Connecting One process Server to Multiple SAP Systems

Hi Experts,
We have a licensed version of the SAP CPS with the Process server limit parameter set to 4, which means we are limited to 4 process server as per my understanding. But when we create a SAP system the process server and the respective Queue is automatically created. SO that means we can create a max number of 4 SAP systems with 4 process servers!!
Or is there a way we can connect one process server with multiple SAP systems ?
Thanks,
Eric.

Yes - Process server limit parameter set to 4 means your CPS environment can start jobs in 4 SAP systems only.
Maybe "SAP Business Automation Enabler (BAE) Connectors" could be useful to you in your situation.
- Check the CPS admin guide for more information on BAE connector.
Regards,
David

Multiple CRM system with one R/3 system, possible?

Dear all,
I wanna see if multiple CRM systems can hook up to one R/3 system. My hunch is that this is not possible, because information exists in table such as R/3 CRMKUNNR for BP data would not be able to distinguish which system an entry would need to send to for syncing.
Am I right?
Thanks,
Kirby

Hi,
Well there is also the MDM (Master Data Management) application with SAP Netweaver. Which actually makes things a lot easier with a number of CRM installations with multiple R/3 instances.
Maybe you would also like to do some read up on MDM.
Thanks, Debasish

One Portal System connecting to Two CRM Systems

Hi All,
We have One Portal System EP 6.0 and we are trying to connect CRM 4.0 DEV and CRM quality.
i mean one portal system connecting tow CRM systems.
How the ivew connects two different CRM system.(dev and quality).
One way I am thinking that we have to maintain tow system alias ie SAP_CRM, SAP_CRM_QTY
and for the CRM quality, i have to change system alias all the iveiws.( becoz by default the system alias is SAP_CRM
1. Is there any other solution for this?
2. How to maintain the crm content for two different CRM systems.
Thanks
Ravi

Hi Ravi,
See if the following thread gives any help:
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=110980">https://www.sdn.sap.com/irj/sdn/thread?threadID=110980</a>
Bye
Ankur
Do reward points for helpful answers!!

Connecting multiple CRM systems to one backend R/3 and vice versa

Hello experts
Can you tell me whether it is advisable to connect 2 CRM systems to a single backend R/3 and vice versa? Is it recommended by SAP? I require some notes or docs on this. I got some notes on this forum but they are all Internal ones which I am unable to see.
Please help!
Warm Regards
Debolina

Hi,
Though SAP does not recommend connecting multiple systems to one ECC backend. But still it has designed a procedure to achieve this.
Here is the excerpts of the steps required.
1. Execute report MCRM_SETTINGS for each CRM system connected to the ERP
system.
2. Check the entries of the table CRMRFCPAR of the connected ERP system:
The field REM_LOGSYS should be filled for every entry marked with
u2018Created by the MCRM reportu2019.
3. Activate the corresponding consumers in the table CRMCONSUM
(transaction SM30).
4. Internal and external number ranges for Business Partners have to be aligned
manually.
Hope it helps you!!!!
Good Luck.
Pardeep

Multiple CRM systems to one R/3 system

Hi all,
Is it possible to connect Two CRM systems to the same R/3 system?
My gut feeling is, it is impossible to do that. Am I correct or is there a way to do it.
Any help will be highly appreciated...
Thanks
Jothi

Hi,
I it is very much possible to do this. SAP provides the functionality in the form of Multiple Backend Exchange feature. Please refer to SAP Note 853430 and also the link http://service.sap.com/crm-mep.
Also you can find a presentation in the link https://websmp107.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000579336&_SCENARIO=01100035870000000112&_OBJECT=011000358700002029062003E.
Hope this helps.
Regards,
Pradeep
MapBox Specialist

Can one R/3 system be connected to multiple BW systems?

Hi All,
Is it possible to connect one R/3 source system to multiple BW systems? If yes, is this setup any different from an R/3 to single BW system.
Points will be assigned.
Thanks,
Sirish.

Yes you can connect multiple BW to single R3 source system.
In the delta queue (RSA7 in source system), you have a field with the target system, so you don´t have problem if you have many target bw system, because the data selection is done by system field.
Challenge arises when you have multiple R3 feeding to single BW system and then you have to consolidate the master data say 0material fed from different source system R3 then you can consolidate data using consolidated infoobject.
The following components concatenate to the key of a consolidated InfoObject:
1)source system ID (two-character source system ID; permitted values are stored NW BI table RSSOURSYSTEM)
2)one blank character
3)backend object type (four-character backend object type; permitted values are stored BI table RSBWBEOTYP)
4)master data key value as stored in the source system
Note that the key of a consolidated InfoObject solely consists of non-integrated informations from the different source systems. Integration across source systems results from a (maybee repeatedly applied) data consolidation and cleasing process which unveils duplicate master data keys.
Hope it Helps
Chetan
@CP..

Can I use existing portal to connect to multiple R3 systems for config

I am planning to use existing portal 6.0 to connect to multiple R/3 systems for testing and configuration.
We have three portals in our landscape DEV TST and PRD.
Our R/3 system landscape -->DEV, DEV2, TST,TST2,TST3 etc.
DEV portal is connect to dev system TST portal to R/3 TST system etc.
Is there a way I can connect DEV portal to DEV2 R/3 System without effecting portal testing and configuration which is in progresses in DEV R/3 system.
If any one has done it in the past, please share instructions
Thanks,
adil

Hi Syed,
Check this link for creating systems.
Configuring EP for connecting to SAP R/3
http://help.sap.com/bp_epv260/EP_EN/documentation/EP/N03_BB_InstallGuide_EN_US.doc
Regards
Arun

How to connect to multiple backend systems to IMS

Hi,
I want to connect multiple backend system to SRM IMS.How to connect multiple backend system.
Thanks in advance
Regards
Nitin Amritkar

Hi
see page 63. it is possible.
define backend systems in spro and record all your ecc systems and create a distribution model fpr bbpiv message in srm and distibute to all backend systems.
http://www.portal.state.pa.us/portal/server.pt/gateway/PTARGS_0_160867_305341_0_0_18/2006_05_26_srm_007.pdf
br
muthu

One GRC connected to multiple R3

Hi
Needed you expert opinion
I am implementing GRC for a customer with 10 R3 systems
We have to implement one instance of GRC connected to 10 R3 systems
Each of these R3 belongs to a Business Unit ( 10 different business units in all)
Each of this business Unit is as good as a independent company have their own business and IT processes, roles and user. ( No user would have access in more than one R3 system)
Though many business process and risks would be common amongst the Business units. The risk owner would be different and so would be the mitigation process etc
In the above scenario I have following choices
Choice one - Use Logical system
This would have the least flexibility for the Business unit to manage their risks, actions and permission
Choice Two - Physical systems
Have a choice of common Risk ruleset and connect the 10 R3 systems as physical systems .
In this case the Risks would be common so would have issues related to risk owner, mitigation etc would remain. This would have limited flexibility. Also we may hit the 46000 rules limit
Choice three
Have 10 rulesets (10 sets of risks/functions etc, one each for the business unit)
Each business unit would have their individual risk and thereby greater control
I am inclined towards last choice. My concern is multiple rulesets/risks will lead to an greater number of rules thereby affecting performance
There would be around 6000 users and around 30000 roles in all these 10 systems put together
Can somebody share their experience/expertise on this
Regards

Hello,
I would suggest using the Logical system, and bundle all the 10 systems into One logical system, so you will have to create and maintain only one set of Rules, This will be very helpful in the long run, when you get into the prod support phase.
Coming to your question on using mitigating controls for this approach, You can have multiple monitors for one mitigating control (Please note that there will be only one Management Approver, I would assume it will be someone more at a central level for the entire business in your case). And on the third tab (Reports) in the mitigating control section, you can define a relationship between the systems and the concerned mitigating monitor. This way the mitigating monitor will recieve reports only for their particular system.
Note: This approach will only help if you have a common set of rules across the 10 systems.
Hope this helps.
- Naveen

Delta and Init Process when R/3 is connected to multiple BW systems

I have a scenarion where one R/3 system connected to 2 BW systems.
In R/3 we plan to have a LO extractor feeding delta to 2 BW systems. I understand delta works fine as delta queue in RSA7 is target system specific.
How are the initializations handled?
What happens if delta in one of the BW system breaks and we need to re-Init?
How would re-init from one BW system affect the delta/init in the other BW?

Hey. I'm assuming both BWs are pointing to the same system/client. I do not have actual experience doing this as I would be very hesitant to have multiple BW systems trying to get delta data from the same source (especially with how logistics behaves).
I know this isn't answering your true question, but could you connect BW system B to pulling the data from BW system A? So something like:
R/3 (logistics) => BW A 1st layer DSO
BW A 1st layer DSO => BW A reporting DSOs/Cubes
BW A 1st layer DSO => BW B reporting DSOs/Cubes
In this way, reporting in BW systems A and B are from the same DSO stage. This would help with any synch/data consistency issues. If A or B reporting providers get corrupted, or whatever, either could be reloaded from BW A 1st layer DSO and everything is still in synch.
Not sure if this helps you or not, but thought I would offer it up as this would probably be my approach.
Thanks

How to download ECC scale basis into CRM system?

Hi All,
Please share / suggest how to download ECC defined scale basis into CRM system (ECC to CRM)?
We used DNL_CUST_CND & DNL_CUST_CNDALL. Do we need to update any Tables in these Objects?
Thanks and Regards,
Fedor.

Hi,
you can create your own condition object(r3ac5), and in the new object > (tables/structures) tab change the condition table (A-)
please be noted that the table (KONW) which pass the scales, exist by defualt
u have to execute your object to replicate the data, and to be konwn your 2 objects which had run just for customzing not for data
feedback me if u have any Q.
الحمد لله الذي علمنا
samer shamandi

Multiple ESS's in one Portal connected to different backend systems?

Hi,
We have two backend systems installed.
We have one portal.
We want to create a second copy of the ESS Portal content connected to the the second backend.
Datawise this is not a problem.
But what about the JCo's and the Homepage Framework?
The WebDympro application seems to look for two specific JCo (for example SAP_R3_HumanResources and ...MetaData) and then both copies of ESS want to use this. Is it not possible to have each copy of ESS use it own JCo's and connect to its own backend system for the Homepage Frameworks?
Thanks,
Adriaan

Adriaan,
Its NOT possible to even talk to different clients in same backend system because you cannot duplicate the JCos and while creating them you need to specify the system and client details.
Also it uses a system alias which also has to be unique.
Per my knowledge one portal instance can talk to only backend client and to talk to another backend / client you will need to create a new instance within the Portal.
This [help|http://help.sap.com/saphelp_nw2004s/helpdata/en/82/76a2406546ba15e10000000a1550b0/frameset.htm] talks sometihng on multiple backend support. I am not much aware about it but see if it helps you.
Chintan

Multiple SRM Systems One SRM-MDM Catalog?

Hi
I'm currently upgrading our SRM 5.0 to SRM 7.01 with SRM-MDM Catalog 7.01. Is it possible to use one SRM-MDM Catalog in our non-production environment and connect multiple SRM systems to it?
For example our sandbox, development and QA SRM 7.01 systems would all connect to the same SRM-MDM Catalog 7.01.
Thanks.
Neil

Hi,
for non-production use and if it is just a catalog without custom coding running I see no problem in using one MDM server for multiple SRM systems (especially sharing one for sandboxes and dev). It is a setup I have seen multiple times and it worked always without problems.
You should set up different repositories for each SRM system so that you don't interfere with each others data (i.e. suppliers or other lookups tied to SRM).
You have to keep in mind that you have to upgrade all systems together. But you can always use separate MDM servers during the upgrade process and then consolidate onto one server when the upgrade is done.
If you are running custom coding with your MDM catalog I would recommend having a separate MDM system for the QA SRM in order to be closer to the production set-up when testing your custom solution.
Regards,
Martin

Steps to connect a CRM system with MDM

Hi everybody,
I've got a problem here : I should build a connection between a CRM system and MDM (get the data in several tables in the CRM system, normalize them in MDM and then put them back in the CRM).
What would the steps I've got to do to achieve that ? Do I need XI between the two systems ? Do I have to map the tables before sending them in MDM (and how could I do that ?)
Thank you for all the help you can give me
Seb

Hi
The Universal Worklist (UWL) iView is part of the KMC (Knowledge Management and Collaboration), capability of SAP NetWeaver. The integration of the SAP NetWeaver MDM workflow with UWL will be provided with SP04. This will provide the ability to expose SAP NetWeaver MDM workflow steps in the SAP Universal Work List (UWL). These jobs may run from the BPM process or can be launched inform within SAP NetWeaver MDM. UWL is defined as the main consolidated Inbox for SAP users, being the main location to monitor jobs directly activated in SAP NetWeaver MDM, or connected to a process that integrates with SAP NetWeaver MDM.
Using the SAP NetWeaver Portal UI, show a summarized list of all workflow (WF) jobs/tasks from all systems of SAP NetWeaver MDM Landscape per user - one single UI for all my tasks. The UWL is already integrated with other major SAP products, like R/3, SAP CRM, mySAP ERP, etc.
https://sapportal.wdf.sap.corp/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/infocenters/ws%20ptg/ptg/platform%20ecosystem/industry%20standards/projects%20and%20programs/business%20process%20management/index.html
First of all, you must set a RFC connectivity between CRM and backend system:
o     Create system users for remote connection (RFC_CONN). This user must have SAP_ALL authorization.
o     Create RFC connections in CRM system.
Go to transaction SM59 on CRM side and click on 'create' button. Set RFC destination name to the back-end system <sid>CLNT<client> (eg. R3DCLNT200), connection type to 3 (abap / R/3 connection) and fill the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
o     Create RFC connections in the back-end system.
Go to transaction SM59 on the back end and click on 'create' button. Set the RFC destination name to CRM system <sid>CLNT<client> (eg. CR1CLNT300), connection type to 3 (abap / R/3 connection) and fill in the target host to your back-end system. On the Logon/Security tab, add the RFC_CONN user created in the previous step. Save your settings.
o     Create a logical system name in CRM.
Go to transaction SPRO -> SAP Implementation Guide -> Customer Relationship Management -> CRMServer -> Technical Basic Settings -> ALE Settings -> Distribution -> Basic Settings -> Logical Systems -> Define Logical System Add a new value:
Save your settngs.
o     Create a logical system name in the back end.
Go to transaction SPRO -> SAP Customizing Implementation Guide -> SAP Web Application Server -> Application Ling Enabling -> Sending and Receiving Systems -> Logical Systems -> Define Logical System Add a new value:
Save your settngs.
2.
3.     Middleware parameters setup Go to transaction SM30 on backend system and choose table CRMCONSUM. Add the following values:
4.     Next, choose CRMSUBTAB for subscription table for the Up and Download Object and add the following values
User     ObjectName     U/D     Obj. Class     Function     Obj. Type     Funct. Name
CRM     empty     Download     Material     empty     empty     CRS_MATERIAL_EXTRACT
CRM     empty     Download     Material     empty     empty     CRS_CUSTOMIZING_EXTRACT
CRM     empty     Download     Material     empty     empty     CRS_SERVICE_EXTRACT
Next, choose CRMRFCPAR for definitions of RFC Connections and add the following values
User     ObjectName     Destination     Load Type     INFO     InQueue Flag     Send XML
CRM     *     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
CRM     *     SR1CLNT300     Request     SR1CLNT300     X     Send XML
CRM     MATERIAL     SR1CLNT300     Initial Download     SR1CLNT300     X     Send XML
Leave all other field empty.
Now, configure filtering for the material master:
Choose the CRMPAROLTP table for CRM OLTP Parameters and add the following values:
Parameter name     Param. Name 2     Param. Name 3     User     Param. Value     Param. Value 2
CRM_FILTERING_ACTIVE     MATERIAL     empty     CRM     X     empty
Now we must edit the table for the application indicator. Go to transaction SE16N on the back-end side and choose table TBE11. Search or add an application component BC-MID and edit activity settings (field AKTIV = X).
Save your settings.
8.     Enterprise buyer with/without CRM In this activity, you define whether you are running the Enterprise Buyer and CRM in the same system. This might accelerate the Master Data download performance. If you are using CRM in the client, then skip this activity.
In the CRM system run transaction BBP_PRODUCT_SETTINGS, deselect 'Test mode' and choose the Execute button.
The system generates a report containing all tables that have been deactivated.
9.     Generate repository objects With this procedure, you generate the middleware function modules (BDoc Object Type) for the material master.
Go to transaction SMOGGEN and choose object PRODUCT_MAT and PRODUCT_SRV. Generate services for all object categories.
Please let me know your email id, i shall send you this document
Regarsd
Rehman
Reward Points if Useful

One ECC Connected to multiple CRM systems

Similar Messages

Maybe you are looking for