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

Similar Messages

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

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.

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

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

Intercompany and Key Mapping Price List

Hi expert,
I have the Intercompany Add-ON version 2.0.8.30 installed on a SAP Business One 9.0 PL15 for 4 localization:
Head Office (H000): IT
Branch 001 (B001): FR
Branch 002 (B002): DE
Branch 003 (B003): CH
This is the scenario:
I started two weeks ago without Key Mapping the Price List because the first choice was that to use different price lists for each country.
Now, I need to replicate the H000 price lists in new created rice List in each brench.
We created new Price lists named "ZZ IT 01", "ZZ IT 02" and so on and we Key Mapped them.
Here the screenshot for Key Mapping:
Problem is that:
NO REPLICATION APPENS!
The Mapping was created 1 week ago but NO syncronization appened...
So, the question is: How I can syncronize the Price Lists?
thanks in advance,
Jonny Cortonicchi

Hi ,
In ABAP API also you can retrieve key mapping of main table records using function 'MDM_API_RETR_CLIENT_SYS_KEYS'.
You will get details of this function in sap library or ABAP API documentation provided by SAP.
For any further queries kindly reply.
Regards,
Neethu Joy

ABAP API and Key Mapping

Hello there,
I am trying to use the MDM 7.1 ABAP API to access MDM data from within a BI system.
Now I am wondering how to access key mapping for records in the Main Table.
In the Java API there is the RetrieveRecordsKeyMappingsCommand which returns all key mapping information for a list of record IDs. But I cannot find something similar in the ABAP API.
Who knows where to start?
Thanks for hints
Ingo

Hi ,
In ABAP API also you can retrieve key mapping of main table records using function 'MDM_API_RETR_CLIENT_SYS_KEYS'.
You will get details of this function in sap library or ABAP API documentation provided by SAP.
For any further queries kindly reply.
Regards,
Neethu Joy

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

How to view the key mapping when viewing Hierarchy in Data Manager

Hi! I previously posted a question on doing value mapping using the hierarchy code rather than the name. I have got that working now using concept of remote key. When I first loaded the hierarchy with remote key and check in Data Manager, I can see the hierarchy structure with the key mappings. However, when I subsequently went back to the hierarchy to have a second look, the keys are gone. Does anyone know how I can view hierarchy in Data Manager with the key mappings?
Cheers!
SF

Hi,
Go to Record mode, and open Hierarchy table. Now to select click on any hierarchy node record and then right click and select "Edit Key Mappings". This will show you existing keys as well as allow you to manually modify keys. You can only Check Remote keys on hierarchy in Record mode and in Hierarchy Mode "Edit Key Mappings" option will be disabled.
Please revert if you face any issue.
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

How to Maintain Surrogate Key Mapping (cross-reference) for Dimension Tables

Hi,
What would be the best approach on ODI to implement the Surrogate Key Mapping Table on the STG layer according to Kimball's technique:
"Surrogate key mapping tables are designed to map natural keys from the disparate source systems to their master data warehouse surrogate key. Mapping tables are an efficient way to maintain surrogate keys in your data warehouse. These compact tables are designed for high-speed processing. Mapping tables contain only the most current value of a surrogate key— used to populate a dimension—and the natural key from the source system. Since the same dimension can have many sources, a mapping table contains a natural key column for each of its sources.
Mapping tables can be equally effective if they are stored in a database or on the file system. The advantage of using a database for mapping tables is that you can utilize the database sequence generator to create new surrogate keys. And also, when indexed properly, mapping tables in a database are very efficient during key value lookups."
We have a requirement to implement cross-reference mapping tables with Natural and Surrogate Keys for each dimension table. These mappings tables will be populated automatically (only inserts) during the E-LT execution, right after inserting into the dimension table.
Someone have any idea on how to implement this on ODI?
Thanks,
Danilo

Hi,
first of all please avoid bolding something. After this according Kimball (if i remember well) is a 1:1 mapping, so no-surrogate key.
After that personally you could use Lookup Table
http://www.odigurus.com/2012/02/lookup-transformation-using-odi.html
or make a simple outer join filtering by your "Active_Flag" column (remember that this filter need to be inside your outer join).
Let us know
Francesco

Key Mapping for Flat lookup tables

Hi,
How do we decide if we need to make Key Mapping "Yes" for flat look-up tables?
Can anyone plz explain with an eg on where to make key mapping yes or no for Flat Tables.
Thanks,
Ketan

Hi,
Can anyone plz explain with an eg on where to make key mapping yes or no for Flat Tables.
1. A remote systems objects are mapped to master data objects within MDM using key mapping. A key mapping maintains the relationship between the remote systems identifier (or key) for an object and the corresponding master data object in MDM.
2. in the data manger based upon some strategy, you found that 4 records are duplicate, and then you merged into single record.
the merged record is having 4 records inside it with respective remote keys.
if you want to edit those records, key mapping should be enabled for that particular table.
3. while harmonizing the records to the respective client systems, you can use edit key mapping functionality for merged records.
if you enabled key mapping functionality in the console for the particular table, then only you can aceess EDIT KEY MAPPINGS functionality in data manager & syndicator.
hope this may help you,
Regards,
Srinivas

Key mapping during the transportation (lookup tables)

Hello,
For look up tables with key mapping during the transportation from DEV-> QA -> Prod it is asked to copy development repository with "out master data" How can we do it? and also how are workflows and matching stragetits transported ?
Thanks

Hi
For look up tables with key mapping during the transportation from DEV-> QA -> Prod it is asked to copy development repository with "out master data" How can we do it? and also how are workflows and matching stragetits transported ?
When we are moving from dev to QA to prod normally the remote system to which MDM is interacting also moves to similar environments. In different environments the reference table data may not match and hence it is advised not to move with same data. You can do this by simply exporting the schema of the repository from dev to QA and so on. That is create a new repository in QA and Prod by using option of "Export from Schema".
Matching strategies and workflows are not supported in this schema transport for MDM 5.5
These has to be created manually once the repository has been created.
Good news is MDM 7.1 supports this.
regards
Ravi

MDM API to read the Record Key Mapping table

Hi,
Does anybody know what class/method I can use to read the Record Key Mapping table?
For the Business Partner table the Key Mapping table has this columns:
Default / MDM Partner ID / Remote System / Key
I have everything but the Key. How can I read it?
Thanks in advance,
Diego.

GetKey Mapping is one of the available Web Services as of SP4.
Else you could use the Java API to get the Key Mapping.
CatalogData class has the following method
GetKeyMapping
public java.lang.String[][] GetKeyMapping(java.lang.String agency,
 java.lang.String table,
 int[] recordIDs,
 boolean isDefaultKeyOnly)
 throws StringExceptionRetrieves the key mapping for each record.
Parameters:
agency - the agency name.
table - the table name.
recordIDs - the list of records.
isDefaultKeyOnly - True to retrieve only the default value, False to all key values.
Returns: the key values for each record.

Key Mapping in Hierarchy Table

Similar Messages

Maybe you are looking for