Importing Remote Keys.

Hi All,
I am trying to Import a Table which is remote key enabled [Remote Key Mapping = Yes ]. But when i try connecting to a corresponding Remote system using Import Manager, in the " Map Field / Values"  Tab i am not able to see the Remote Key field on right hand side [i.e. Destination Fields].
Pls help out with your suggestions.
Thanks in Advance.
Amol.

Hi Amol,
please make sure that the Client System you use is configured as "inbound/outbound" in the Console. Otherwise, the Remote Key is not available because you didn't define the system as receiving data from MDM.
Regards,
Christiane

Similar Messages

  • Remote Key Field not visible on destination during Import

    Hi All,
    I have made certain tables(Main, Flat,QT) remote key enabled. but when i m trying to import data remote key field in the destination side doesn't come up. Remote sys is of type Inbound/Outbound. Please let me know in case any one can provide any link to this.
    Thanks
    Manish

    Hi Manish,
    I have made certain tables(Main, Flat,QT) remote key enabled. but when i m trying to import data remote key field in the destination side doesn't come up. Remote sys is of type Inbound/Outbound. Please let me know in case any one can provide any link to this.
    There are 2 steps to get the remote key in the Import Manager destination side. One is to ensure that the key mapping is set to YES in Console ( which I guess you have already done). And the other is while Opening import Manager, choose the Remote system in the Connect to Source screen.i.e Mention the remote system name in the Remote System in the Import Manager dialog Box. This would get you the remote key on the destination side, that you are looking out for.
    For reference refer the link below to get the info:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30843106-5539-2b10-75a9-da483911b0d9
    Thanks and Regards
    Nitin Jain

  • 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

  • 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

  • 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

  • Remote key mapping in Category table

    Hi,
    We are not able to populate the Remote key in the Category table.
    In standard repository the Category table only has one field 'Category Name' which is defined as Display Field.
    In order for us to map customer file records which has UNSPSC code with our Category definitions we have added a field 'UNSPSC ID' in the Category table.
    As 'Category Name' is the field that should be displayed we need to use the Remote Key function in order to get a unique identifier in the Category table for automatic mapping of supplier records to the Categories in the Category table. However, we are not able to populate the Remote key field in the destination table Categories.
    The Category table has 'Key mapping' set to yes and in the Import manager we clone the field 'UNSPSC ID' and map the clone to destination field 'Remote Key'. However, 'Remote Key' does not come up as unique Matching field and performing the Import we can see that the Remote key is blank for all records in the category table.
    Does anyone out there know what needs to be done in order to populate the 'Remote Key' in the Category table?
    Please note that we are able to map and populate the Remote key field in other tables such as Product Group, Supplier etc but not in the Category table. Is there some special considerations as this is a taxonomy table?
    Regards
    Jan

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • 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

  • 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

  • Remote Keys for Multiple Systems

    I am working on an SRM project where we have internal catalogs items (from ECC) and external catalog items (from Excel files) going into an MDM Catalog repository.  For both, we use a lookup table for the Supplier number to cross-ref to a supplier name.
    We have a Supplier List message that runs from ECC to MDMCAT to populate this table.  In doing so, it creates a key mapping for the ECC remote system...which gets used for cross-referencing supplier names when catalog items load.
    The issue...we do not have such a Supplier List from the external catalog "remote system", so when external catalog items get loaded there is no supplier number/name cross-ref happening.  I can manually create key mappings for the external remote system, but I want to automate it. 
    I am thinking about having our PI middleware make a copy of the ECC Supplier Lists and send them to a new port set up as the external remote system...thinking that this would generated extenal system keys...hopefully without duplicating supplier lookup records.  Before proceeding, I wanted to throw this out to see if there is a better solution.
    Any suggestions?
    Thanks,
    Keith

    Hi Keith,
    some remarks:
    if you send data from ECC to MDMCAT, the catalog items contain the supplier keys of the ECC system. That's why the import works automatically. If you want to reuse the ECC supplier keys, the first question to answer is: does your external system  use exactly the SAME keys as ECC? Only if this is the case, duplicating the ECC supplier message works for you. Otherwise you'd create keys for your external system that are never sent by the external system.
    If the external system uses the same keys as ECC, the next question is how often do you update the supplier list in MDM? Regularly? Only once? If regularly your option with PI is a good idea. This won't duplicate supplier records as Import Manager (or MDIS) is able to identify already existing suppliers and updates the remote keys only (anyways you should check the related import map!). If it's a one time action only, you can re-open the same file multiple times for different remote systems with Import Manager. Then you wouldn't have to configure an additional connection from PI to MDM.
    Best regards
    Michael

  • 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

  • Remote Key

    Dear Experts,
    I want to know the use of remote key in the import manager. Also wantto know the process how to use the same.
    Thanks,
    Kiran

    Hello Kiran
    For remote key using you should  do that:
    - check your import server is installed and running
    - add more than one remote systems in your repository
    - check thta your main table has setup "key mapping" paramiter to "Yes"
    - for each your remote system inbound port has been created
    - add(or check) field in your repository where you will save your remote key
    - create import map for your source in your import manager
    - add that map to your inbound port
    - check thta your import server is working in automatic mode
    - put source file in ready inbound directory and whait some time
    - if your source file moved from ready directory and you hadn't get import error
    - load data manager and check your data
    - in data manager select record, open submenu, select "edit key mappings" for manage your remote keys
    more information about that you can found here:
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/content.htm
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/72b8aaa42301bae10000000a42189b/content.htm
    Regards
    Kanstantsin Chernichenka

  • Maintaining Remote key in look up tables for Production data

    Hi,
    me
    SEE in DEV and QA to maintain the Remote key for Look up tables.First i have exported those look up table values and again imported with mapping Remote keys (clone the field and map it to Remote key.). By this i have maintained the Remote keys to all look up tables. Now for Production what should i do. Is it the same process extract all records from production into our desktop and then again import it using IM, clone the field and map it to Remote key.
    1. Is this the right process?
    2. What happens if there are huge data present in production how to proceed furthr then?
    Required your suggestion please.
    Thanks,
    Pradeep

    HI Pradeep,
    I dont see any problem with this method if I am getting it right
    You are updating remote keys by reimporting lookup data, and this way you have multiple remote keys for data in lookup table,right?
    This will help you to automap entries in Import process for different Remote systems.
    I did not get your 2nd point?
    Thanks,
    Ravi

  • Remote key issue

    Hi,
    Can someone explain me briefly why should I consider remote key mappings for Sub tables, look ups, hierarchy, taxonomies, qualified?
    Using XML files based on XML schemas in Console I am finding it difficult to assign the Customer_Number (appearing at level 1 of xml file) to sub tables. Since the level 2, level 3 etc nodes appear as different tables in MDM Import manager source table list (with no links to Customer_Number) but only _ID fields showing how many number of entries are there, how do I get remote key mappings accomplished?
    May be I am missing something very stupid... let me know...
    - Dev

    Hi Devashish
    Remote key for lookup table required when say we have Lookup values coming from different remote systems say ECC and some other legacy system which perfoms sales order placed by customers and we have Account groups in both source system.
    regards-
    Ravi

Maybe you are looking for