Key mapping from vt100 to vt220

my existing system is in forms3.0 and report writer3.0 with
oracle 7.1 on aix 3.x with vt100 terminal
now I have upgraded to forms and report developer 6i , oracle 8i
on aix 4.3. as forms6i and report6i only supports vt220 , I have
to map my vt100 key functionality to vt220 terminal.
is there any utility for doing this ??
can i do it using oraterm or any other utility is ther??

dear Joseph,
you can use datasource 0plant_text, 0plant_attr and 0material_text and 0material_attr to extract r/3 material and plant to bw. they are using view to access mara and lfa1.
logon to r/3 and tcode rsa5, choose application component LO-IO, and transfer these datasources,
then from bw, rsa1->source system->r/3 source system->right click 'datasource overview' and go to the same application component node, and 'replicate datasource'.
then rsa1->infosource and locate 0material and 'assign datasource', choose r/3 source system and datasource 0material_text and 0material_attr. do the same for 0plant.
the other way is through business content activation, using infoobject 0material and 'in dataflow before'.
hope this helps.

Similar Messages

Key mapping in vt100 terminals

Dear sir,
The current application is running in the below Configaration.
1. IBM RS 6000 AIX 4.0
2. Oracle 7.2
3. Sql*forms 3.0
4. unix
Sql*form3.0 application is running in this above Configared server.Now the client required to connect this unix server to another
client pc( windows based pc) using telnet connection in vt100 terminals. once they connect then they can invoke the same sql* forms3.0 application
from the client pc .now they want the same key board functionality in both the unix server and client pc .how to key map to bring the same
unix server key board functionality into the client widows based pc. (whatever sql*key board fuction available in the unix platform they want same key board
help in the client widows based pc in vt100 termianals).
example :
In the sql* froms3.0 application if they press f4 key for saving
the records in the unix platform .when they invoke the same
sql*form 3.0 application from the client pc (telnet connection vt100
terminals).They want the same f4 key function to save the records
in the telnet
connection
vt100 terminals (widows based pc)
how to key map in the vt100 terminals?
please help me .

do a google search on :
kermit terminal emulation oracle forms mapping keys
in general there are two options :
1. create your own oracle terminal resource file and tell sqlforms to use it
or
2. use your terminal emulator (e.g. KERMIT) to rearrange the function key strings and work with a given terminal type
back 1994 I did it succesfully by using kermit, good stuff

MDM Exception: Key mapping value must be unique. You cannot overwrite key

"ServerException: Key mapping value must be unique. You cannot overwrite key mapping values."
I received such exception when code tried to manipulate Key Mappings of the record.
error was not happen on mdm 5.5 but on 7.1 it sometimes appears.
What is probable reason of this?
How to resolve this ?
Code is approximate so:
                                     String[] keys = keyMapping.getKeys();
                    if (recordKeyMapping.containsKeyMapping(remoteSystem)) {
                recordKeyMapping.replace(remoteSystem, keys);
          else {
               recordKeyMapping.addKeyMapping(keyMapping);
          //Persist
          targetRecord.update();
//where methods are:
     public void replace(RemoteSystem remoteSystem, String[] keys) {
          KeyMapping keyMapping = getKeyMapping(remoteSystem);
          if (keyMapping == null) throw new IllegalArgumentException("Can't update keys: key mapping for the system '" + remoteSystem + "' is not found");
          else {
               keyMapping.setKeys(keys);
     public void addKeyMapping(KeyMapping keyMapping) {
          RemoteSystem remoteSystem = keyMapping.getRemoteSystem();
          for(int i = 0; i < keyMapping.size(); i++) {
               addKey(remoteSystem, (String) keyMapping.get(i));
Edited by: Vladimir Grigoryev on Oct 5, 2010 11:26 AM

Hello -
I am not sure on that coding part. but is it like are you trying to retrive Key Mapping from Memory accelerator. Here this information always needs to be read from Database.
I am sure you also maintained the required attribute for key mapping as in Property in Console should be set as "Yes" and other relevant things properly .
Here also go through the below link for more insight from tools perspective.
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30843106-5539-2b10-75a9-da483911b0d9
http://help.sap.com/javadocs/mdm/sp06/com/sap/mdm/data/KeyMapping.html
It may help
Rgds
Deep

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

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

Question about key mapping for bank data in SP3 standard Vendor Repository

Hello Colleagues:
The situation is the following:
1) MDM Standard vendor repository does not use Key Mapping for the qualified table data "Bank Details". This makes sense because normally you would pay a vendor in the same account and bank regardless of the company or R/3 system you are paying him from.
2) However, here in my project customer don't have the same bank data for all of the 3 R/3 Systems. Furthermore, they would like to pay a vendor in a diferent bank and account number; depending on where the payment is generated (Company or R/3 system).
Because of this, I though about creating a lookup table for the banks which would use key mapping. I did this and I had no trouble importing bank data in to it.
Now I have this tables:
1) Banks: Lookup Flat:
Country and Bank Key as display fields.
2) Bank Details: Qualified Flat:
2.a) Field "Bank" as a non-qualifier display lookup field which points to a record on "Banks" table (Described in number 1).
2.b) The rest of the fields (Account number, Account holder, Reference, etc.) as qualifier non-display fields.
This aproach works well in data manager.
However, when I try to import vendors from R/3, I'm not being able to map the bank details, not even with "compound field" functionality, because I cannot map the display fields in the "Banks" lookup table (Described in number 1); in the "Map Fields/Values" tab in the Destination fields pane, it won't show any fields from this table.
Also, I'm not very sure if I will be able to syndicate this data back to the R/3 systems correctly, this is; replicate only the banks which exist on each R/3 client system.
Any ideas on how to solve this problem? Please help.
Best Regards,
Jorge.

