Person Data Sync Configurations

The table below provides the business configurations available for attributes that can be mapped for the Fusion Contact (individual) or Account (business) synchronization to Persons in the Oracle Utilities system.

Person Data Sync Configurations for communicationType include new fields, iconClass, contactPointPurposeField and contactPointValueField, that require mapping. The iconClass refers to class of the icon that can be used in the interface for the communication type. The contactPointPurposeField and contactPointValueField both map to the Fusion application API field for the associated communication type, and are used to retrieve the corresponding contact purpose data and contact point value.

Person Data Configuration Comment

Name: IdentifierType

Description: Holds the mapping of lookup values for customer legal entity identifier types.

Example:

"ccsValue": "DL NUMBER", "faValue: "DRIVER_LICENSE", "isPrimary": false

 This mapping is not currently used by the delivered data synchronization flows but is available as a sample and for possible future support within the solution.

Name: communicationType

Description: Holds the mapping of lookup values for COMMUNICATION_TYPE.

Example:

"ccsValue": "FAX", "faValue": "TLX"

"iconClass": "oj-ux-ico-laptop", "contactPointPurposeField": "WebPurpose",

 This list of values is fixed in Fusion applications and configurable in Oracle Utilities systems, where it is referred to as a routing type. If the values in Oracle Utilities are different than the fixed values in Fusion, you can map the corresponding values. If there is no entry, the values will be passed through unchanged.

Name: PHONE_purpose

Description: Holds the mapping of lookup values for the CONTACT_PURPOSE type.

Example:

"ccsValue": "WORKPHONE", "faValue": "WORK"

"ccsValue": "FAXPHONE", "faValue": "FAX"

This refers to the contact purpose specific to the PHONE contact type. You might not have the same contact purpose names configured in both systems.

Be aware that in Oracle Utilities systems, FAX is a contact routing type that needs at least one value set as the primary value. In Fusion applications, FAX is a purpose field under Communication Type = Phone. The Communication Type needs at least one primary value in Fusion applications as well.

To handle this mismatch, set up Fax as a custom communication method in your Oracle Utilities system to mimic the Fusion application setup so the sync will be successful. If you have different contact purpose names configured in Fusion applications and your Oracle Utilities system, update the mapping between Fusion applications and your Oracle Utilities system purpose name, and store it under the PHONE_purpose configuration in utilityConfigurations API, as FAX is considered to be a type of phone number.

Additionally, be aware of the following:

  • Any extension on phone Type should be added under Phone Type in the Utility Configuration.
  • The lookup ORA_HZ_PHONE_TYPE provides the list of supported values that are delivered with the system. To add custom phone types, refer to Overview of Lookups
  • It is recommended to retain the LAND phone type in the Utility Configuration, and ensure a corresponding mapping is created in your CIS. This is needed because if no phone type is explicitly provided, Fusion defaults to LAND. To ensure this defaulted data syncs to your CIS without issues, the LAND type must be recognized and mapped appropriately. For example:
    {
            "name": "PHONE_Purpose",
            "description": "Holds the lookup values for CONTACT_PURPOSE type",
            "configurations": [
                {
                    "ccsValue": "CELLPHONE",
                    "faValue": "MOBILE" // Phone Type
                },
                {
                    "ccsValue": "HOMEPHONE",
                    "faValue": "HOME"
                },
                {
                    "ccsValue": "WORKPHONE",
                    "faValue": "WORK"
                },
                {
                    "ccsValue": "FAXPHONE",
                    "faValue": "FAX"
                },
                {
                    "ccsValue": "LANDLINE",
                    "faValue": "LAND"
                }
            ]
        },
  • Any custom phone purpose from a prior release should be included in the fallback mapping configuration using the PhoneType - Phone PurposeMapping admin entity. This ensures upgrade safety by preserving compatibility with existing data. For example, you introduced a new PHONE_Purpose configuration in a prior release, such as the following:
    {
    “ccsValue”: “TEST_PHONE_CCS”,
    “faValue”: “TEST_PHONE_PURPOSE_FA”
 }
    Then this FA value should be added in the fallback mapping configuration using the PhoneType - Phone PurposeMapping admin entity. The CCS value can be kept as such and the new phone type will be in the faValue place of PHONE_Purpose configuration. For example, use this fallback mapping for the PhoneType and PhonePurpose admin entities:
    {
   "id": "MOBILE",
   "phoneType": "TEST_PHONE_TYPE_FA",
   "phonePurpose": "TEST_PHONE_PURPOSE_FA"

}
    and use this example for the PhonePurpose configuration in the utility configuration:
    {
    “ccsValue”: “TEST_PHONE_CCS”,
    “faValue”: “TEST_PHONE_TYPE_FA”
 }
  • PhoneType - Phone PurposeMapping reference type and PHONE_Purpose configuration must be in sync for flows to work correctly.

Name: EMAIL_purpose

Description: Holds the lookup values for the CONTACT_PURPOSE type.

Example:

"ccsValue": "PRIMARYEMAIL", "faValue": "PERSONAL"

 This refers to the contact purpose specific to the EMAIL contact type. You might not have the same contact purpose names configured in both systems.

Name: WEB_purpose

Description: Holds the mapping of lookup values for the CONTACT_PURPOSE type.

Example:

"ccsValue": "WEB", "faValue": "PERSONAL"

 This refers to the contact purpose specific to the WEB contact type. You might not have the same contact purpose names configured in both systems.

Parent topic: View and Edit the Existing Configuration