Assign records to different remote systems in MDM

Hello Experts,
I am using qualified range to generate internal number range for vendor. The remote key & remote system details for the records are generated during syndication. My scenario is that I have couple of records in MDM for different remote systems. I want to syndicate it to the respective systems. Is there a way to identify the respective records per system with out inserting the details in "edit key mapping".
If we try specifying Remote system details in edit key mappings with a blank or specific Key value , then the qulaified number generated for vendors is overwritten with this key value mentioned in key mapping.
I need to retain both the qualified range functionality as well as tag the records to different remote systems.
Kindly advice.
Thanks and Regards,
Elizabeth.

Hi Shiv
So, i am not sure, but this all makes me feel that syndication tasks can not be executed parallel.
Your understanding here is correct since we are using here the same table for syndication process so it will be executed in steps. I mean syndication 2 has to wait until the syndication 1 ends. But the thing is that even after syndication 1 completes syndication 2 is not going to place that's the issue here.
Please find solution which tells same thing in MDM import manager context.
Can I run two Import Managers at the same time?
Yes, several instances of the Import Manager can be open concurrently. The only existing limitation though is when actual importing process starts the tables involved in the importing process are locked for write access. So if two instances of the Import Manager import to different tables then no synchronization issue occurs. If they use the same table, then the instance getting access second has to wait until the first ends.
For more details, Please refer this below link:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7dc6ba86-0501-0010-0b82-849437929f0d?quicklink=index&overridelayout=true
@ Elizabeth: After Syndication 1, Have you checked after sometime whether syndication2 & so-on takes place or not. I feel that Syndication for syndication 2 , syndication 3 & syndication 4 should also occur after some time as they executed one by one not parallel so will take some time. Just check and revert with result whether your workflow gets completed after some time or not.
Note: Make sure that for all these Syndications outbound ports Processing Type = Manual in Console else syndication will not occur.
Regards,
Mandeep Saini

Similar Messages

MDM 7.1 remote key generation on different Remote Systems

I am checking onthe remote key gerneration.
1. When I import data from a remotesystem lets say A AND the data have e.g.. a vendor number in Vendors from BusinessContent
    the remote keys are generated for this remote system.
2. Whe I want to syndicate these date to another remote system e.g. SAP ERP, the objectid i.e. LIFNR is NOT shown in
   the syndicators Destination Preview.
   independent of the map properties setting "Remote Key Override"
3. When I enter the key by hand inthe data manager the data are shown in the syndicator but only it "Remote key overrifde"is
   set to the target system.
Question:
It looks like that the remote keys for a different remotesystem other than the one I omported from are NOT set.
How to do a automatical assignment to the keys of this different Remote System

I checked:
SAP ERP Remote System range 100000 999999
A range 100000 199999
Key Mappings defined for SAP ERP Remote System (checked in Data Manager)
key Mappings not defined for A (checked in Data Manager)
Everything I do I do in the Syndicator
With mapping property "Remote Key Override" marekd as "Reset" no LIFNR is written to SAP ERP
With this property set to SAP ERP the LIFNR is sent.
When I use System A it doesn't matter which settings I have there is no VendorNumber sent out.
Looks like I miss the settings for a property?

Unable to Edit/Remove Remote Systems using MDM 7.1

Unable to find an answer to this in either the forums or the Wiki...
Using MDM 7.1 through the SAP MDM Console 7.1.03.54
I can add a new Remote System, it comes up with the default values for the Remote System fields:
Name: New Remote System, Code: NewRemoteSystem, Type: Inbound, Key Generation: None
But I cannot modify the field values nor can I delete the Remote System.
The right-click context menu always has 'Delete Remote System' greyed out.
Nor do I see any mechanism to modify the fields' values. Moving to the Remote System Detail pane, none of the fields are edittable; I have tried left-clicking, right-clicking, double clicking, using the Edit tool bar menu - nothing lets me edit these fields.
My user account has the Admin role. Looking to the Admin role, it has Execute for all functions, and Read-Write to the Remote Systems in the Tables and Fields tab.
Any help would be appreciated.

