Syndicator - Remote Key

I'm trying to map some Remote Keys at the Syndicator, but i'm having the following problem:
The key mapping values from source do not transfer any value to destination. My Remote System is the "MDC R/3 & ERP", but I have tried to configure the "Output Remote System" property as "MDC R/3 & ERP" and I have inserted the remote key values in flat tables (lookup).
What need I to do to get the key mapping values in Syndicator?
Evandro.

Hi Evandro,
The key mapping values from source do not transfer any value to destination. My Remote System is the "MDC R/3 & ERP", but I have tried to configure the "Output Remote System" property as "MDC R/3 & ERP" and I have inserted the remote key values in flat tables (lookup).
To syndicate out remote Key form Remote system in MDM syndiactor you need to take care of the following:
- Enable the Key mapping as Yes in MDM Console.
- While Importing data either for the main table records or the Lookup table records make sure to map the Unique key field from the source side to the <Remote key> in the destination in MDM Import manager.
- In the syndicator you need to take care of two imp things
- Firstly while opening the syndicator you need to select the Remote system in the destination properties(File>New)
- This will make sure that you are sending the key mappings to that remote system.Output remote system property works slightly differnt.
- You need to make sure that the first property in MDM syndicator under the map property tab(remote system) is having your Remote system name.
- Then you need to map the the value field(under remote key in the source) to the destination field for remote key.
You will understand better in the below related links:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c (Key mapping)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30843106-5539-2b10-75a9-da483911b0d9 (Key mapping)
Hope It Helped
Thanks & Regards
Simona Pinto

Similar Messages

Why two remote keys are genrated in data manager when i'm syndicating the same records twice

Hi Experts,
Please guide me that will there be any problem if two remot keys are getting generated for the same system thougt we are expecting to update the same Business Partner Number in ECC.
Also We are able to see two different business partner number(in ECC this is KUNNR in KNA1)
Please guide me how to proceed so that when we syndicate the same set of records we want to get update the records in ECC for the same KUNNR.
We don't want to get another KUNNR for the same records.
Thanks!
Pankaj

"barbara" wrote in message
news:506500000008000000FAC20000-1077587809000@exchange.ni.com...
> I'm using the simulation interface toolkit V2.0 but it works only the
> first time after the installation. When I restart again my computer it
> doesn't work any more. Why??????????
>
---snip
I am not familiar with the different software that you mentioned but as a
first step I would check compatibility which is done as below:
Get original operating system CD that was used to install Windows XP on the
machine in your post. When Windows XP is inserted into CD ROM drive it
normally will ask you to conduct compatibility check for the current
installation. See what it says.
HTH
Mohan Pawar
----snip

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

Key mapping/ remote key

Hi All,
I have some understanding of key mapping internal functionality.
my question is ... should I use this key mapping feature from all look up tables, main table while importing from remote systems?
should all my feilds have REMOTE KEY enabled.
Lets say I have loaded data into my repository from 3 different remote systems(R1,R2,R3) using remote key feature.
Now, I want to see all the records that belong to R1 only or R2 only?
Can this be seen using remote mapping feature? or how can I see only specific records for one remote system.... should i create another field that identifies the source and just map it? ....... generally how do we handle this?
Also, have uploaded the data for my lookup table DIVISIONS,when i try syndicating it for remote R1......
in my destination preview i can see some records that belong to only R2 and R3 also. I mean I am not able to see only the
records belong to R1 system.
I mapped
division <-> div
desc     <-> desc
there are two more keys like remote key, v...... Should I also map these keys?
Pls let me know,
Thanks & regards,
Vee

Hi,
my question is ... should I use this key mapping feature from all look up tables, main table while importing from remote systems?
should all my feilds have REMOTE KEY enabled.
1. It is totally dpeend upon business requirement which table you want to make remote enable.
    The main reason to use remote key is to syndiacte the data to remote system specific.
     So if you are syndication your subtables to then it is good to make remote key enable.
2. Only tables are remote key enabled not the fields.
Lets say I have loaded data into my repository from 3 different remote systems(R1,R2,R3) using remote key feature.
Now, I want to see all the records that belong to R1 only or R2 only?
Can this be seen using remote mapping feature? or how can I see only specific records for one remote system.... should i create another field that identifies the source and just map it? ....... generally how do we handle this?
This is not possible as standard way.
But workaround is when you map the source field to remote key at destination side in import manager,just make the clone of source field and map it to the new fields to store the system from where the records came.
So in data manager you can search on this field to see only records that is specific to some remote system.
Also, have uploaded the data for my lookup table DIVISIONS,when i try syndicating it for remote R1......
in my destination preview i can see some records that belong to only R2 and R3 also. I mean I am not able to see only the
records belong to R1 system.
I mapped
division <-> div
desc <-> desc
there are two more keys like remote key, v...... Should I also map these keys?
Yes you have to map these fields as well.
Even after mapping this option if you want to syndicate all the remote system records then there is option "override remote keys".after enabling this option there is record generated for each remote system.
hope it helps you.
Thanks,
Sudhanshu

Remote Key values in one file

