![]() |
|
![]() |
|
About the Synchronization Engine and Field MappingThis topic describes how the Synchronization Engine identifies matching records and explains the field mapping required when performing a synchronization. Identifying Matching RecordsWhen you run the initial synchronization between Oracle CRM On Demand and your PIM application, the Synchronization Engine reviews certain key fields to match records in your PIM application and Oracle CRM On Demand. When you add new contacts or update the account name of an existing contact, Oracle PIM Sync On Demand (the PIM Sync client) executes fuzzy matching on the account and contact names, which is enabled by default when Oracle CRM On Demand is first set up for a new company. The PIM Sync client ignores differences in punctuation and capitalization when determining matches. For more information on fuzzy matching, see Synchronizing with PIMs. The following rules are used to determine if two names are the same:
For example, if you have John Smith as a contact in Microsoft Outlook and JOHN SMITH as a contact in Oracle CRM On Demand, the Synchronization Engine treats them as one record. In addition, the Synchronization Engine treats the following variations of a specific account name (linked to contacts) as matches, and therefore the same record: TYC, T.Y.C, tyc. CAUTION: If you use Oracle PIM Sync On Demand when the following Company Profile settings are set in Oracle CRM On Demand (that is, when fuzzy matching is disabled), then the PIM Sync client does not ignore differences in punctuation and capitalization when determining matches and, as a result, any records that are not identical are duplicated: - Disable PIM Sync Extended Account Association - Disable PIM Sync Account Association The following table shows which fields are the key fields for synchronization, which fields are required, and how the fields are mapped between Oracle CRM On Demand and Outlook or Lotus Notes. Field mappings are fixed and cannot be changed. Those fields that are not listed here are not mapped; the information is not retrieved from any of the applications.
NOTE: If the required fields are not filled, the record is not created during synchronization, and this information is recorded in the log file. |
| Published 7/18/2011 | Copyright © 2005, 2011, Oracle. All rights reserved. Legal Notices. |