Data Quality Guide for Oracle Customer Hub > Configuring Data Quality with Oracle Enterprise Data Quality >

Data Format for Deduplication of Multiple Child Entities

To enhance the functionality of Siebel Universal Connector and a third party external key generating vendor, the Siebel Universal Connector API supports hierarchical data format. For example, instead of making multiple calls to the third party vendor for multiple address deduplication, the hierarchical data format sends all child addresses in one payload, thus enabling the connector to make just one call.

The following example shows the data format with the ListOf container used for each child entity.

Note the following:

• The Name field is derived from the parent business component.
• The ListOf container is used for the Address child object.
• The Street field is a join field derived from the child business component.

<Data>
<DriverRecord>
<Name>...</Name>
...
<ListOfAddress>
<Address>
<Street>...</Street>
...
</Address1>
<Address2>
<Street>...</Street>
...
</Address2>
...
<AddressN>
<Street>...</Street>
...
</AddressN>
</ListOfAddress>
</DriverRecord>
<CandidateRecord>
</CandidateRecord>
</Data>

The following example shows the data format for the Contact object.

<Data>
<DriverRecord>
<Contact.Id>12-12ABC1</Contact.Id>
<FirstName>abc</FirstName>
<LastName>abc</LastName>
<ListOfAccount>
<Account>
<Name>A. K. Parker Inc</Name>
<Location>San Mateo</Location>
</Account>
<Account>
<Name>Hibbing Manufacturing</Name>
<Location>San Jose</Location>
</Account>
</ListOfAccount>
<ListOfPersonalAddress>
<PersonalAddress>
<City>York1</City>
<Country>USA</Country>
<Zip>78201</Zip>
<State>AL</State>
<Street> 1200 Davisville Road</Street>
</PersonalAddress>
</ListOfPersonalAddress>
</DriverRecord>
<CandidateRecord>
<Contact.Id>12-BCDD</Contact.Id>
<FirstName>abc1</FirstName>
<LastName>abc1</LastName>
<ListOfAccount>
<Account>
<Name>A. K. Parker Inc</Name>
<Location>San Mateo</Location>
</Account>
</ListOfAccount>
<ListOfPersonalAddress>
<PersonalAddress>
<City>York1</City>
<Country>USA</Country>
<Zip>78201</Zip>
<State>AL</State>
<Street> 1200 Davisville Road</Street>
</PersonalAddress>
</ListOfPersonalAddress>
</CandidateRecord>
<CandidateRecord>
<Contact.Id>12-BCEE</Contact.Id>
<FirstName>abc2</FirstName>
<LastName>abc2</LastName>
<ListOfAccount>
</ListOfAccount>
<ListOfPersonalAddress>
<PersonalAddress>
<City>York3</City>
<Country>USA</Country>
<Zip>78203</Zip>
<State>AL</State>
<Street> 1203 Davisville Road</Street>
</PersonalAddress>
</ListOfPersonalAddress>
</CandidateRecord>
</Data>

The following example shows the data format for the Account object.

<Data>
<DriverRecord>
<Account.Id>12-ABCC</Account.Id>
<Name>Hibbing Manufacturing</Name>
<Location>San Jose</Location>
<ListOfCUTAddress>
<CUTAddress>
<City>York1</City>
<Country>USA</Country>
<Zip>78201</Zip>
<State>AL</State>
<Street> 1200 Davisville Road</Street>
</CUTAddress>
</ListOfCUTAddress>
</DriverRecord>
<CandidateRecord>
<Account.Id>12-AAAA</Account.Id>
<Name>Hibbing Manufacturing1</Name>
<Location>San Jose</Location>
<ListOfCUTAddress>
<CUTAddress>
<City>York1</City>
<Country>USA</Country>
<Zip>78201</Zip>
<State>AL</State>
<Street> 1200 Davisville Road</Street>
</CUTAddress>
<CUTAddress>
<City>York2</City>
<Country>USA</Country>
<Zip>78202</Zip>
<State>AL</State>
<Street> 1201 Davisville Road</Street>
</CUTAddress>
</ListOfCUTAddress>
</CandidateRecord>
<CandidateRecord>
<Account.Id>12-BBBB</Account.Id>
<Name>Hibbing Manufacturing2</Name>
<Location>San Francisco</Location>
</CandidateRecord>
<CandidateRecord>
<Account.Id>12-CCCC</Account.Id>
<Name>Hibbing Manufacturing3</Name>
<Location>San Mateo</Location>
<ListOfCUTAddress>
<CUTAddress>
<City>York1</City>
<Country>USA</Country>
<Zip>78201</Zip>
<State>AL</State>
<Street> 1200 Davisville Road</Street>
</CUTAddress>
</ListOfCUTAddress>
</CandidateRecord>
</Data>