Data Quality Management (DQM) Issue: Duplicate Prevention Not Working With Custom Attribute (Doc ID 1348468.1)

Last updated on NOVEMBER 07, 2019

Applies to:

Symptoms

In R12.0.6, duplicate prevention with DQM match rule using a custom attribute, e.g. 'Tax Registration Number' is not working.  Duplicate 'Tax Registration Number' can still be assigned to different customers.

Steps to reproduce:

1) Create a DQM match rule using a custom attribute = 'Tax Registration Number'
Responsibility: Trading Community Manager
Navigation: Administration > Match Rule

-Click on Create Single Match Rule
  Name = XXXHZ_ORG_DUPLICATE_ONLINE
  Search Operator = Match All
  Match Threshold = 100
  Attribute Name = Tax Registration Num (TAX_REFERENCE), Usage = Acquisition
  and Scoring, Score = 100
  Transformation = EXACT SPECIAL, Weight = 100, Adjust Score = 100, Use in Acquisition = Yes, Use in Scoring = Yes
-Click on 'Save and Compile' button.

2) Set the profile options:
Responsibility: System Administrator
Navigation: Profile > System

-HZ: Match Rule for Organization Duplicate Prevention = XXXHZ_ORG_DUPLICATE_ONLINE
-HZ: Match Rule for Person Duplicate Prevention = XXXHZ_ORG_DUPLICATE_ONLINE

3) Enter Duplicate Tax Numbers for different customer records

Responsibility: Customers Online Superuser
Navigation: Customers > Organizations subtab
-Query for a customer.
-Click on Update icon
-Under Tax and Financial Information region, enter the Tax Registration Number = 987654321.
-Save. Receive confirmation saying "The value has been updated."
-Query for another customer.
-Enter the same Tax Registration Number = 987654321
-Save. Receive confirmation saying "The value has been updated."

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.