Import Initial Contact Data

Before you can begin using Customer Experience for Utilities solutions, you must perform the initial load of contact data into the Oracle Fusion system.

This image shows a simplified example of what the file might look like when you complete these steps:

Figure 5-1 Import Contact Sample File


Example of the contact import file.

  1. Using the method of your choice, export the following data from your Oracle Utilities customer information system (CIS) into a CSV file:

    • Person records with PER_OR_BUS_FLG = P

    If you are using Oracle Utilities Customer Cloud Service, release 24 or later, you can use batch processes provided in the system to export your data. See Exporting Data from Customer Cloud Service.

  2. Update the CSV file so that it contains the following column headings, in this order, and so that the data in the columns represents valid Oracle Fusion values. For additional information about accepted values, see Appendix A: Data Mapping.

    1. SourceSystem - This column should contain the value CIS for all records.

    2. SourceSystemReferenceValue - If you are not using auto numbering, this column should contain the Person ID from your CIS. For example, 0123456789.

    3. PartyNumber - If you are not using auto numbering, this column should contain the values that you want to use. You might use a combination of the SourceSystem column and the SourceSystemReferenceValue column, separated by an underscore. For example, this column might contain CIS_0123456789.

      Oracle Fusion has a Profile Option Code, HZ_GENERATE_PARTY_NUMBER, that controls whether the Party Number (Registry Id) is auto generated or provided. It also controls whether edits to this value are allowed. See "Foundation Profile Options" in the Oracle Fusion Cloud Sales Automation Implementation Reference Guide, available in the Oracle Sales library, located in the Oracle Help Center.

    4. Type - This column should contain the value that you want to use for the ZCA_CONTACT_TYPE of your person records. Valid lookup values are:

      • ZCA_CONTACT

      • ZCA_CUSTOMER

      • ZCA_PROSPECT

      The default value can be set in Oracle Fusion and the field is typically hidden from users so they can't change the value after it is set. See "Set the Default Customer Type" in the Configuring Sales for B2C Guide, available in the Oracle Sales library.

      If you use ZCA_CUSTOMER or ZCA_CONTACT, addresses are not required because person addresses are not included in the data synchronization from your Oracle Utilities system. However, you must set the value for these profile option codes to No, so that the address is not required:

      • ZCA_ACCOUNT_ADDRESS_REQUIRED_ENABLED

      • ZCA_CONTACT_ADDRESS_REQUIRED_ENABLED

      See How Do I Set Up Required Address Option for Accounts and Contacts in the Oracle Fusion Cloud Sales Automation Implementation Reference Guide for additional information.

    5. FirstName - This column should contain the first name of the person.

    6. LastName - This column should contain the last name of the person.

    7. You can include additional columns to import characteristics. When importing characteristics, you must ensure that the column heading is an accepted value in the Oracle Fusion system. For additional information, see Appendix A: Data Mapping.

    8. Import your file into Oracle Fusion. See the Understanding Import and Export Management for Sales and Fusion Service Guide in the Oracle Sales library for instructions.

    9. Verify that the contacts exist in the Oracle Fusion system. For information, see the Managing Contacts topic in the Oracle Sales library.

Parent topic: Initial Data Synchronization