Hi Andrew,
Your repository should be in unloaded state to make changes in any table whether main table, subtable, Ports, Special tables or Remote Systems table etc. As you want to make changes in your repository Remote Systems, please unload your repository->Go to Admin>Remote systems>Make necessary changes (Add/Delete/update)--> Then load repository.
Note: You can only add User and Roles during Repository loaded state.
Regards,
Mandeep Saini

Remote System and Remote Key Mapping at a glance

Hi,
I want to discuss the concept of Remote System and Remote Key Mapping.
Remote System is a logical system which is defined in MDM Console for a MDM Repository.
We can define key mapping enabled at each table level.
The key mapping is used to distinguish records at Data Manager after running the Data Import.
Now 1 record can have 1 remote system with two different keys but two different records cannot have same remote system with same remote key. So, Remote key is an unique identifier for record for any remote system for each individual records.
Now whenever we import data from a Remote System, the remote system and remote key are mapped for each individual records. Usually all records have different remote keys.
Now, when syndicating back the record with default remote key is updated in the remote system that is sent by xml file format.
If same record is updated two times from a same remote system, the remote key will be different and the record which is latest contains highest remote key.
Now, I have to look at Data Syndication and Remote key.
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back. But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
Regards
Kaushik Banerjee

You are right Kaushik,
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back.
Yes, but if they are duplicate, they needs to be merged.
But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
This is after merging. So whichever remote key has tick mark in key mapping option(default) , it will be syndicated back.
Pls refer to these links for better understanding.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/80eb6ea5-2a2f-2b10-f68e-bf735a45705f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c%0c
Hope this helps,
+ An

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

Syndication Search Using Remote System

Is there a way to use the Key Mapping's remote system as part of the search criteria for syndication?
I am not referring to the map property that allows you to suppress records that do not have a remote key.
For example, only send records when "remote system = DEV_100".
Thanks,
Keith

Hi,
When you create a map you have already defined the remote system for which is getting created and you have mapped key and name of that in the syndicator mapping.Suppose you craeted a map fro remote system DEV04
Now when you only want to syndicate the records for this remote system then you should define only this as a output remote systems and then if you have supressed records without key,then only records pertaining to the DEV04 system which have key will get syndicated and not others
Thanks
Vinay

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

Search for records by Remote Key or Remote System in Data Manager

Hi all,
We have a requirement to search for records by Remote key and/or Remote System at the main table level. Is it possible to do this using the Data Manager? If so, how?
Thanks in advance!
Lavanya.

Hi,
I crosschecked with MDM 5.5 and Don't think it is possible through Data Manager. How ever using APIs you can search records using remote key/ remote system.
Regards,
Shiv

Connecting MDM to Remote System

Hello,
I was brought on-site to an MDM assignment that is connected to an SAP 4.7 system. The client is now upgrading to ECC 6.0 and I am going to be in charge of pointing the MDM system from 4.7 to 6.0.
I am not sure where to start or where to look to figure out how to create a new connection to a remote system. I have looked in the Console Ref. Guide, the MDM Master Guide, and a few other places.
Can anyone help me with what needs to be done and perhaps where there is documentation to walk me through this?
Thanks experts!
Nichole
Edited by: Nichole Smith on Jul 26, 2010 5:52 PM

HI Nichole
the remote system defined in MDM is only the logical system and ports are defined pertaining to the remote system defined. This has in turn no dependencies on related landscape.
So no changes required at MDM side. (If you can continue with the existing system name for ECC).
If not change the remote system name in MDM first with the correct logical name.
In the PI system landscape and also ECC we need to define the logical systems matching/pointing to MDM defined remote systems.
You can refer to below thread for step by step guidnace for establishing interface between MDM and ECC
MDM-ECC Integration
hope this helps-Ravi

Central Autoreaction method won't assign to remote system

