Match Rule Configuration Example

Back Next

Match Rule Configuration Scenario

Your organization has customer information stored in the Party base object and other related base objects. The Party base object contains duplicate records for many customers. You want to configure match rules that can identify and queue up duplicate records for merge.

The Party base object contains duplicate customer records that might have the first name and the last name missing, or with incorrect or inconsistent entries. The Display Name column has values for each record. The records are categorized as a Person or an Organization party type. The addresses of the customers are stored in the related Address base object. The Party Address Rel relationship base object defines the relationship between the records in the Party and the Address base objects.

You want to create match rules to match duplicate customer records that have the Person party type in the Party base object. Records with the Person party type belong to individuals. You can perform the match based on names and addresses stored in the Party and Address base objects.

To match duplicate records, you need to create an automerge match rule for records that are sufficiently similar and can be queued for automerge. Also, you need to create a manual merge match rule for records that are possible duplicates, but need to be reviewed by a data steward before the merge process.

The Party base object shows important columns and sample records.

Rowid Object	First Name	Last Name	Organization Name	Display Name	Party Type
1019	NULL	NULL	NULL	WILL R DE HAAN	Person
1072	NULL	NULL	NULL	AHMED RAUF	Person
1106	RACHEL	ARSEN	NULL	RACHEL ARSEN	Person
1154	RACHEL	ARSEN	NULL	RACHEL ARSEN	Person
1191	WILLIAM	DE HAAN	NULL	WILLIAM DE HAAN	Person
1419	BILL	DE HAAN	NULL	BILL ROGER DE HAAN	Person
1475	NULL	NULL	RYERSON AREA	RYERSON AREA MED CTR	Organization
1642	AHMED	RAUF	NULL	AHMED RAUF	Person
1800	NULL	NULL	NULL	RYERSON AREA MED CTR	Organization

The Address base object shows important columns and sample records.

Rowid Object	Address Line1	Address Line2	City Name	State Cd	Postal Cd
920	69 BUTLER ST	NULL	ATLANTA	NULL	30303
991	7610 ROSENWALD LN	NULL	NOKESVILLE	NULL	20181
1221	RR 1 BOX 4	NULL	SUGAR RUN	NULL	18846-9701
1279	RR 1 BOX 3	NULL	SUGAR RUN	NULL	18846-9701
1711	69 JESSE HILL JR DR SE	NULL	ATLANTA	NULL	30303-3033
1860	5493 S QUEENS RD	NULL	ROCHELLE	NULL	61068
1909	5193 S QUEENS RD	NULL	ROCHELLE	NULL	61068
1960	669 BUTLER ST SE	NULL	ATLANTA	NULL	30303-3033
2005	7601 ROSENWALD LN	NULL	NOKESVILLE	NULL	20181

The LU Address Type lookup base object shows important columns and sample address type lookups.

Rowid Object	Address Type	Address Type Disp	Address Type Desc
1	BILL	BILLING	BILLING
4	LGL	LEGAL	LEGAL
10	RSID	RESIDENCE	RESIDENCE
11	SHIP	SHIPPING	SHIPPING

The Party Address Rel relationship base object shows important columns and sample records.

Rowid Object	Party ID	Address ID	Address Type	Status CD
976	1019	920	BILL	NULL
1051	1072	991	BILL	NULL
1080	1191	1960	LGL	NULL
1100	1419	1711	BILL	NULL
2001	1154	1909	LGL	NULL
2002	1106	1860	LGL	NULL
2004	1642	2005	LGL	NULL
2049	1475	1279	LGL	NULL
2050	1800	1221	LGL	NULL

Rename Saved Search

Table of Contents

Match Rule Configuration Example

Match Rule Configuration Example

Match Rule Configuration Scenario

Match Rule Configuration Scenario