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

Similar Messages

  • 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

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

  • Key Mapping in Hierarchy Table

    Hi,
         I have enabled the Key Mapping = Yes  for Hierarchy table. But when I imported the records to the Hierarchy table, I am not seeing any key mapping info for the Hierarchy table records. Any thoughts?. Key mapping does not work for Hierarchy tables?.
    Thanks
    Job.

    Hi Job
    Key mappings work fine with hierarchy table as well.What was the means of import for hierarchy table. If you have used a excel file and while connecting to Import manager which remote system you selected. If you have used MDM as remote system key mapping will be blank. we need to add the record key mappings. Select all the records in record mode for hierarchy table and edit key mappings.
    Also which mode you are ssing the records. This will not come in hierarchy mode, select record mode and check the edit key mapping functionality.
    Please award if useful.
    Regards
    Ravi

  • Keynote bluetooth remote - key mapping

    Hello,
    Since I've switched to a MBP Retina, my old Apple IR remotes don't work anymore. I've bought a remote from iStabilizer, the "shutter remote". It works well, except that there is no "menu" button that allows me to have the navigator appear on the presenter screen.
    This is really important for presentation, so that you can skip slides or go backj dependent on the response of your audience.
    Does anyone have any clue how to solve this ?
    By buying another remote that does have this capability;
    By remapping keys one way or another.
    Thanks for the feedback.
    Best,
    Serge

    Thanks Gary,
    That, I found. What I meant is to do this from your remote, like you used to be able to do from Apple's IR remotes. Hit <menu>, scroll a few slides ahead, select, and continue, without your audience noticing anything.
    So, any remote that could replace the Apple remote would be great, or a way to map other remotes to do that...
    If not, this is really two steps back for people who are serious about presentations. I don't think you can take your audience seriously without being able to jump ahead and back in your presentation.
    Best,
    Serge

  • Object key mapping in KSSK table

    Hi All,
    We are facing an issue wherein SAP BW Job is failing as it is not able to pull the data for Hierachy from SAP.
    When we checked the details it seems that there is an error entry in table KSSK.
    However- the table has class type 026 and object key value.
    We are not able to figure it based on the object key that what is error entry.
    I need info to trace back how to find out the error entry based on Object key from table KSSK.

    We had found out the entry which was erroneous and removed the entry.
    Find out the object key and connection between KLAH and KSSK table and they we deleted the erroneous entry from KSSK table. We spoke to SAP in this regards and the entry was created due to reclassification by user for one article.
    The entry was deleted from Table using SE16n.

  • Import Key Mapping of many Remote Systems in one step

    Hi,
    I have to update the key mapping of a flat table. My problem is that I have more than 30 remote systems.
    Is it possible to import the key mapping of more than one system in one step?
    If there is now way to do it with Import Manager can I use APAP API to edit key mapping?
    Much thanks in advance
    Klaus

    Hi Klaus,
    Unfortunately it is not possible to update keys for multiple remote system in one go using import manager.
    But you can use ABAP API or JAVA API to edit remote key mapping. using these API you can write a program/application to update keys for multiple remote system.
    Best Regards,
    Shiv

  • Syndicating Key mapping value from lookup table

    Hi Experts,
    I want to Syndicating Remote Key value from lookup table as per the remote system.
    In syndicator, if I map destination field to the remote key of the lookup table, I am getting blank value.

    Hi Mrinmoy,
    kindly check in the Data Manger whether have you maintained Remote keys for the lookup table. If yes then choose the specified remote system from Remote key override fields under Map properties in the syndicator.
    Incase you cant find the remote system in the "remote key override" field for which remote key is assigned in Data manager, then you need to check the Type (outbound) of the remote system in Console admin node. Because only those Remote systems type set as Outbound can been found in Remote key Override in the syndicator.
    After choosing the remote key you need to map the destination field with Remote key value as shown in the below image.
    Regards
    Rahul

  • 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

  • Create key mapping using import manager for lookup table FROM EXCEL file

    hello,
    i would like create key mapping while importing the values via excel file.
    the source file containing the key, but how do i map it to the lookup table?
    the properties of the table has enable the creation of mapping key. but during the mapping in import manager, i cant find any way to map the key mapping..
    eg
    lookup table contains:
    Material Group
    Code
    excel file contain
    MatGroup1  Code   System
    Thanks!
    Shanti

    Hi Shanti,
    Assuming you have already defined below listed points
    1)  Key Mapping "Yes" to your lookup table in MDM Console
    2) Created a New Remote System in MDM console
    3) proper rights for your account for updating the remote key values in to data manager through import manager.
    Your sample file can have Material Group and Code alone which can be exported from Data Manager by File-> Export To -> Excel, if you have  data already in Data Manager.
    Open your sample file through Import Manager by selecting  the remote system for which you want to import the Key mapping.
    (Do Not select MDM as Remote System, which do not allows you to maintain key mapping values) and also the file type as Excel
    Now select your Soruce and Destination tables, under the destination fields you will be seeing a new field called [Remote Key]
    Map you source and destination fields correspondingly and Clone your source field code by right clicking on code in the source hierarchy and map it to Remote Key if you want the code to be in the remote key values.
    And in the matching criteria select destination field code as a Matching field and change the default import action to Update NULL fields or UPDATED MAPPED FIELDS as required,
    After sucessfull import you can check the Remote Key values in Data Manager.
    Hope this helps
    Thanks
    Sowseel

  • 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

  • How to map lookup main table field in another main table using MDM 7.1?

    We created a new SAP MDM 7.1 repository with multiple main tables.  The first main table is called ProductMaster table which contains Products information.  The ProductCode is the primary key and the only display field for the table during data loading process. The second main table is ProductByRegion table which has a main table lookup field ProductCode and a RegionId field.  These two fields (ProductCode and RegionId) combine as the PK for this main table.  Both main tables have key mapping enabled. 
    I was able to load ProductMaster table using Import Manager.  But Iu2019m having trouble to load data into ProductByRegion table using MDM Import Manager.  Although I have met all the 5 requirements below (excerpted from MDM Import Manager Reference Guide P.222), the ProductCode wonu2019t show up on the destination value pane.  If I mapped all productCode to NULL field, ProductCode wonu2019t load.  If I u2018Addu2019 all ProductCode to Destination Value pane, the Import Manager added duplicated rows to Product Master table while only loading 1 record to ProductByRegion table.  I canu2019t get ProductCode show up in Matching Destination Field list.  When I checked ProductMaster records in MDM Data Manager, I right-clicked on one of records, chose Edit Key Mappings, it didnu2019t show anything.  However, if I right-clicked on one of those duplicated rows, Edit Key Mapping shows remote system and key correctly.
    Where did I do wrong?  How can I fix the problem?
    Thank you for help in advance.
    From: SAP MDM Import Manager Reference Guide:
    Mapping to Main Table Lookup Destination Fields
    Import Manager handles main table lookup fields (Lookup [Main])
    differently than other MDM lookup fields. Specifically, Import Manager
    does not display the complete set of display field values of the records
    of the underlying lookup table. Instead, the values it displays for a main
    table lookup field are limited by both the key mappings for the lookup
    table and the values in the source file.
    Also, Import Manager does not automatically display the values of a
    Lookup [Main] destination field in the Destination Values grid when you
    select the field in the Destination Fields grid. Instead, for a main table
    lookup field value to appear in the Destination Values grid, all of the
    following conditions must be met:
    u2022 The lookup table must have key mapping enabled
    u2022 The lookup field must be mapped to a source field
    u2022 The source field must contain key values for the lookup table
    u2022 The destination value must have a key on the current remote system
    u2022 The destination valueu2019s key must match a source field value
    NOTE ►► The current remote system is the remote system that was
    selected in Import Manageru2019s Connect to Source dialog (see
    u201CConnecting to a Remote Systemu201D on page 416 for more information).
    Vicky

    Hi Michael,
    Thank you very much for your response.  I'm new to SAP MDM, I need some clarification and help regarding your solution. 
    I did use two maps to load ProductMaster and ProductByRegion separately.  Here were my steps:
    1. create main table ProductMaster with key mapping enabled at the table level and set ProductCode as unique and writable once (primary key).
    2. create a map to load ProductMaster record from a staging table located an oracle database.  But Key mapping didn't show anything when I looked at them using Data Manager.
    3. create main table ProductByRegion with a lookup field looking at ProductMaster table.  This field and RegionId combines as a unique field for ProductByRegion table. 
    4. create a map to load ProductByRegion table.  But ProductCode records only shows on the source pane not destination pane and can't be mapped properly.
    My questions:
    1. How can I "Ensure that you add key mapping info for all ProductMaster records" besides enabling Key Mapping on the table level?
    2. How can I define a concatenation of ProductCode and RegionId as a REMOTE KEY"?
    Thanks a lot for your help!
    Vicky

  • Steps in Key mapping

    Hi all,
    i have gone through many forum's regarding key mapping.
    i can see that the following are used..
    --> remote systems
    --> key mapping option in table-field properties
    --> key mapping option in table properties.
    -->key generation(none, range, qualified range) field in remote system properties.
    But never understood like in which order we need to define all the above, what is the relation b/w them.
    i have gone through some theory in sdn regarding key mapping but unable to get the logic..
    can any one one show me with 2 records in 2 tables so, that i can clear my confusion.
    Thanks in advance.
    Regards
    phani

    Hi Phani,
    first you should understand the basic idea of key mapping. MDM usually wants to consolidate master (objects like vendors, customers, and so on) and/or reference (lookup tables like countries, regions, and so on) data. The idea is to load this data from various remote systems into MDM, compare and match the data, and in some cases merge multiple records into a single one. Let's take an example.
    Image you have attache two remote systems to MDM. The first is an ERP system, the second a CRM system. Both system contains countries as reference data. In ERP, your country India looks like
    Name = India
    Code = INDIA
    whereas in CRM it looks like
    Name = India
    Code = IND
    It is obvious that the country is the same, but the systems use a different internal code. Now you load this data into MDM. What do you do? Do you want to create two records having different codes? Or do you want to "merge" the indentical records into a single one. The common decision in MDM is the second one.
    But what happens now if you send customers from ERP and CRM to MDM? Usually the Customer message contains the Country CODE but not the Country NAME. From ERP the message could look like:
    Customer = Mr. X
    Country = INDIA
    whereas from CRM the message could look like
    Customer = Mr. X
    Country = IND
    Surely you want to map the different code in both case to the same country "India". That's why you use key mapping in MDM. Key Mapping allows MDM to store different codes for the same data. So in MDM you store just one record, but if you receive and/or send data from and/or to remote systems, you can always ensure that you store and/or send the correct codes.
    Hope that clarifies your doubts about key mapping in general?
    OK, now regarding your question about "Update NULL fields only":
    In Import Manager you have several options for data import. If you import for the very first time (for RS1), your table in MDM is usually empty. That why you need to "Create" the records. If you import the second time (for RS2), your table in MDM already contains data. Depending on the matching field for import, several options are now possible. If Import Manager is not able to match the record you want to import against any other existing in the repository, you have to "Create" the new record. If Import Manager is able to match the record that you want to import with a record of your repository table, you can choose what happens next. "Update NULL fields only" compares the record you want to import with the existing values in MDM. In your case, following info is already part in MDM:
    Country = India
    Code = INDIA
    Remote Key RS1 = INDIA
    Remote Key RS2 = NULL
    Now the file you want to import contains the following values:
    Remote System = RS2
    Country = India
    Code = IND
    Import Manager identifies that only "Remote Key RS2" is NULL. All other fields already have values. As you choose to "Update NULL Fields only", only Remote Key RS2 gets a new value. If you choose a different option, e.g. "Update All Mapped Fields" Import Manager would update the Country and Code fields, too.
    Best regards
    Michael

Maybe you are looking for