Prevent Duplicate Entry With DQM Match Rule For Email Attribute Not Working For Organization
Last updated on JANUARY 03, 2018
Applies to:Oracle Trading Community - Version 12.1.3 and later
Information in this document applies to any platform.
We have created a DQM matching rule for organizations with attribute Email (hz_contact_points.email)
We expected to receive the warning message that duplicate email exists when user is entering an email address with the same for another organization.
This does not work and end-user can create duplicates without any warning.
But DQM does warn of duplicate when using match rule for person party type.
The application is generating a warning when entering a duplicate Email.
The data is seen in
604401 EMAIL A
Also seen in the hz_staged_contact_points table under tx columns
select party_id, contact_point_id, contact_point_type, tx5, tx6, tx12 from hz_staged_contact_points where contact_point_id = 604401
585190 604401 EMAIL firstname.lastname@example.org INF ABST ES A
Does not kick in when using duplicate exact email address
To reproduce issue
Create a single match rule with just the email address attribute
with match threshold of 100 and exact.
Works for only creation of a party type person - just not an
STEPS TO REPRODUCE
Create a new match rule for duplicate prevention on email field.
Match Rule Name - EMAIL_DUP_FOR_ORG
Used only Party Name and e-mail address attributes.
Name (PARTY_NAME) Party Acquisition and Scoring 30
E-Mail Address (EMAIL_ADDRESS) Contact Point Acquisition and Scoring 30
Match threshold is low 30 set
Assigned EMAIL_DUP_FOR_ORG match rule to profile HZ: Match Rule for
Organization Duplicate Prevention at the Responsibility level
Create a Organization that has a duplicate email address already existing in the TCA Registry
A warning is not generated that email already exists.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms