SWIMergeServices When used to Merge Parent Contact and Child Opportunity, merge not re-parenting opportunities
(Doc ID 2375608.1)
Last updated on NOVEMBER 06, 2019
Applies to:Siebel CRM - Version 16.8 [IP2016] and later
Information in this document applies to any platform.
When merging contacts using Vanilla Business Service “SWI Merge Services”. It is observed that post merge opportunities are not getting re-parented, PR_CON_ID in S_OPTY tables is getting update with survivor/ winning contact id but S_OPTY_CON records left untouched with victim/loosing contact id. This is causing issues where in opportunity is not visible in contacts view as the link between Contact and Opportunity uses S_OPTY_CON table.
1. Select two contacts and added Opportunities to these contact.
2. Two Kinds of Test
a) First test was in the UI. In the UCM > Existing Duplicates > Duplicate contact I did a Merge and found that the records are getting merged and I see all the opportunities under the Survivor Contact record.
b) Second Test was in the SOAPUI. I sent following request. I made sure both Survivor Contact and Victim Contact has opportunity records. Run the SOAPUI request and checked in the UI that under the Survivor contact records also showing the victim contact's opportunities.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:asi="http://siebel.com/asi/" xmlns:swim="http://www.siebel.com/xml/SWIMergeObjectIO">
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document