Our sales team is creating duplicate opportunities in SAP CX Opportunity Management despite having duplicate detection enabled. We’re seeing multiple opportunity records for the same customer account with identical product configurations and similar deal values. The duplicate detection rules were configured to check account name, opportunity amount (within 10% variance), and expected close date (within 30 days), but the system isn’t flagging these obvious duplicates during opportunity creation. This is causing inflated pipeline reports and confusion about which opportunity record is the active one. The fuzzy matching configuration seems to be set too strictly, and our batch deduplication process hasn’t been run in months. How can we tune the duplicate detection to catch these cases without generating too many false positives?
Check your duplicate detection rule threshold settings in Data Governance Configuration. If the matching score threshold is set too high (like 95%), it will only flag exact duplicates and miss near-matches. Try lowering it to 75-80% to catch similar opportunities. Also verify that the rule is actually active and assigned to the Opportunity object.
For active opportunity pipelines, run batch deduplication weekly during off-peak hours. Monthly runs leave too much time for duplicates to accumulate and cause reporting issues. Schedule it for Saturday nights when user activity is minimal. The job can take 2-4 hours depending on your opportunity volume, so plan accordingly. Make sure to back up your data before the first run.
That’s helpful. I’m now looking at the batch deduplication process. Our last run was in August, which explains why existing duplicates haven’t been merged. What’s the recommended frequency for running batch deduplication jobs in Opportunity Management?