Customer Data Extract

Customer information including persons, service points and service agreements in Oracle Utilities Customer Cloud Service (or Oracle Utilities Customer to Meter or Oracle Utilities Customer Care and Billing) can be extracted and sent to Oracle Utilities Digital Asset Cloud Service (or Oracle Utilities Digital Asset Management) for use in enrolling customers in demand response programs.

An initial extract is used to duplicate customer information data as of a given date in Oracle Utilities Customer Cloud Service in Oracle Utilities Digital Asset Cloud Service. This is typically done during initial set up of the Digital Asset Cloud Service implementation.
Following the initial extract, audit algorithms track new data and changes to existing data and create data synchronization requests, which can be used to create incremental extract files via batch processing.

Extracted data is sent to Digital Asset Management in a delimited file, which is uploaded into the system via batch processing and data synchronization. See Importing Customer-Related Data from a Customer Information System in the Oracle Utilities Digital Asset Cloud Service User Guides for more information about the import process.

Extract Process Overview

This section provide an overview of the extract process and outlines the various system objects used for each type of data (contacts, service points, and service agreements). The overall process is as follows:

An initial "extract" batch process is used to extract customer data into files that can be imported into Digital Asset Cloud Service.
Audit algorithms on the Contact, Service Point, and Service Agreement maintenance objects create synchronization requests.
Sync requests are processed using the specific batch processes (a separate batch control is provided for contacts, service points, and service agreements) to create incremental extracts.

Initial Load vs. Incremental Downloads

Customer data can be extracted in one of two modes: Initial or Incremental.

Initial extracts are used when setting up the system to export contact, service point, and service agreement data from Oracle Utilities Customer Cloud Service.

Incremental extracts are used to update customer data in Digital Asset Cloud Service as customer data changes in Oracle Utilities Customer Cloud Service.

Initial Extract Batch Processes

Extract files are created using object-specific "extract" batch processes. See Extract Process Object Summary below for the specific "extract" batch process used for each type of customer data. These are used only for the initial extract.

These processes use the following parameters:

File Name: The name of the extract file. File names can use wildcards (Required)
Flat Path: The file location where the extract file is created. This can be a file location on a local server or a location in Object Storage. See Referencing URIs in the Framework Administrative User Guide for more information. (Required)
File Format: The file format used for extract file. This should be FIXD. Each extract type has its own format.
Low SP Id Override Value: A service point ID used to define the low value in a a range of IDs to limit the data extracted.
High SP Id Override Value: A service point ID used to define the high value in a a range of IDs to limit the data extracted.

Use the Batch Control portal to learn more about these and other parameters used by these batch processes.

Audit Algorithms and Sync Request Business Objects

Sync requests are created by audit algorithms, and are based on data specific sync request business objects. See Extract Process Object Summary below for the specific audit algorithms and "Sync Request" business objects used for each type of customer data.

The table below outlines the stages of the sync request lifecycle. Use the Business Object portal to learn more about these business objects and the details of each lifecycle state.


State	Notes
Pending	Sync requests begin in this state. An Enter algorithms creates the initial snapshot of the Digital Asset Cloud Service (DACS) data (contact, service point, or service agreement). The Sync Request Monitor (F1-SYNRQ) batch process is used to transition sync requests in this state to the Determine if Sync Needed state.
Determine if Sync Needed	An Enter algorithms creates the final snapshot of the DACS data. An Enter algorithms compares the initial and final snapshots. If there is no difference, the sync request moves to the Discarded state. Otherwise, the request moves to the Send Request state,
Discarded	Sync requests for which there is no different between the initial snapshot and final snapshot are sent to this state.
Send Request	An Enter algorithm creates a General Process record for the sync request. The request then moves to the Awaiting Acknowledgement state.
Awaiting Acknowledgement	Requests remain in this state until the system receives an acknowledgement that DACS has received the data contained in the request.
Synchronized	Sync requests enter this state following the Awaiting Acknowledgement state when the system receives an acknowledgement that DACS has received the data contained in the request. If an error occurs, the request moves to the Synchronized with Error state.
Error	Sync requests enter this state if an error occurs while in the Awaiting Acknowledgement state. An Enter algorithm creates a To Do entry.
Canceled	Sync requests enter this state if canceled in either the Error or Synchronized with Error states.
Synchronized with Error	Sync requests enter this state if an error occurs while in the Synchronized state . An Enter algorithm creates a To Do entry.

Incremental Extract Batch Processes

Incremental extract files are created from General Process records using "Incremental Extract" batch processes. See below for the specific "Incremental Extract" batch processes used for each type of customer data. These should be run as needed for incremental updates.

Use the Batch Control portal to view the parameters used by these batch processes.

Extract Process Object Summary

The table below lists the batch controls, algorithms, and business objects used by each type of customer data.


Object Type	Initial Extract Batch Process	Audit Algorithms	Sync Request Business Object	Incremental Extract Batch Process
Person	Migrate Person to DACS Contact (C1-DCTIL)	Sync Person as DACS Contact (C1_DAPERSYNC)	Sync CCB Person to DACS Contact (C1-DACSContactSyncRequest)	Contact Incremental Sync Batch Control (C1-DCTEX)
Service Point	Migrate CCB SP to DACS MSP (C1-DSPIL)	Sync Service Point as DACS Metered Service Point (C1_DASPSYNC)	Sync CCB SP to DACS Metered Service Point (C1-DACSMSPSyncRequest)	SP Incremental Sync Batch Control (C1-DSPEX)
Service Agreement	Migrates SA to DACS Metered Service (C1-DMSIL)	Sync Service Agreement as DACS Metered Service (C1_DASASYNC)	Sync CCB SA to DACS Metered Service (C1-DACSMSSyncRequest)	MS Incremental Sync Batch Control (C1-DMSEX)

Acknowledgement Messages

When Digital Asset Cloud Service processes incremental updates, it can send an acknowledgement back to Customer Cloud Service.

Refer to the Oracle Utilities Customer Cloud Service Integration to Oracle Utilities Digital Assets Cloud Service documentation for more information about configuring Digital Asset Cloud Service to send acknowledgements.