Multiple Exchange Projects (MEP) Multiple Backend System

Hi,
How can you replicate products in SAP CRM from several R/3 back end systems and avoid double entries?
What is the appropriate process ? How do you do that in the middleware ?
Thanks for your help

Hi Nilanjan
Wish you a very happy new year.
I need to get it clarifed with the team whether they have aborted in between the Full Optimization process. Becuase i remember in one of the earlier engagement , we have aborted the modify application application and it cretaed multipple cubes at the back and subsequently SAP has suggested to delete the other cubes keeping the correct one.Can you elucidate the relevance of the _B Virtual Info provider from the rationale perspective, why its required them.
I shall update you on the same.
Thanks
Krish

Similar Messages

Creation of multiple connectors if we have backend systems with multiple

Hi All,
If I have 5 backend systems with 2 clients each.
Do I need to create UWL connector for each client.
Regards
Suneel

Hi,
You have to create a connector for each system alias. So if you have a backend with 2 clients and you want to retrieve work items from both clients you will have to create 2 systems (and 2 aliases) and 2 UWL connectors.
Regards,
Pierre

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

Find exact RFC Destination for Multiple backend Systems In SAP Gateway

Hi Gateway developers,
I have requirement,if gateway hub system has multiple backend systems( for example two backend systems: ECC and SRM ) then how hub system can get the suitable backend alias for exact entity collection..
Here i have developed two entities one entity regards: ECC and second one regards SRM system..within this when I run the service it is always taking any of the same alias for both the collections..
Can you please suggest me..
Thanks
Sreenivas Pachva

Hi Srinivas,
You can add the respective system Alias Name: Like logical system name in your URI also.
Example:
/sap/Service Name;mo=ECCCLNT210/zentity1?Customer1='0001'
/sap/Service Name;mo=SRMCLNT400/zentity2?Customer2='ABCD'
May this help you.
Thanks,
Saurabh Gupta

Unable to define connector for multiple backend systems in BRM

Hi,
I am on GRCFND_A V.11 and SP04
I have multiple backend systems integrated with GRC box. So far I was using one backend connector as default one for role maintenance but it is not feasible if you have to create roles in variuos backend connected systems. I know one way to do so, i can keep changing the default connectors whenever i need to create roles but that is obviously not at all the onw any one would like to go with.
So, I tried to create unique connector groups for every individul backend connectors. But the issue is, the moment i assign the backend connector to the respective connector groups, the same gets reflected to other connector groups as well. So, whenever i either add or delete some of the connectors to any connector groups it gets modified/changed from all of the connector groups.
These are the backend connectors where i have to create roles from BRM whenever needed.
These are the connector groups:
I followed to the ink: GRC AC 10 BRM: Default Connectors with Multiple Back-end R/3 Systems , which is the same as mine issue, but not able to come to the solution point.
would appreciate for your quick response.
Thanks,
Ameet

Could anyone suggest solution to the above mentioned issue please?

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

Programmatic access to multiple backend systems using adaptive RFC

Hello,
The following link http://help.sap.com/saphelp_nw04/helpdata/en/af/84a34098022a54e10000000a1550b0/content.htm talks about the support to map multiple backend systems by specifying the backend system as URL parameters in a webdynpro application.
For example:
http://<hostname>:<port>/webdynpro/dispatcher/local/ESSProject/ESSApp?
sap.wdarfc.useSys=WD_MODELDATA_DEST:ABC&
sap.wdarfc.useSys=WD_RFC_METADATA_DEST:ABC
Is it possible to programmatically change the backend systems the application connects to? in other words can a single application while executing connect to different backend systems by dynamically changing the model parameters?
(This should be possible without the portal in the picture)
Cheers,
Praveen

