Data Sync Considerations and Recommendations

This section lists several items that should be considered during implementation of the data sync process.

Data	Considerations and Recommendations
Contact Types	In your Oracle Utilities system, each contact type refers to a routing type that has delivered base values, but each implementation can add more configured values. Only one primary contact point record is allowed for each routing type. Synchronizing a list of multiple instances of the same communication type (such as multiple home phone numbers) is enabled because the integration synchronizes a cross-reference of the unique contact communication point record identifiers in each system. Recommendation: Implementation teams should use the same configured values for communication types in both systems where possible so that no further value mapping is needed. However, if different values must be configured, mappings within the CX Industry Framework Utility Configurations can be used to configure the integration. For additional information, see Manage Integration Configurations.
Characteristics and Extension Attributes	Oracle Utilities customer information systems support configuration of characteristic types to store additional data on person objects. For additional information, refer to Defining Characteristic Types in the Customer Cloud Service Administrative Guide, available in the Oracle Utilities Customer Cloud Service library. If these values need to be synchronized to Contacts or Accounts in Fusion, determine the mapping to explicit fields in the Fusion application schemas. For additional information on extensions, refer to the Configuring and Extending Fusion Cloud Applications in the Oracle Help Center. Recommendation: Set the Utility Configuration to map the Characteristic Type as the “cssValue” and the Fusion application field as "faValue" for each pair of attributes that should be included in the data synchronization. For example: "ccsValue": "C2MBTHDT", "faValue": "DateOfBirth" or "ccsValue": "C1-NICK", "faValue": "NickName" For additional information, see Manage Integration Configurations.
Primary IDs and Personally Identifiable Information (PII)	Oracle Utilities customer information systems support multiple types of identification that can be used to identify a customer. Typically, at least one of some group of fields must be provided to verify the customer identity. For example, in the United States: Federal Social Security Number, state driver's license number, or passport number for an individual. Federal Employer Identification Number for a business. Each type of identification, and the rules regarding which fields are required for verification, are configured by the utility during installation. Recommendation: Sensitive data can be retained only in Customer Cloud Service and typically would not need to be stored in the Oracle CX Sales or Oracle Fusion Service systems. If this sensitive information is required in multiple systems, the data synchronization can be extended by your implementation to include customer identifiers with appropriate security controls. Optionally, Oracle Fusion Enterprise Data Quality can be implemented with the Oracle Fusion applications to identify duplicate records where matching rules are configurable. Warnings can be issued based on a match score (using name, communication points, and other information beyond identifiers), which allows for selecting an existing party instead of creating a duplicate. See Appendix A: Data Mapping for detailed synchronization message mapping information for this integration.