Hi,
Is there anyway to get the multiple remote key values(different remote systems) for a single record in a single XML file?
Regards
Nisha

Hi Nisha,
you can do this with Syndicator. Asuming that you have defined a XSD for your desired XML format, you can create a syndication map that uses the remote keys for all remote systems. The tab "Map Properties" has a property named "Remote Key Override". This property allows you to select the remote systems that you want to include in syndication. If you add all existing remote systems and set the property flag "Suppress records without key", syndicator creates an XML containing all remote keys.
A suitable XML format could be something like
<Root>
<Record>
    <MdmId />
    <RemoteSystemCode />
    <RemoteKey />
</Record>
</Root>
Record is the repeatable node.
Use MdmId to identify the record in the repository (this is optional of course).
Use RemoteSystemCode and RemoteKey to syndicate the key mapping.
Best regards
Michael

Number Generation & Remote Key Updation

Hi Experts,
We have a scenario of integrating MDM with SAP and 3 Non SAP systems
All the systems have the same number range for the account types
Whenever there is a request , a copy should always go to SAP plus the requested system
Doubt:
The request comes to the import server and the requirement is to automate it
Now the question is how to generate the number in main table and it should update the key mapping of 2 remote systems automatically
Kindly help
Regards,
Antony

Hi Antony,
As you have 4 remote systems, one SAP and 3 non-sap systems, you need to create 4 remote systems in MDM Console ( as shown in page 3/10, 1.2 Create/modify the remote system u201CSAP R/3u201D and specify type as u201Cinbound/Outboundu201D and key generation as u201CQualified Rangeu201D in below article).
While syndicating you have to select remote system one by one as it is shown here for SAP R/3 (on page 5/10, 2.5 Specify the type as u201CFlatu201D and remote system same as created in step 1.2 : u201CSAP R/3u201D ), you need to do it for all the 4 remote systems one by one. you need to be carefully map remote key for all of these remote systems as shown in section, 4.2 The u201CSAP Material Numberu201D field, which is to be generated during syndication, is to be mapped to the remote key field u201CValueu201D.
For complete understanding, Please refer the below Article.
[Using qualified ranges to generate SAP numbers|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/807ce1ba-94c0-2a10-a398-afdfd8135ebd?quicklink=index&overridelayout=true]
Regards,
Mandeep Saini

Is it possible to Update Remote Key

Hi,
I have a remote system which create remote key while syndicating to ERP...
ERP will create the material number which inturn needs to be updated in MDM using import manager..
While importing I am mapping Material number to remote key.. which is creating new remote key along with defualy remote key generated while
syndication... Is it possible to have one key as it is of same material from same system? And at the same time it is again syndicating after
I import with material number (Remote Key)..
Thanks
Rajeev

HI Ravi,
by doing so I am having the dublicates in the Data Manager...
Steps I peffromed :
I have a main table of fields FName(DF),LName,City ....I created a remote Sytem (Remote1) with range of 1000 to 2000 .. Imported two records say ((A,AA,City1)(B,BB,CITY2)) using FName as matching filed (I didnt mapped remote key).. MSS is started so I see the keymapping as A,Remote1 and 1000 and B,Remote1 and 1001 for these two records..
NNow I created a dummy remote system and added a new field to the main table MatNumber.... I importing the file with (A,AA,City,Mat1) and remote system as dummy where I am mapping MatNumber to Remote Key... By doing so I see three records with one record dublicating as It got imported from new remote system with key value Mat1..
Can you please guide how to havve only two records by just updating the key value....
Thanks
Rajeev
Edited by: rajeev raj on Jun 22, 2010 10:53 AM

Default remote key check box

Hi ,
Does anyone know the significance of defalut remote key mapping check box that appears during Edit Key mapping ?
Let me know if it can be used in any way.
Regards
Yogesh

Default remote key check box is used to select 1 record among multiple merged records from same remote system.
if you get 2 or more duplicate records from 1 source systems, then only 1 record out of them can have default remote key check box.
an MDM object may map to multiple keys from the same remote system. When an MDM object maps to multiple keys, one of the keys is marked as the default key. The default keys the one that is used when syndicating a reference to the mapped MDM object.
For example, for a particular remote system, the two color objects Light Red and Dark Red both map to the MDM object Red. An MDM product object Shirt has a Color attribute set to Red. When this Shirt object is syndicated back to the remote system, the default key is used to choose the value to syndicate from the two objects Light Red and Dark Red.
+ An
Try to close your previous questions if they are answered.

Remote key for lookup tables

Hi,
I need some advice on remote keys for lookup tables.
We have loaded lookup data from several client system into the MDM repository. Each of the client system can have diffferences in the lookup values. What we need to do is to enable the keymappings so that the syndicator would know which value belongs to which system.
The tricky part is. We haven't managed to send out the values based on the remote keys. We do <b></b>not<b></b> want to send the lookup tables themselves but the actually main table records. All lookup data should be checked at the point of the syndication and only the used lookup values that orginally came from one system should be send to that particular system. Otherwise they should be tag should be blank.
Is this the right approach to handle this demand or is there a different way to take care of this? What would be the right settings in the syndicator?
Help will be rewarded.
Thank you very much
best regards
Nicolas

