Last updated on MARCH 02, 2017
Applies to:Siebel Data Quality Matching - Version 18.104.22.168 SIA  and later
Siebel Data Quality - Version 22.214.171.124 SIA  and later
Siebel CRM - Version 126.96.36.199  and later
Siebel Universal Customer Master - Version 188.8.131.52 SIA  and later
Information in this document applies to any platform.
An external application called the createOrganization operation on the OrganizationService web service to insert an account. It called it again to insert another account with a similar name. The second account was not identified as a match of the first account as expected and, therefore, it was not used to update the first account in the base tables.
The following detailed behavior was observed in Universal Customer Master (UCM):
Call 1 - Create an account "Oracle US" using SoapUI and calling createOrganization operation of OrganizationService.
Call 2 - Create an account "Oracle USA" using SoapUI and calling createOrganization operation of OrganizationService.
Actual Result -
1. Account>Account List did not show Oracle US or Oracle USA.
2. Transaction History Table contained both these records and Record Type was "Source" for both.
Expected Behavior -
1. Account > Account List should have shown Oracle US since it being the prior record (Oracle US) should have survived using Account Default Role of "History".
2. Transaction History table should have contained both the records but one record (Oracle US) should have record Type as "Source" and other record (Oracle USA) should be "History".
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