When I assign a remote autoreaction method to my CRM systems in rz21 it won't show in method alloctaion. I get no errors. It shows the assignment as being created but when I got to rz20 and display the node and do a - view - method allocation the autoreaction method is not assigned. When I look at properties for the method it takes me to the remote system but again doesn't show the autoreaction method assignment. I checked that the systems are online in rz21 display remote systems.
My ecc systems are working just fine.
Any ideas?
Thanks,
Dan

Hi Dan,
Try checking in RZ21 that any agents for the satellite system are online as they should be.
In RZ20 SAP CCMS Technical Expert Monitors - Selfmoniring CCMS Agents, the same agents should also show as 100% Available. There may also be errors in the agent log (sapccm4x.log).
These SAP notes are also worth a look:
429265 - CCMS monitor architecture: Central auto-reaction
939616 - CCMS auto-reactions: Help with troubleshooting
Regards,
Brendan

Search for [Remote Key] and [Remote System] in Data Manager

Hello all
I would like to be able to search on the remote key and the remote system in the MDM Data Manager is that not possible? I thought I remembered seeing that possibility under the Free-Form Search but now I can't find it.
I have, however, found this in the Data Manager reference guide:
REMOTE SYSTEM AND REMOTE KEY FIELDS
MDM uses the remote systems defined in the Remote Systems table
within the MDM Console to store and maintain key mapping information
for each record or text attribute. It does this using a virtual key
mapping field that you never see in the MDM Client.
This virtual key mapping field is very much like a qualified lookup field
into a virtual key mapping qualified lookup table.
Key Mapping information stored in virtual lookup field
The Remote System and Remote Key fields are normally not visible;
however, they do appear in several places in the MDM Client.
Specifically, both fields: (1) appear in the File > Export dialogs in Record
mode for exporting value pairs; (2) are recognized by the File > Import
dialog in Record mode for importing value pairs; and (3) appear in the
Edit Key Mappings dialogs in both Record mode and Taxonomy mode,
for viewing and editing value pairs.
Is there any way to search on the value in the remote key from the Data Manager?

Not sure search i think not possible.
But you can see keys as mentioned:
Enable Key mapping in Console.
MDM Client maens MDM Data Manager.
They do appear in several places in the MDM Client or Data Manager. Three different methods to see in DM are given already below:
Specifically, both fields: (1) appear in the File > Export dialogs in Record mode for exporting value pairs; (2) are recognized by the File > Import dialog in Record mode for importing value pairs; and (3) appear in the Edit Key Mappings dialogs in both Record mode and Taxonomy mode, for viewing and editing value pairs.
BR,
Alok

Key generation in Remote Systems.

Hi,
When we are creating a remote Sytem we have a filed called Key Generation , where we can specify the from , to Range.
Can any one provide me the business scenario where this key generation is used?
I have an idea about key mapping which is used to differentiate filed values which are different in connected remote systems.
regards,
Venki.

Hi Venki,
The key generation is a very useful concept.
For Key Generation = Range, From=100, To= 200:
You need to map the Remote key to MDM_Material field during syndication in which you want to maintain the value.
So the first time you syndicate data, 100 will be assigned to the MDM_Material field for the syndicated record.. so on..
It gets updated to your field only after syndication and you can see it on edit key mapping against the record.
For Key Generation with Qualified range:
You need to select the lookup table, based on whose values you want value to be maintained in MDM_Material.
And for each value in the lookup field, you can select the range.
Example: Assigning Material number based on Account Groups.
Hope it help.
Thanks,
Priti
Edited by: Priti Rani Patnaik on Apr 7, 2010 10:23 AM

Can you clone Remote System key mappings?

We have 2 Remote Systems set up for our MDM repository with key mappings for 60 tables. I now need to add an additional Remote System which is similar to one of the existing ones, but with a few different values. Is there any way I can clone the existing one or do I have to go through all 60 tables one by one, export the info, edit it to show the new Remote System name and re-import it? I have searched the sources but can't find anything on this precise topic.
Thanks for any help you can give.
Peter Croft

