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,

Similar Messages

  • 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

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

  • '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

  • 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

  • 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

  • One PI for multiple ECC systems

    Hi PI experts,
    We have one PI instance per environment, but multiple ECC instances, so taking Dev we currently have a BAU ECC and a project ECC, although there are occasionally conflicting needs this is generally manageable.  However a new project has introduced the need for two further ECC instances per environment, all requiring the same interfaces.  We will still only have one PI.  All of the interfaces receive files coming into the same folder structure. 
    Has anyone else experienced this scenario?  How was it best to manage the competing projects trying to use one PI instance?
    Thanks very much in advance
    R_Macd

    Hi R_Macd,
    You need to register the ABAP Systems in SLD, use the transaction RZ70 to do this, please check the refer links:
    http://help.sap.com/saphelp_nwpi71/helpdata/en/7c/1966ab384d42a78deaebc74d33c032/frameset.htm
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=213353417
    After that, create the business systems with the client do you need to connect.
    http://help.sap.com/saphelp_nwpi71/helpdata/en/ae/e3bd4f6b61e146ad1384954ecabb41/frameset.htm
    Best Regards,
    .Luis Bernal.

  • Multiple HANA systems connection for Smart Business Fiori Apps

    Hi Experts,
    I could configure and run standard Fiori apps through launchpad and able to configure all type of Fiori apps through web dispature and single HANA system1 [retail]
    As per the recommendation from SAP, we have separate HANA system2 for finance.
    Now here is the tricky part.
    I have added HANA system2 in web dispature. Also I have the trusted connection in my front end gateway server for transactional apps.
    Transactional apps from HANA system2 db is working fine. Now, I would like to configure Finance related Analytical apps from HANA system2 views. For this I am not able to get KPI IDs for evaluation and drill-down configuration.
    The path for Smart Business KPI modeler in both the HANA systems are same. Is this causing issue to bring KPI IDs and HANA views into modeler?
    How to get both views in single KPI modeler tool to configure the KPI tiles?
    Please let me know how to proceed?
    Thanks!
    Praveen.

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

  • MDM's Source ECC System Splitting into Two

    We are running MDM 5.5 and have a single source ECC system, PR1_400, that serves two divisions (Europe and North America).  Our company is going to create a separate ECC system for the European division and leave PR1_400 for NA.
    The problem is that all of the data in MDM has key mappings to PR1_400 and the European items will need to become tied to XYZ_400.  Has anyone experienced such a change and have recommendations?
    Thank you.

    Hi Keith
    If you haven't installed syndication server - install it
    You haven't configured remote systems and inbound/outbound ports in your repository
    1) stop repository
    2) create two remote systems (EU and AF for example)
    3) create inbound/outbound ports for remote systems
    4) set "key mapping" parameters in main table to "Yes"
    5) load repository
    6) Syndicate or save form Data Manager all data to files
    7) Create import maps in Import manager for all source files( and save its in repository
    8) stop repository
    9) go to inbound/outbound ports and select early saved map files for automatically load data
    10) start repository
    11) put source file to inbound directories
    12) start syndication server
    13) wait when import process was done
    14) load data manager (you see triple records from EU from AF and with empty "edit key mappings" properties)
    15) select matching mode and turn matching rules for key fields
    16) run matching process
    17) merge tree to one record
    18) after that one result record had tree remote systems in "edit key mappings" propeties
    manually
    do step 1-10 if it need
    11) stay ro record and load "edit key mappings" propeties
    12) push add button select remote system
    13) push OK
    14) dublicate records
    15) do step 12-13 only select another remote system
    16) do that steps 11-15 for all records
    17) do steps 15-18 but with two identical records
    finish
    Regards
    Kanstantsin

  • 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

  • BI Source System connection to ECC

    Hi experts,
    I have a BI 7.0 fresh install and I'm trying to connect ECC 6.0 client dev100 (golden client) to BI so I can activate BI Content. However, the client 100 goes to the BI folder instead of the SAP folder when I create source system in AWB. Is this normal behavior?
    I have another system client dev200 and it goes inside SAP folder when I create source system. I'm just wondering if this has something to do will my error in BI Content activation. Key figures and characteristics are activated but not DataSources, Update rules, and InfoPackage.
    Your comments are greatly appreciated. Thank you

    Hi JD,
    I think the source system connection must have been made in Bi folder. basically even BI folder shall contain BI system but if ECC system connection is made in this folder it shall not make any diffrence. You must be getting the datasources as of ECC only after replication.
    Regards,
    Wrushali
    Request for points deleted. Please do not ask for points in the forum.
    Edited by: Vikram Srivastava on Jun 22, 2010 1:56 PM

  • SCM question -2 SCM system connected to single R/3 system

    Hi Gurus,
    What is the implication using two SCM systems with single R/3 system when both SCM systems using for different modules (say one for DP and other one for GATP).
    I know SAP recommends using multiple OLTP with single SCM. But this scenario opposit of that.
    Thanks,
    BKN
    Edited by: BKN on May 6, 2008 7:08 PM

    It is possible that there can be multiple SRM system connected to 1 R/3 system...You need to setup on...IMG>SRM->SRM Server->Technical Basic Settings>Define Backend System-> There you need to provide Logical System/Description/RFC Distination and Sys Type.
    I hope it clarifies your issue.

  • 2  Srm Systems connected to 1 R/3 system is it possible

    Hi friends,
    I was looking into a situation where you would have 2 SRM systems pointing to 1 backend R/3 system. I<b> dont believe its possible.</b>
    I believe you can have 1 SRM pointing to multiple backend systems, this is do-able.....
    cheers
    alex

    It is possible that there can be multiple SRM system connected to 1 R/3 system...You need to setup on...IMG>SRM->SRM Server->Technical Basic Settings>Define Backend System-> There you need to provide Logical System/Description/RFC Distination and Sys Type.
    I hope it clarifies your issue.

  • 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

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

Maybe you are looking for

  • OWA 2010 send/reply window does not close on IE10/11

    Hi, We've been experiencing issues with OWA on Exchange 2010 for several of our users after rolling out Internet Explorer 11, and this was also an issue with IE10. The issue occurs when a user tries to reply (does not happen when sending out a new ma

  • How to upload a  logo in smartforms

    can anybody tell me how to upload logo in Smartorms

  • JMS Message Bridge with MQ, only BytesMessage available ?

    I have successfully set up bridging between MQ and JMS, and have an MDB that receives messages via the bridge when a message producer puts messages on the MQ-queue. Ideally, I would like to receive MapMessages and not BytesMessages which seems to be

  • BurnNow software for X201

    Hi all complete lenovo newbie here. I need to create an clone image for a Lenovo X201 using the site license version of Windows 7 belonging to my employers. Unfortunately this means doing a windows install from scratch. Everything was going great unt

  • Increase the line size in ABAP Editor

    Hai experts, I write  ABAP code  one  line upto 73 charcters only in ABAP editor, how to increase the line size in ABAP editor. please its urgent. thanks and regards sitaram