Hi,
[This|JCO connection to multiple R/3 Back end system; might help especially the reply from Bertram Ganz.
Regards,
Satyajit.

WD Exception when pointing ESS Travel & Expense to multiple backend systems

Hi All,
I have a query regarding ESS Travel Management pointing to multiple backend systems.
ESS MSS is installed on a single portal(Portal1).
ESS MSS is currently pointing to Backend System1. The requirement is that ESS Travel from Portal1 should point to various multiple Backend Systems therefore making ESS Travel region-specific.
Is this possible? and if so what are the pros and cons?
This is what I have attempted:
1. Followed the documentation from "Multiple Back End Support for the Adaptive RFC Model" [http://help.sap.com/saphelp_nw70/helpdata/en/af/84a34098022a54e10000000a1550b0/frameset.htm]
Therefore, I created 2 JCOs namely: SAP_R3_Travel_R1 and SAP_R3_Travel_MetaData_R1 pointing to Backend Sytem 2. SSO and JCO tests successfully.
2. On the iview properties for ESS Travel & Expenses, I added the following to the Application Parameters: sap-wd-arfc-useSys=SAP_R3_Travel:_R1&sap-wd-arfc-useSys=SAP_R3_Travel_MetaData:_R1
3. I additionally created a system in the Portal under System Configuration pointing to Backend System2 and adding the SAP_R3_Travel_R1 as the default System Alias. Do I need to add SAP_ITS_XSS and SAP_WebDynpro_XSS system alias, if so how since it is seeing as redundant because it is added in the system I created for Backend System1.
4. I then tested one of the ESS Travel & Expenses iviews. I have the following error:
Accessing System XYZ is not possible because RFC Metadata was retrieved using System ABC. Please assure you have configured the RFC Connections properly. A Server restart may be necessary!
Your help is appreciated.
Thanks.
RD

Hi,
Can you please share the solution you got for this problem as we are also facing the same kind of problem.
thanks
Gaurav

JCo Scenario with multiple Backend Systems

Hello @ all,
Is it possible to use multiple Jco destinations to multiple Backendsystems in one WD application?
The scenario is as following: I want to call different function modules on different SAP Backend systems?

Hi Mehmet
Alternatively you could try switching the destination through URL parameters
http://<Host-Name>:<Port-Nummer>/webdynpro/dispatcher/local/Example_Project/Example?sap-wd-arfc-useSys= WD_MODELDATA_DEST:SyB&sap-wd-arfc-useSys=WD_RFC_METADATA_DEST:
SyB
Check this link (I havent tried it though)
http://help.sap.com/saphelp_nw04/helpdata/en/f4/651741f163f023e10000000a155106/frameset.htm
Regards
Pran

Multiple backend systems for business package ESS/MSS

Hi,
I would like to know whether there is a smart solution for connecting the business package ESS/MSS with multiple backend systems (up to 10 systems).
I am aware of the possibility using parameter "sap-wd-arfc-useSys", but this implies, that content needs to be duplicated n-times in order to be able to maintain the Jco destination suffix.
Any hint, also for custom built solutions are very welcome!
Best regards,
Johannes

Johannes
There is some problem with the link
See this.
Connecting multiple SAP Systems
Thread name is 'Connecting multiple SAP Systems'
Krishna Murthy

UoM issue due to multiple backend systems

Hi All,
We have multiple backend systems hooked up with the SRM system. One issue that we have is that many of the UoMs are different in the backend systems. For example, for THOUSANDS, we have TH and THO in different systems. As part of optimization we intend to include only 1 entry per UoM in SRM box.
The problem is if we put TH as the unit, then if it is chosen by a user linked to the backend system that does not have this Commercial unit, then the Shopping Cart fails when trying to create a follow-on document.
Any advice how we can get this resolved will be greatly appreciated.
Best Regards
Gaurav

Hi Gaurav,
Common problem when using multiple back-ends, which can be resolved rather easily. The best way to solve this is by a business change. That isu2026. synchronize the use of the UoMu2019s throughout the organization. This would be the most elegant solution. All back-ends will then have the same valueu2019s in their respective CUNI tables.
Off course the feasibility of this will depend on your organizational structure and the hitting the u2018right stringsu2019 in order to get every one to understand the importance of this.
As a back-up an other solution would be to create a Z-table which will translate the UoM used in the SRM system to the corresponding UoM in the respective back-endsu2026.. The table will have three columns. u2018SRM UoMu2019 u2013 u2018Back-end Systemu2019 u2013 Back-end UoM. Depending on the implementation scenario U use, you can have the interface to the back-end carry out the translation. For this you can use the available Badiu2019s: BBP_CREATE_BE_PO_NEW, BBP_CREATE_BE_RQ_NEW, BBP_CREATE_BE_RS_NEW
Downside of this solution will be the extra maintenance effort for the Z-table. Best choice in my perspective would be the business change.
Kind Regards,
Skander

CRM Middleware/MEP multiple R3 backends with different customizing

We have hooked up our CRM7.0 system to two R/3 backends both with differeng customizing data. I can successfully perform for example a DNL_CUST_SHIP from either one. The problem I have is that it overwites the data from the other system. I need to know if there is a way to pull in the customizing from both systems and then only have to manually maintain those entries where there is a clashing key.
Regards
Marc

Hi,
I read that these projects (MEP) customer must implement with SAP.
Because which projects is very hard for implementation
and specify of business processes what you want to implement.
I try to implement this process. I think so:
1. Business objects must have different numbers.
2. Customizing object must have same values.
Denis.

Working on projects on multiple systems

Hi, I have Final Cut Pro X installed on my iMac and I have a lot of projects and events on an external hard drive. I also installed FCPX on my macbook pro because I need to do some editing at one client's location. If I have my external hard drive plugged in my macbook pro and launch FCPX, I can see all my events but I can't see the project. If I close FCPX and browse my external hard drive to the "Final Cut Events" folder, I open any of the projects folder and double click on the file "CurrentVersion.fcpevent", it opens FCPX but I still can't see the projects.
Anyone can help me ?

Originally posted by: kim_horne.ca.ibm.com
You need to investigate working sets. These will allows you to group
your projects as you suggest. Try searching the help system for
"working set".
rich boakes wrote:
> Working with Eclipse on large systems where there are multiple plugin
> projects seems harder than it should be.
>
> The large number of projects visible in the hierarchical explorer views
> make it difficult to focus on the two or three projects which are under
> development at any one time.
>
> Is there something I've missed which might enable me to create project
> groups, or is it possible to have the source to multiple plugins in a
> single project?
>
> Cheers
> Rich

Multiple backend systems in ESS CATS Webdynpro scenario - challenge

Hello Everyone!
For one of our customers we have the following challenging situation with the ESS CATS Webdynpro scenario:
System Landscape:
ERP 6.0 HR Backend System
ERP 6.0 FI/CO Backend System
EP 7.0 with already running ESS scenarions
Our customer actually uses the ESS CATS Scenario for collecting wage types into infotyp 2010. Now, additionally, they want to
use ESS CATS for an internal cost allocation scenario. This means, that the data from the CATS Webdynpro have to be redirected to the FI/CO backend system instead of the HR system (because of a missing standard ALE scenario for this case). The JCO SAP_R3_HumanResources points to the HR-System. Is there a way to dynamically redirect the system assignment depending of the used CATS scenario. Out of the CATS Profile we can conclude which system should be assigned. I red a lot about dynamic system resolution in the SAP Library, but it seems not to be the right solution for this issue - because I need to know the CATS profile for the descision.
Any hints would be great. Thanks in advance!
Cheers,
Harald

Rob Christopher
First of all, I introduce myself: it’s Oscar Garcia de las Heras, from Madrid, Spain.
I can check in SCN and Linkedin your high expertise in ALE, ESS and SAP.
We have a delicate situation in my current project; I would like to ask your help.
The situation is this: we have different machines in HR and FI, and are trying to implement Travel Management through the SAP Standard Portal.
TM settings is in the FI machine, but ESS calls to the HR machine.
We have 2 ideas:
-A, differentiate the different services of the Portal, so specific HR processes will call to a HR machine and others will call to a FI machine.
-B, set the ALE processes to duplicate HR information in FI, and Portal will call just FI machine.
We prefer first idea; would you recommend us?
Thanks a lot for your time

Syndication of merged records to multiple backend systems (MDM 7.1)

Hi all,
I have setup an MDM scenario with >1 ECC systems connected to MDM via PI. Everything works fine in terms of end-to-end process from ECC to MDM or MDM to ECC (creation, update, syndication). I have also merged records in MDM from the same backend system and am able to see the remote key information under 'edit key mappings' and when I update the merged records in mdm the data is olso updated in ECC.
BUT the update in ECC does not work for merged records where the keys are from different backend systems.
Example:
Remote system: RS1 and RS2
I have merged two records, one from RS1 and the other from RS2. The newly created record has two key mappings (RS1/RS2). Also the newly created record shows - let's say - RS1 in MDM and the the RS2 informaion is attached as remote system information. When modifying the record in MDM, only RS1 is updated but not RS2.
Remote Systems RS1 and RS2 are set up in the Cosole. Also I have setup a port for each remote system. Syndication in general works perfectly without any problem. I know that I have to trigger syndication for each port but still does not work. Any ideas?
Thanks!!!
BR,
Erdal
P.S. I am using MDM 7.1

Hi Erdal,
OK, I assumed a setup like this.
> in 5.5 there was "Output Remote Systems" whereas in 7.1 we don't have
You have this one in 7.1, too. "Output Remote Systems" was renamed to "Remote Key Override". I don't know why, but the functionality is exactly the same.
> "Supress Unchange Records" is checked
This explains the behaviour that you are facing. "Supress Unchanged Records" is used to distribute only these records that have been changed. What happens inside MDM is the following.
MDM Server creates kind of a change pointer for the changed record AND for each remote system that record belongs to:
Imagine you have a record A with a key for RS1 and RS2 each. You change this record. MDS creates two change pointers A-RS1 and A-RS2.
Now you switch to Syndicator and distribute the records with the port for RS1, but with "Remote Key Override" for both RS1 and RS2. Syndicator creates a single message and includes both the remote keys for RS1 and RS2. Furthermore it deletes BOTH change pointers A-RS1 and A-RS2 as the record was distributed for BOTH systems!
If you then connect with Syndicator to the port for RS2 and start the syndication, Syndicator cannot find any change pointers and thus won't create a message.
If you want to send the golden record to different systems, I'd suggest to add each system to MDM Console. Create a syndication map & port FOR EACH system. Within the map use the target system only as "Remote Key Override". Use "Supress Records without key" to exclude those records, that do not have a remote key for the target system. Use "Supress unchanged records" if you want to distribute only the changed records.
If you need a message having all keys of all systems (e.g. to update a BI system with grouping information), create a specific remote system for this purpose. Create a map & port, the map shall now use the "Remote Key Override" for all systems. The "Supress" settings can be made as above, but especially for BI we're recommending to syndicate always all records (do not "Supress unchanged records").
Best regards
Michael

Multiple Exchange Projects (MEP) Multiple Backend System

Similar Messages

Maybe you are looking for