Peter,
No you cannot.
Prepare a source having Just two columns ex., new Remote Keys of the system and an common identifier field in the table which you are planning to import with the data. Import it and get it to the data manager as records with just two fields(Remote Key and Common identifier). If you have the import maps already stored for the tables when you have done for the previous imports for the other two remote systems, use them and automate the importing process for this particular remote system (via port configuration in console and Data manager) for the remaining fields of the table.

Syndicating based on Addition of a Remote System Key

Hi
We have a distributed system syndication scenario where we need to syndicate a record automatically when a remote system key is added to an existing harmonized record in MDM. By adding the Remote System Key, it essentially means the remote system is 'subscribing' to the new harmonized record.
Is there any way to fire off a syndication event when a new remote system key is added to a record? It seems that MDM currently only flags a record as ready to be syndicated when a value changes in one of the fields of that record - it doesn't seem to identify the addition of a new system key to the record as a change to the record.
Thanks for your assistance in advance.

Hi Ravi
Thanks for the reply. The current view is that we were going to add it manually as a remote system key mapping, as the material record would already exist and would have been harmonized in mdm - so no need to add it through an import map. The scenario is that the master record already exists and another system wishes to also receive this record. Any thoughts on what options do we have if we go this approach?
Also, is their anyway to indicate if a remote system key is added for a new system to an existing mdm material, to indicate when syndicating that the record being sent is a 'Create' record - and hence only to syndicate it to the new remote system added and not to the other systems which also have remote key's against that record?
Thanks
Costa

Unable to syndicate same Remote System with differnt value

Hi,
I am working on MDM 7.1 SP05 and I have the following issue with syndication:
I have a remote system table (Key Enabled) with System as Non-Qualifier and value as Qualifier and I have values in the MDM Datamanager as
MDM ID, Remotesystem (Multivalue Qualifier Table with Key Enabled)
111,((Qual1-Key,Val1),(Qual1-Key,Val2),(Qual1-Key,Val3))
When I syndicate I see only one value as 111, (Qual1,Val3)... But I want to have all the Qualifiers-Key with multiple values.. Where as in MDM 5.5 I can see all the Qualifiers with out any issues..Is this a restriction in MDM 7.1?
If I map System instead of Remote Key of Qualifier Table then I can see multiple times of same remote system with appropriate values.. But If I map remote key then I see the consolidated/the latest system-remote key wiht value... But I want system-remote key value appear multiple times...
Thanks alot
Rajeev

I am using customised...
Did you tried syndicating Remote key of that table or the field of the Qualifer table?
I am able to syndicate out with the system field and values.. But I want to syndicate out the multiple values wiht remote key of the table..
As mentioned Remote keys are AAA and BBB for System Sys1 and Sys2..
First I imported remote system table with Sys1 and Sys2 with remote Keys as AAA and BBB. then along wiht main table record I imported Sys1 and Sy2...
While Syndicating I want to syndicate AAA and BBB values along with Value field...
Suppose:
I have data :
MDM ID, RemoteSystem(System, Value)
111, ((Sys1,Val1),(Sys1,Val2),(Sys1,Val3),(Sys2,Val1))
Remote Keys for Sys1AAA and Sys2BBB
In the Syndication Manager I mapped as below: RemoteSystems RemoteKey and value are mapped to target...
RemoteSystem
--RemoteKey
System(DFNQ)
--Value(Qualifier)
I mapped RemoteKey and Value to the target fields.. Which is a XML output..
<REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val3</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>BBB</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
</REMOTE_SYSTEM>
Where I need the following Output:
<REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val2</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>AAA</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val3</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
- <Z_MDM_REMOTE_SYSTEM >
<Z_MDM_SYSTEM_NAME>BBB</Z_MDM_SYSTEM_NAME>
<Z_MDM_VALUE>Val1</Z_MDM_VALUE>
</Z_MDM_REMOTE_SYSTEM>
</REMOTE_SYSTEM>
Any inputs.
Thanks
Rajeev

Assign records to different remote systems in MDM

Similar Messages

Maybe you are looking for