... Where
did Terminal's default keystrokes (e.g., Esc,[5C for
ctrl-right-arrow) come from? They just produce
annoying beeps in bash. Are they standard sequences
for some shell that I don't know about? I
Somewhere deep in the bowels of computer history....for example
http://vt100.net/docs/vt100-ug/table3-6.html
http://www.termsys.demon.co.uk/vtansi.htm#cursor
that is to say, these codes date back to early hardware terminals such as the VT100. I believe. And that is why Terminal is a member of a class of software called "terminal emulators".

Remote System and Remote Key Mapping at a glance

Hi,
I want to discuss the concept of Remote System and Remote Key Mapping.
Remote System is a logical system which is defined in MDM Console for a MDM Repository.
We can define key mapping enabled at each table level.
The key mapping is used to distinguish records at Data Manager after running the Data Import.
Now 1 record can have 1 remote system with two different keys but two different records cannot have same remote system with same remote key. So, Remote key is an unique identifier for record for any remote system for each individual records.
Now whenever we import data from a Remote System, the remote system and remote key are mapped for each individual records. Usually all records have different remote keys.
Now, when syndicating back the record with default remote key is updated in the remote system that is sent by xml file format.
If same record is updated two times from a same remote system, the remote key will be different and the record which is latest contains highest remote key.
Now, I have to look at Data Syndication and Remote key.
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back. But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
Regards
Kaushik Banerjee

You are right Kaushik,
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back.
Yes, but if they are duplicate, they needs to be merged.
But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
This is after merging. So whichever remote key has tick mark in key mapping option(default) , it will be syndicated back.
Pls refer to these links for better understanding.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/80eb6ea5-2a2f-2b10-f68e-bf735a45705f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c%0c
Hope this helps,
+ An

Key Mapping - Automation

Hi , I have a following scenario that I want to automate within MDM :
Vendor data coming from 3 remote systems ( say p-Carrd , Legacy Supply management and Invoice system) .
1. Have loaded vendor data from all the systems in MDM using import manager .
2. Have applied rules for match and then merge for likely identical records
3. Now I want to see the key mappings for the merged record to determine say what are the source records have been merged into a single record so one way is I could add the id of source systems for this MDM record but that is manual .
Is there any way to automate this i.e. whenever I merge records and clieck on view key mapping I should have all the source system ids and remote systems appearing .? Key mapping is enabled for main table i.e. Vendor master
Regards,
Amit

Hi Amit,
first before importing any records, you should add your different source systems to your repository in MDM Console. You can do this in the Admin section. Having done this you can already import your source files for your source system. This step will automatically create a key mapping entry that can be seen in MDM Data Manager. Make sure that you map the actual key field of your record to the destination Remote Key field in your import map. If you now merge records from different source systems in MDM Data Manager, the merge will automatically append the remote keys of the different systems to your merged record.
Best regards
Michael

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

Problem with childs nodes and automatic key mapping in a Data Object

