Consolidation/Syndication

[Former Member]

I have consolidated data from Legacy1 and Legacy2 Systems.

Legacy1 had SKU1, SKU2 and SKU3.

Legacy2 had SKU4, SKU5, and SKU6.

Now in MDM Client, I have 6 records.

Now I change SKU2 and SKU5 in MDM.

When I syndicate the change records to Legacy1, I should syndicate only SKU2 which already exists in Legacy1 system.

Similarly, syndication to Legacy2 system should include only SKU5.

How can I achive this?

I should be able to syndicate records to several systems which are relevant in those systems.

I do NOT want to select manually in a mask.

Any thoughts on this?

[Former Member · Accepted solution]

Hi Adhappan:

For this, you should have the KEY MAPPING parameter set to ON in the main table properties of your MDM repository.

Once you have properly defined the client systems Legacy1 and Legacy2 in the ADMIN branch of your repository in the MDM CONSOLE, just make sure you have properly set the KEY MAPPINGS for every record in the data manager. (Right-button click on the record, key mappings).

Then, when you sindicate, do it only for the desired client system.

That will to the magic.

Hope this helps.

Best regards,

Jorge.

[Former Member · Accepted solution]

Thanks Subbu and Jorge.

What if I create a new record in MDM using MDM Client.

Let us assume for the first time, I syndicate this record to Legacy System1 only using mask technique.

Later, I make changes to this record.

How can I syndicate this record together with SKU2(with key mapping) to Legacy1 system.

By selecting suppress records without key mapping will leave out the new record which was syndicated earlier.

Am I making sense?

[Former Member · Accepted solution]

Exactly Adhappan, you need to use the "supress records without a key" in MDM syndicator for the key mapping thing to work.

If you create a new record in the MDM data manager, you can also create there it's key mapping as I explained in my previous post.

Best regards,

Jorge.

[Former Member · Accepted solution]

I will try to put it simpler:

Activate "supress records without a key" and also "supress records without changes".

This way, only new or changed records which have a key mapping belonging to the selected client system will be syndicated.

If you later change a record it will be syndicated again for all client systems in it's key mapping.

If you add a new client system to a record in it's key mapping, it will only be syndicated for this new client system.

Hope I made my self clear.

[Former Member]

Hi,

This can achieved using the Key Mapping concept in MDM.

Steps:

For the Main table in the repository you are using set the "Key Mapping" property to Yes.

1. Define 2 Client Systems in MDM Console,

(Legacy1,Legacy2)

2. Import data using Import Manager using the Client System as Legacy1

and repeat the import data process using Client System as Legacy 2.

3. As you said you will 6 records.

4. In syndicator use Legacy1 as Client system and excute the syndication.

Make sure in the "MAP Properties" tab, look for supress records with out key is checked.

In this scenario only the records which has the Legacy1 system as the Client system will be syndicated.

Hope this helps.

Let me know if you need any additional information.

Thanks and Regards

Subbu