cancel
Showing results for 
Search instead for 
Did you mean: 

Key Mapping Information

Former Member
0 Kudos

Hello All

We have a case where we would like to move a selected set of materials from repository 1 to another repository 2 and still maintain the Key Mapping information that those materials have from the original Import into repository.

Any suggestion?

all help greatly appreciated

C

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

C,

Load the repository1 in Console and log into Data Manager. Download (import) the materials (to be moved to repository2) into your local pc as an excel file. Unload the repository1 in Console and load repository2. Log into the Data Manager and export (upload) the excel sheet.

Hope it resolves your problem.

Thanks,

Satyanarayana.

Former Member
0 Kudos

Hey

We have considered this, but would like to have a more Automated (or at least semi-automated process).

Rgs

Con

michael_theis
Active Contributor
0 Kudos

Hi Con,

did you consider using Syndicator and Import Manager (or MDSS and MDIS)?! You could create a Syndication map with target system equal to the one you want to keep the key mapping. This would syndicate the full record including the key mapping information. With manual syndication you could put the file directly in the import folder, automatic syndication would need a mechanism (maybe a simple batch job?!) copying the file from outbound to import folder.

BR Michael

Former Member
0 Kudos

You can do this with the Syndication Server, but you will not be able to get the "default" flag. If you write a program with the JAVA api, you could snag all of the key mappings and move them across.

Former Member
0 Kudos

Hello Michael,

The problem we see with this is that want to Migrate data from the first MDM Rep to the Second Rep by Product Category is possible and not by Remote system.

Any suggestions?

Con

Former Member
0 Kudos

Hi Con,

The migration works fine for Product category wise from one repository to other repository but the Remote system information is not updating properly - correct me if am wrong.

<u>Possible place of corrections :</u>

1. Make sure the second repository's Key mapping property made YES > can be found at console>Repository-->Key mapping

please feel free to revert to me if things are not working.

thanks

Alexander

P.S.Kindly reward the points if found problem solved.

Former Member
0 Kudos

Yes., That is correct.

Our bbjective is to take a category, lets say "Caustic Soda" and migrate it to a new repository.This category contains materials form multiple remote systems and we are looking for the most effective way to migrate and maintain then correct key mapping details.

Thanking you in advance

Con

michael_theis
Active Contributor
0 Kudos

Hi Con,

I just want to summarize if I understood you right: you have a category that has some products. You want to migrate both into a second repository. Migration of the category is working but the key mapping information is lost or incomplete?!

How do your products look like? Do they have multiple key mapping entries? The syndicator would be able to distribute multiple key mappings (you can add multiple target systems in the destination properties of your map). But Import Manager is currently able to import only one key mapping records for a single remote system during an import run. This would mean that you have to syndicate your products for each remote systems and you have to do the same amount of imports.

BR Michael

Answers (0)