Hi experts!
I'm doing the service order tutorial from the mobile help at [this link|http://help.sap.com/saphelp_nwmobile71/helpdata/en/21/9b5b924c3b434fba4767731794b029/frameset.htm] and I have a problem...
In the topic "Modeling the Equipment Data Object", says you have to mark the "Automatic Key Mapping" checkbox. So when I had to create a third child node ( the location node ) the system raised an exception with the message "Deselect automatic key mapping flag for more than two-level nodes". I'm trying deselecting the flag and creating the location node, but when I want mark again the automatic key mapping flag, this is disabled.
What can I do to solve this and create the three child nodes with the flag marked? It's a configuration thing?
Any help it's very welcome. Thanks in advance.
Best regards,
Simon.

The thing is: Its not allowed to use automatic keymapping if you have more than two levels. This is why the message showed up, and this is why its been disabled.
What automatic keymapping does: Figures out automatically which child node belongs to which parent (by guessing from the field name and type, which fields in the child correspond to which key fields of the parent).
On three levels, this becomes more complicated => Its disabled.
How to do keymapping yourself instead of having the DOE do it automatically: Do 'Explicit keymapping' from each child to its parent. Explicit keymapping is done by clicking on the corresponding menu button in the child node. Here you need to associate child node fields (they need not be key fields of the child, but they are allowed to be that as well) to each of its parent nodes key fields (so that each child can be associated to its parent).
Cheers

REP-52005: The specified key userlogin does not exist in the key map file.

