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
Similar Messages
-
Hi All,
I have 3 fields in my source file Id,Category (Key Mapping) ,Name.
In Import Manager
I have mapped Remote Key field with ID .
Name with Name
category with Category Qualified Range (A 1-10)
I have source file like this
Id name category
11 10 A
In syndicator i have one more field Material Number .Mapped this with Material Number (should Get generated material Number )
Name with Name
Category with Category
Remote Key value with Material Number
After syndication I am getting Id values in Material Number .(Instead of 1 I am getting 11)
Can any one let me know the solution?Got It . Should not Map Id field with the Remote key in Import Manager.
-
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,
AntonyHi 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
RajeevHI 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 -
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 -
Remote Key Manupulation in Java MDM APIs
Hi ,
I need to do create/Modify/retrieve remote key using MDM Java APIs. I have found out two APIs for retrieve and modify of remote key (RetrieveRecordsKeyMappingsCommand and ModifyRecordsKeyMappingsCommand using RecordKeyMapping).
I am not getting any API to create remote key using Java APIs. Can anyone help me in this regard.If anyone has sample code also that would a great help.
Thanks and Regards,
SubhasisHi,
Please have a look on below code ...
/TableID/
TableId tableId = schema.getTable("table Code").getId();
RecordId recordId = new RecordId("R1"); // record id of record to which you are going to add key mapping
/Remote System Properties/
RemoteSystemProperties remoteSystem = schema.getRemoteSystem("RemoteSystemCode");
/*Creating new instance of RecordKeyMapping */
RecordKeyMapping recordKeyMapp = KeyMappingFactory.createRecordKeyMapping(tableId,recordId);
/*Creating new instance of KeyMapping */
KeyMapping keyMapping = KeyMappingFactory.createKeyMapping(remoteSystem.getId());
/*Setting value to Key value */
keyMapping.addKey("1234");
/storing keymapping instance in RecordKeyMapping instance/
recordKeyMapp.addKeyMapping(keyMapping);
RecordKeyMapping [] recordKey = ;
ModifyRecordsKeyMappingsCommand rkm = null;
try {
rkm = new ModifyRecordsKeyMappingsCommand(context);
} catch (SessionException e) {
} catch (ConnectionException e) {
rkm.setKeyMappings(keyMappings);
try {
rkm.execute();
} catch (CommandException e) {
Hope this helps you.
Cheers,
Veeru. -
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,
PradeepHI 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 -
Hi Guys,
I am confused with the remote key concept.
If we have tow remote system attached with MDM then
How we can create remote key automatically when the data come from systems.
Is remotekey+remote system is unique key for each record.
If the same data will come from different system but some fields value is different then how its maintain in MDM and when we tranfer same data to different system from where it came previously then in taht case which data will transfer to each system.
Query regarding import
Yesterday i was trying to import the different languages data in hierarchy lookup table .In the import manager i map each language fields to each destination fields but after importing i get same value in all language fields i.e. whatever info maintain in english.I read somewhere how to import multilingual data in hierarchy lookup nad its mentioned that you have to map remote key also.so i want to know why is necessary to map remote key and if my table is not remote key enabled then in that case how i can trabsfer this multi language data.
Please help me on these issues.
Thanks,
Sudhanshu"Two records coming from two different remote systems which hold different values in some fields" looks to me like a race condition between two remote systems updating for example an typo in an address or name field.
Typical situation: you have local companies holding their indepnedent set of customer data.
Assume that a customer orders at two local companies at the same time.
Assume further that during the entry process there was an address update or a small change in the comapny name.
Assume further someone makes a typo.
Because of the independency they will update the customer locally and send the update to the mdm.
So we have now two differnent values for the same record. In this case typically last one wins. So at the end the last record sent will update the mdm to the last golden master value.
To avoid this situation you can either use MDM as the only entry/update system or put some processes (not only workflows) in place which helps to avoid this situation. In any case bacause of the key mapping both records will map to the single golden master record in the mdm as already mentioned.
d'accord with the hint: this has to be part of the steady consolidation scenario.
regards
lpk -
Key Mapping Conflict of GT780DX
My GT780DX is unable to support 10 keys pressed together, while it is said
"MSI’s gaming keyboard supports simultaneous pressing of 10 keys or more, allowing users to issue commands rapidly and respond to games with precision."
Two examples:
Key I invalid when Key S,D are pressed together;
Key D invalid when Key U,I are pressed together.
I am wondering if my nb is lack of some drivers,
though I have downloaded the most drivers from official site http://www.msi.com/product/nb/GT780DX-GT780DXR-.htmlHi,
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 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 BanerjeeYou 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 -
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
JanDear 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 -
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
KlausHi 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 -
How could I turn off the Command Key to Windows Key mapping in Remote Desktop for Mac 8
I'd like to be able to turn the Command key->Windows key mapping off. In this new app, whenever I use the Command key to initiate a Mac-side function, it registers a press of the Windows key within the Remote Desktop session. Speaking only
for myself, I use the Command Key for quite a lot of Mac operations, while my need and expectation for a Windows key press is zero.I'd like to be able to turn the Command key->Windows key mapping off. In this new app, whenever I use the Command key to initiate a Mac-side function, it registers a press of the Windows key within the Remote Desktop session. Speaking
only for myself, I use the Command Key for quite a lot of Mac operations, while my need and expectation for a Windows key press is zero.
Agreed. Cannot stop it by disabling the "Windows" key (from within Windows 7). Every time I Cmd-Tab to change apps, the Start Menu pops up,
and persists, overlaying other app windows. Much more than annoying.
Also, there is no Clipboard Sharing, apparently. Love typing in long binary strings into the Registry. -
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
Maybe you are looking for
-
Power on MacBook Pro takes me to login screen. All user icons appear as normal. Once I enter password for myself (administrator) spinning takes longer than normal and doesn't log in but displays a no sign (circle w line through it) when attempting to
-
PowerBook G4 1.67GHz Won't Boot, Doesn't Get Past the Grey Screen
The other day I was attempting to Safe Boot, and during the grey screen with the rotating cog, I could hear the hard drive spin down, the the display would turn off. The computer worked fine for the next few days, and now when I attempt to boot it (w
-
Apple Ireland public relations rule Apple all the way
Hey i recently had been having a lot of trouble lately trying to get my hinges fixed on my Macbook. I was told by the company doing the repairs that they were not covered under warranty. I know i did not do anything out of the ordinary to damage the
-
Veritas Volume Manager Upgrade Hints?
We are considering upgrading from Veritas VM 3.0.4 on Solaris 2.6 to 3.1 on Solaris 2.6. o Has anyone else gone through this upgrade? o Did you follow the steps in the "Veritas Volume Manager 3.1 Installation Guide" with success? I notice that under
-
Can I use the new in December iMac monitor with the mini mac?
Considering buying the new iMac the Dec. issue. I wanted to know if this iMac monitor can also be used as a monitor for the new Mini Mac?