Multiple Fields Matching Rules

[former_member202443]

Hi Guys,

I have a problem. I like to match records depending upon multiple fields matching rules. Let's have an example. I have record consisting several fields like Customer Name, Address, Email, Telephone I like to see if all these fields values are same in two or several records.

What I currently have is that I have made several Matching Rules and used them in one Matching but it shows me many duplicate records. Eventhough, they are not completely duplicate. What the Matching Strategy does is that if any of Matching Rules used in it is duplidate it shows me as duplicate record.

But I like see duplicatation if all above mentioned fields are duplicated.

Any recommendation???

Regards,

Naeem

[Former Member · Accepted solution]

Hi Naeem,

You need to select All the matching fields in your Rule and take the combination of those fields when using them in your Strategy.

Include all the Rules combination in your Strategy to get the desired result.

You can refer the below link which explains Matching in MDM:

Hope It Helped

Thanks & Regards

Simona Pinto

[Former Member · Accepted solution]

Hi Naeem,

You need not create rule for each and every field.You can select the required fields while

defining the rule.You can create one rule,select all the fields you want to match,assign this rule

to a strategy and perform matching over this strategy.If all the fields are matching,it will give you

a success score.If none of the fields are matching,it will give you a failure score.If some fields are matching,it will give you the score based on the no. of fields matching.Based on this you can find the

potential duplicates.

Thanks and Regards,

Preethi

[former_member202443 · Accepted solution]

Thanks Prethy,

It's working.

Can you recommend me some thing like Strengths and Weaknesses of SAP MDM??? I like to know also the weaknesses like as above I have discussed Soundex function in it.

Regards,

Naeem

[Former Member · Accepted solution]

Hi Naeem,

In SP5 and SP6 versions,we can have only on main table.So for the entitites like

Vendor,Material,Business Partners etc we need to have individual repositories

because we need to store these entites in the main table.So if they share a common

lookup table for eg. Countries we need to maintain them individually for each repository

which is repetitive.Wherein 7.1 we have the option of maintaining multiple main tables

and can have one common lookup table,where each main table can lookup into the same

table.

Please mark this thread answered if your question is answered.

Thanks and Regards,

Preethi

[former_member202443 · Accepted solution]

Hi Prethy,

ya that's true. I have also seen Release Notes of 7.1. Its a good document which let us show weakness of earlier versions while they have improved it.

As in 7.1, repositories may have several main tables. Is it is also possible to make them in relation like in RDBMS. Is there any tool in Console which shows the logical diagram of the Repository, if several main tables can be in relation.

Regards,

Naeem

[Former Member · Accepted solution]

Hi Naeem,

Yes, we can relate the main tables as well.There is a field type called Lookup(Main)

so that we can look up into other main tables also like Hierarchy and Taxonomy tables.

I dont think we can see the relationships between tables in the form of logical diagram

in the console.

Thanks and Regards,

Preethi

[Former Member]

Hi Again

Try combining the fields you mentioned Customer Name, Address, Email, Telephone while writing a rule and use token as Search functionality. Select all these fields using Ctrl and Add, this will combine the fields for performing the match. It will meet your requirement.

Best regards

Ravi