Hi Andreas,
that is correct. Let's take two examples:
1) regions
2) Sales Area data (qualified lookup data)
Both tables are filled and loaded directly from the R/3s. So you would already know which value belongs to which system.
The problem that I have is that we will not map the remote key from the main table because it will be blank for new created master data (Centralization scenario). Therefore we cannot map the remote key from the attached lookup tables, can we?
The remote key will only work for lookup tables if the remote key of the actual master data is mapped. Since we don't have the remote key (local customer ID form R/3) in MDM and since we do not create it at the point of the syndication... how would the SAP standard scenario would look like for that?
This is nothing extraordinary it's just a standard centralization scneario.
Please advice.
Thanks alot
best regards
Nicolas

Automatic remote key updation in data manager after a data import.

Hi experts,
I'm using SAP MDM 7.1 SP10 and after I do a data load via import manager my remote keys of lookup tables are updated. For example, lets just say I do a vendor mass load for some operating company for which I didn't maintain remote key for lookup table "Country" (figure Before load) and after the load its autometically updated in data mager (figure After load).
Before load.
After load.
I want to understand if its noramal SAP behaviour or not. If yes, how can i avoid this.
Thanks and regards
Shamit Prakash

Hello Ravi, I just want to leverage Shamit question :
I noticed the same behavior after the key mapping enable and the problem is : every time I import a file via Import manager now, when I check my mapping, sometimes a supplier that does not exist in my file is mapped with a different one from MDM. Previously the key mapping property was enabled, if this situation occurs in my import, as the supplier is a key in my map, this field would not be mapped and I had to correct my file or include this supplier in the database. Now, this became dangerous, as my import can map wrong information. Do i have another option to syndicate only changed records, without enable the key mapping ??? Example : use the selection Criteria in syndicator.

Import Manager Remote Key issue

Dear All,
I have imported all the records from R3 system in Material repository. Since the full MATMAS xmls were of bigger size I devided it into 5 ports MARA, MARC, MARM, MVKE, MBEW.
Now while importing MARA, remote key was not mapped by mistake.
But we want local Material numbers (i.e. material numbers from R3).
so now do i need to reimport everything again or is there any workaround to it.
-Poonam

Hi Poonam,
In lines with what nitin has said
I feel is the right way to go about with the scenario when you have to deal with remote sytems and remote keys.
To explain:
When ever you are importing data from an external system you need to maintain a remote key which will identify that these set of records are coming from a differnt remote system.
For this we use Remote sytem mapping.
The unique key of the incoming source file is to be mapped with the remote key in the destination side in Import manger.
This remote key will then act as your primary key and can be used in the matching field tab.
The unique key then can be cloned to map it with its correcponding field in the MDM rep.
Eg Material no -> Remote key
Material no(cloned) -> Material no
Then when you syndicate these field you need to do proper mapping in the syndicator for the remote sytem and then on your local id will be store in the value field and global id in the remote key field
Hope it helped
Kindly reward points if found useful
Thanks
Simona

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?

Isn't there remote key concept for Hierarchy lookup Tables?

I don't see the [remote key] field in destination items.?
I really don't intend to use this remote Key concept in syndicating back to the source system, but specifically to satisfy this operation need:
I have a hierarchy table with two fields and both of them need to be display fields, Code & Name for Business reasons.
So when loading in the hierarchy field at main table level, I don't have to go through this compounding effort and just map the remote key which is just the code and not the name?
-Sudhir

Yes, remote key is available for Hierarchy Table as well. Set remote key ON on hierarchy table.
As per your Business requirement, you can create clone of code field and then map code to remote key and clone to Code field while initilizing hierarchy table in repository. Then while importing Main table data, if you are getting code in the source file, you need not to map code with the name of the hierarchy. if the code exists as remote key then Import Manager will automatically map code with the Hierarchy class name..
Try this and am sure it will work and solve your problem.
Regards,
Shiv

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

Remote Key Mapping - Maintanance

Hi All,
I have Auto Id field in my repository; I would like to maintain this as my remote key value in my key mapping table ( automatically) in the following scenarios:
1. Initial Loading
2. On going ( from portal)
3. Manual creating a record
The issue is, since its auto id - not available until unless it get created?
Do I need to syndicate all and loop back as Import and update remote key??? or any webservices and so?
thanks,
Alexander.

Hi Raja
You are correct on the approach. This can be done by automatic syndication of the newly created records from any of the channels( excel import, Portal, MDM GUI) to Outbound ready folder from where the files are copied to Inbound folder and automatically imported back in MDM. Steps to be followed can be-
Create ports for syndication and auto Import
The syndication map should contain mapping for Auto ID and any other unique field for reference. Assign this to Outbound port above.
The map used for importing should contain mapping of Auto ID to remote key for the record.Assign this to Inbound port above.
Define/set up a batch job for copying the files from Outbound Ready folder to Inbound Ready folders.
hope this helps.
Ravi

Syndicator - Remote Key

Similar Messages

Maybe you are looking for