key mapping/ remote key

[Former Member]

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

[Former Member · Accepted solution]

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

[Former Member · Accepted solution]

hi sudhanshu,

thanks for the quick reply.

I still have a doubt,

if I create 12 new product master records in MDM and

I want to syndicate 3 records to R1, since it falls under R1 system

4 records to R2, since it falls under R2 system

5 records to R3.

so should i make the main tabe as remote key enabled with my product id as the remote key?

2.

remote system <->

Value <->

division <-> div

desc <-> desc

what should i map these two fields(remote system, Value), I dont have anything else in the target.

also let me know where this option is "override remote keys".

thanks,

ve

[Former Member · Accepted solution]

Hi Veena,

so should i make the main tabe as remote key enabled with my product id as the remote key?

Yes you have to make the main table as remote key enabled with Producid as remote key and

to Product table which records assign to remote system and remote key will syndicate your records accordingly to R1,R2,R3 System

what should i map these two fields(remote system, Value), I dont have anything else in the target.

also let me know where this option is "override remote keys".

You need to map Value, and "override remote keys" option is available in MDM synidcation under Map Properties tab ---> Remote Key Override

Thanks,

Jignesh Patel

Edited by: jignesh patel on Sep 16, 2010 11:02 AM

[Former Member · Accepted solution]

Hi,

so should i make the main tabe as remote key enabled with my product id as the remote key?

Yes you have to make maintable remote key enabled.If your productid is unique then you can make it ask remote key.

remote system <->

Value <->

division <-> div

desc <-> desc

what should i map these two fields(remote system, Value), I dont have anything else in the target.

also let me know where this option is "override remote keys".

You have to create these two fields in your xsd to map these two fields.

You can find override remote keys property under the map properties tab..

You can also check on page 27 under this PPT

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0f6bd20-b864-2d10-e2b2-f7e6a713f...

Thanks,

Sudhanshu

Edited by: Sudhanshu Agarwal on Sep 16, 2010 4:22 PM

[Former Member · Accepted solution]

Hi Veena,

I want to syndicate 3 records to R1, since it falls under R1 system

4 records to R2, since it falls under R2 system

5 records to R3.

so should i make the main tabe as remote key enabled with my product id as the remote key?

I think in the above case, you need to create 3 syndication maps . Before that records should have remotesystem and remote

key maintained in data manager.In the 1st syndicaton map, you just select remotesystem(R1) and choose option suppress records without key under map properties. So only records which are related to R1 will be syndicated to R1.

and in the 2nd map, select remote system(R2) and choose option suppress records without key under map properties.So only

records which are related to R2 will be syndicated to R2. The same thing will be applicable to R3 remote system too.

I hope it will work . Let us see for some more answers from MDM experts.

Thanks,

Narendra