Hi,
I am using oracle 11g report server. I am getting the error of REP-52005: The specified key userlogin does not exist in the key map file.
I updated the user_string in cgicmd.dat file. My cgicmd.dat file content is below
; OracleAS Reports Services                       ;
; CGICMD.DAT                                      ;
; Example CGICMD.DAT Mapping file                 ;
; Syntax:
;      KEY : VALUE
; Where:
; KEY - the first argument of the rwservlet URL request (case sensitive).
; VALUE - command line parameters and/or special parameters.
; Keys can be referenced in the following ways:
;    1. Parameter on command line to the reports servlet
;          e.g. http://machine/servlet/rwservlet?KEY
;    2. Parameter on command line to a reports jsp
;          e.g. http://machine/mydir/myreport.jsp?KEY
;    3. Within a reports jsp - in the rw:report custom tag
;          e.g. <rw:report parameters="KEY">
; In addition to the Reports Server command line parameters, VALUE can include special parameters
; represented as "%X", where X identifies the parameter. Currently recognized special
; parameters:
; %0 - %9 - 0..9 arguments from original rwservlet URL request. Note that %0 refers to the key itself.
; %* - entire contents (all arguments) of original rwservlet URL request.
; %D - request users to input database userid everytime they run the report.
; %P - request for report parameter form in HTML format. It generates the PARAMFORM=HTML
;       construction on the first submission of the URL and PARAMFORM=NO upon parameter form submission.
; CGICMD.DAT Usage Notes
;   1. Multiple keys in this file MUST be separated by an EXTRA empty line.
;   2. Extra spaces are ignored. Multi-line entries allowed.
;   3. Lines starting with ";" character are treated as a comments.
;   4. Comments within a key or key value are NOT allowed.
;   5. NLS language support is provided and can be used (encoding should match the one
;      used in HTML request - no language conversion of any kind is attempted.
;   6. For %P special parameter, HTML format is by default mapped to the HTMLTABLE format in this release.
;      The HTML format in the future may be mapped to the HTMLCSS format.
;;;;;;;;;;;; Example Key Entries
; Example 1: Run a simple breakb report and output to HTML
orqa: report=breakb.rdf destype=cache desformat=html server=repserver
; Example 2: prompt for userid the first time, then use database userid stored in the cookie subsequently.
report_defaultid: report=breakb.rdf destype=cache desformat=html server=repserver
; Example 3: use %D to require user authentication every time
report_secure: report=breakb.rdf destype=cache desformat=html server=repserver1 %D
; Example 4: Take all arguments from URL and send it to the reports server
run: %*
; Example 5: Run breakb report with HTML parameter form.
breakbparam : report=breakb.rdf destype=cache desformat=html server=repserver userid=scott/tiger@mydb %P
; Example 6: take all URL arguments, and also generate a HTML parameter form
runp: %* %P
; Example 7: Run an Express Report. Replace <MYHOST> with the name of the machine running the Express server. The
; builder on-line help explains the rest of the parameters (the /sl, st etc. etc.)
express: report=my_expr_rep express_server="server=ncacn_ip_tcp:<MYHOST>/sl=1/st=1/ct=0/sv=1/" desformat=htmlcss userid=scott/tiger@mydb destype=cache server=repserver
;;;;;;;;;;;; Keys for Reports Demos
; Using default/in-process server.
; JSPs
;charthyperlink_ias: userid="scott/tiger@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=%DBHOSTNAME%)(PORT=%DBPORT%))(CONNECT_DATA=(SID=%DBSID%)))" %*
;charthyperlink_ids: userid=scott/tiger@ %*
;barcodeweb:         userid=oe
;parmformjsp:        userid=oe
;tutorial:           userid=oe
; Paper Reports
;xmldata:            userid=oe report=inventory_report.rdf destype=cache p_filelocation="http://%HOSTNAME%:%OC4JPORT%/reports/examples/xml_pds/scripts/" desformat=pdf
;barcodepaper:       userid=oe report=shippingmanifest.rdf destype=cache desformat=pdf
;distributionpaper: userid=oe report=inventory_report_dist.rdf distribute=yes destination=exampledistribution.xml
;pdfenhancements:    userid=oe report=utf8test.rdf destype=cache desformat=pdf
userlogin : userid=SYMFINBTOTEST@fin10r21 %*
As in the above file i have added a key as userlogin at the end of the file. But the reports server does not take the key that i have given. I followed the same steps provided in oracle docs. I used "showmap" to check the cgicmd file that is used by the reports
http://aspirevm8-17.aspiresys.com:9002/reports/rwservlet/showmap?server=bluQubeReportsAtLocalEnv&destype&userid=SYMFINBT…
It shows me the content of the cgicmd.dat file and it also shows my updations. But in the "Parsed Map File Entries" it does not show my key value pair
Parsed Map File Entries
Return to Top
Key Name
Value
runp
%* %P
breakbparam
report=breakb.rdf destype=cache desformat=html server=repserver userid=scott@mydb %P
report_defaultid
report=breakb.rdf destype=cache desformat=html server=repserver
run
report_secure
report=breakb.rdf destype=cache desformat=html server=repserver %D
express
report=my_expr_rep express_server="server=ncacn_ip_tcp:<MYHOST>/sl=1/st=1/ct=0/sv=1/" desformat=htmlcss userid=scott@mydb destype=cache server=repserver
orqa
report=breakb.rdf destype=cache desformat=html server=repserver
Please help me to to make the key being populated here and being used by the reports server.
Thanks,
Priya

uncomment #KEYPMAPFILE=CGICMD.DAT. remove the #
then for development set
reloadkeymap=yes (same file - rwservlet.properties).
Now it should reload everytime. (otherwise for every change u need to restart oc4j_bi_forms)
(For * production* may be you want to set reloadkeymap=no once all testing is done)
see cgicmd.dat for many examples of using keymap file
[ All Docs for all versions ]
http://otn.oracle.com/documentation/reports.html
[ Publishing reports to web - 10G ]
http://download.oracle.com/docs/html/B10314_01/toc.htm (html)
http://download.oracle.com/docs/pdf/B10314_01.pdf (pdf)
[ Building reports - 10G ]
http://download.oracle.com/docs/pdf/B10602_01.pdf (pdf)
http://download.oracle.com/docs/html/B10602_01/toc.htm (html)
[ Forms Reports Integration whitepaper 9i/10g ]
9i - http://otn.oracle.com/products/forms/pdf/frm9isrw9i.pdf
10g - http://www.oracle.com/technology/products/forms/pdf/10g/frm10gsrw10g.pdf
http://www.oracle.com/technology/products/forms/techlisting10g.html
---------------------------------------------------------------------------------

Can Key Mapping details be available as a serach parameter in MDM DM?

Hello Experts,
Is there any way that we can display or search certain Records in Data Manager/Portal based on the Key Mapping details (Remote System/Key Value assigned for any remote system).
The scenario where I am trying to apply this is:
I have say lacs of records in MDM and i have merged certain records into a new record (Record1) and assigned key mappings to this record1 to point to System1 and System2.
System1 has the key value as ABC and System2 has value set as DEF. If any user wants to now find the merged record based on the key value of system2 (i.e DEF), how will he proceed?
Kindly advice.
Thanks and Regrads,
Elizabeth.

Hi Elizabeth,
In MDM Data Manager, once the record is merged you can see only one record in place of all merged records.
In your case ABC from system1 and DEF from system2 are merged into ABC.
So in data manager you can just search the record based on ABC but not DEF.
However, if you select the record ABC and right click and select Edit key mappings, then you will see both the records and its respective system.
So the work around is using syndicator, send the records in excel sheet or CSV file where you can send both the merged records with merged values.
The users can make a search in that CSV file with DEF as well.
Regards,
Sravan

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

Key mapping from vt100 to vt220

Similar Messages

Maybe you are looking for