Utilities Data Synchronization

When a change is made, or a new record is created in your Oracle Utilities customer information system, the system sends one message for every customer that needs to be synchronized. This message contains all customer-related data. The changed records are marked as pending synchronization.

You then run the sync request batch process (F1-SYNRQ) to generate messages for all pending changes from your Oracle Utilities system since the last batch run. You can schedule this batch process to run as frequently as required.

For ongoing synchronization to occur, you must map business configurations between Oracle Fusion and your Oracle Utilities system so that the right information is transferred and stored with the appropriate values in each system. You use the Fusion CX for Industries Framework Utility Configurations REST Service to configure this value mapping and to define target URLs.

For additional information about this REST service and about person data mapping and configuration, see:

• Manage Integration Configurations

• Appendix A: Data Mapping

• Appendix B: REST APIs

The remaining steps in this topic are written for Oracle Utilities Customer Cloud Service. If you are using another Oracle Utilities customer information system, refer to the documentation for your identity management system to determine how to complete these steps for your implementation. Contact your implementation team for additional assistance.

Service-related updates to customer information that are initiated in the Customer Experience for Utilities solutions follow these high-level steps:

1. Customer service agent accesses a customer record and submits an update, or creates a new customer record. The new or updated record is committed in the Oracle Fusion application by invoking the Oracle Fusion REST API.

2. If the customer record is already linked to a Customer Cloud Service person record, or this is a utilities service-related flow:

   • The Oracle Utilities Person Information Synchronization REST API is invoked with the party number as the external identifier and the person details.

   • If no errors occur, the person identifier is returned, and the customer record in the Oracle Fusion application is updated with the source system reference of the Customer Cloud Service person identifier, which is the system-assigned key for the record.

3. If errors occur from the REST APIs, messages are displayed for the end user to review.

See Appendix B: REST APIs for additional information.

In this section:

• Configure the Data Synchronization Process