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

Similar Messages

Object Creation Of One class into another and vice versa

Hello Everyone,
My name is Prashant Sharma from Jaipur [Rajasthan]
Can u people help me
How to create of one class into another and vice versa
Eg,
I am having class A and class B
I want to create object of class A into class B and vice versa
Plz help me out of this problem as soon as possible....

Read this: [Creating Objects|http://java.sun.com/docs/books/tutorial/java/javaOO/objectcreation.html]
Then, do one of these three:
1. Create an instance of the class
2. Extend the class
3. Access methods within the class
Try it out. Post the problem code if you're having trouble.

What are the best ways (for best performance) in MII to process the incoming process messages from shop floor systems to SAP ECC 6.0 and vice versa?

Hi All,
Can you please suggest to choose the best ways (for best performance) in MII (12.2 on NW 7.3), to process the incoming process messages from shop floor systems to SAP ECC 6.0 and vice versa?
Thanks

Hi Surya,
Best practices for flow of data from ECC --> SAP MII --> Shop floor & Vice verse:
1. Send ECC data through IDOC's/RFC's as messages to SAP MII message listener and BSL transaction process data and update directly on shop floor database as if you configured in Data services or later send those data by web service to shop floor system (i.e. depends on Shop floor machines).
From Shop floor:
shop floor --> SAP MII --> ECC
1. Use either Web service or fetch data from DB and pass data to BAPI's for sending to ECC through BLS transaction.
Regards,
Praveen Reddy

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

Possible to connect multiple R3/Systems to one XI?

Hi,
is it possible to connect mutiple R3-Systems to one XI?
How does it work?
Regards
Stefan

Stefan,
You can certainly connect multiple R/3 systems to one XI.
1. If your R/3 system release is 4.7 then use point 8 from the configuration guide. (RZ70 transaction collects the system data and creates a technical system in the SLD)
2. If your R/3 system release is < 4.7 (means 46c or 46B, 40B) then you should create a technical system in the SLD.
3. For any other SAP product with ABAP stack (including R/3 47 system), you should check the SAP_BASIS release if it is 6.20 you should apply XI Add-on to use XI Proxy adapter. For SAP_BASIS < 620 you cannot have XI Proxy adapter. For SAP_BASIS > 6.20 you do not need any add-ons (from this point onwards it is NetWeaver)
To find SAP_BASIS release -> SPAM Transaction -> Click on Package Level.
Then create a business systems for each one of them and import them into the Int. Directory when needed.
Regards
Shravan

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

How to connect an non-hana-ewm with an Hana-ECC and vice versa

Hello,
for our migration project planning I am wondering how to connect EWM on SAP with ECC on Hana and vice versa.
As it is, both systems are (productive) on non - hana with actual SAP-Release and have to be migrated.
The background of my question: we may be not able do the "big bang" thing to migrate ERP ECC607 and EWM (with special Add-Ons) at one point to Hana (DMO) and therefore may need an interim solution. I checked ETL and LTS as "connectors" but they - from my point of view - are one-way solutions from EWM to ECC/Hana -not bidirectional.I Found some questions concerning the same theme in the net but no solution at all till now..
How about BODS ? (Didnt work with it yet)
Best regards,
Ronald

Great. So I have to either install OS X, or buy a new mcahine. Can OS X run on a G3 without grinding to a halt?
By the way, I cannot get the iPod to even mount when connected via firewire. The USB/firewire PCMCIA card does not have drivers for OS 9. I thought that this support was built into OS 9. The USB port works (although the iPod will not mount when connected via USB either). Any ideas?
Thanks

Connecting two SCL systems to one backend

Hi,
Is it possible to maintain 2 SCL system connections to one ECC system? We have already connected one SCL system to ECC as a backend and now we want to connect second one. Is it possible to do that?
If yes how to maintain Logical Ports call parameters for that?
Thanks
Domas

Hi Domas,
As pointed our by Holger, this is supported for inbound flows where your use case is to read (pull) some information from SAP into SharePoint. But use cases like reporting and workflow which publishes some items in SharePoint you cannot have the same ECC system.
But if you intention is only for DEV landscape setup and want to save a VM image and still want to support reporting & WF scenarios, then you could also create a new client which is the copy of your existing clients in the same ECC system.
Since logical port configurations are client specific you could practically connect same ECC system (but 2 diff clients) to 2 gateway systems.
Thanks,
Girimurugan

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

MFP Anomaly Detected Access Points are moving from one wlc to another and vice versa

Hi together,
a customer has lost some Access Points to another WLC with 7.2 and then they come back after 15 minutes to the origin WLC with 7.5
Attached the messages
MFP Protection is configured as optional
152
Wed Nov 27 05:33:26 2013
MFP Anomaly Detected - 1 Not encrypted event(s) found as   violated by the radio 58:bf:ea:0f:67:4a and detected by the dot11 interface   at slot 1 of AP 58:bf:ea:0f:67:40 in 300 seconds when observing . Client's   last source mac 70:11:24:e4:43:0f
153
Wed Nov 27 05:31:40 2013
AP Disassociated. Base Radio MAC:88:43:e1:56:91:d0
154
Wed Nov 27 05:31:40 2013
AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:88:43:e1:56:91:d0 Cause=New Discovery Status:NA
155
Wed Nov 27 05:31:33 2013
AP Disassociated. Base Radio MAC:58:bf:ea:0f:73:d0
156
Wed Nov 27 05:31:33 2013
AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
157
Wed Nov 27 05:31:33 2013
AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:73:d0 Cause=New Discovery Status:NA
158
Wed Nov 27 05:31:28 2013
AP Disassociated. Base Radio MAC:58:bf:ea:0f:fc:20
159
Wed Nov 27 05:31:28 2013
AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
160
Wed Nov 27 05:31:28 2013
AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:58:bf:ea:0f:fc:20 Cause=New Discovery Status:NA
161
Wed Nov 27 05:31:17 2013
AP Disassociated. Base Radio MAC:b4:e9:b0:e4:02:20
162
Wed Nov 27 05:31:17 2013
AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
163
Wed Nov 27 05:31:17 2013
AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:b4:e9:b0:e4:02:20 Cause=New Discovery Status:NA
164
Wed Nov 27 05:31:15 2013
AP Disassociated. Base Radio MAC:a4:18:75:eb:da:b0
165
Wed Nov 27 05:31:15 2013
AP's Interface:1(802.11a) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
166
Wed Nov 27 05:31:15 2013
AP's Interface:0(802.11b) Operation State Down: Base Radio   MAC:a4:18:75:eb:da:b0 Cause=New Discovery Status:NA
167
Wed Nov 27 05:28:26 2013
MFP Anomaly Detected - 35 Not encrypted event(s) found as   violated by the radio d8:24:bd:2f:df:6f and detected by the dot11 interface   at slot 1 of AP d8:24:bd:2f:df:60 in 300 seconds when observing Deauth.   Client's last source mac 00:23:14:a7:e3:54
168
Wed Nov 27 05:23:26 2013
MFP Anomaly Detected - 23 Not encrypted event(s) found as   violated by the radio f8:4f:57:a5:40:b2 and detected by the dot11 interface   at slot 0 of AP f8:4f:57:a5:40:b0 in 300 seconds when observing . Client's   last source mac 44:4c:0c:ba:27:77
Don´t know at the moment how to handle it.
Regards
Alex

Hi lAlex,
Disable Client MFP under WLAN advanced tab & see if this still occur
Regards
Rasika
**** Pls rate all useful responses *****

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

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

When we connect two bw systems to one R/3 system?

Hi ,
When we connect two bw systems to one R/3 system,
could you please exlain what is the imact to SAP and BW in terms of query performance, batch performance,Develoment ,Quality system,security,BW Support.
Thanks in advance.
Regards,
kranthi

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..

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.

Multiple SAP Systems In One MSCS Cluster

We have installed a NW 7.0 EHP abap stack in a MSCS Cluster with 2 nodes.
This was installed as a standard Cluster Install.
We have now higlighted a requirement to install a 2nd (Java ) instance in this Cluster Group.
The NW 7.0 EHP1 documentation and Note 1321854 shows that multiple SAP systems in one MSCS cluster is supported.
The documentation, however, is not clear if the 2nd instance can be installed when the 1st instance was installed without the preperations for Multiple Systems.
There are no further documentation or guidelines to help.
Has anyone come across this situation or managed to install 2 SAP instances in one Cluster Group based on Windows 2003, SQL Server 2005.
Regards

I am not quite sure if I understood your problem completley. But let's see...
Usually you use on on MSCS Cluster Group per SAP instance. So you have your already existing NW 7.0 ABAP stack in a separated Cluster Group, and you create a new Cluster Group for your new Java system.
You can find more information about it in this guide here on SDN:
Link: [High Availability;
More information about High Availability Setups for SAP System can be found here on SDN:
Link: [High Availability]
If you want to use the same database for your clustered ABAP stack and your new Java stack you can do a MCOD installation.
Please see Link: [SAP Note 388866 - Multiple Components on One Database - Installation|https://service.sap.com/sap/support/notes/388866]
Hope this helps.
Best regards,
Mathias

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

Similar Messages

Maybe you are looking for