Extracting Persons
This topic provides additional details related to extracting Persons from Oracle Utilities Customer Cloud Service for import into Oracle Utilities Digital Asset Cloud Service.
Initial Extract Batch Process
Initial extract files for persons are created using the Migrate Person to DACS Contact (C1-DCTIL) batch process. Use the Batch Control portal to view the parameters used by this batch process. This process should be run only for the initial extract.
Maintenance Object Audit Algorithm
The Sync Person as DACS Contact (C1_DAPERSYNC) audit algorithm tracks new person data and changes to existing person data and creates data synchronization requests, which are used to create incremental extract files.
Sync Request Business Object
Person sync requests are based on the Sync CCB Person to DACS Contact (C1-DACSContactSyncRequest) business object.
Incremental Extract Batch Process
Incremental person extract files are created from sync requests and General Process records using the Contact Incremental Sync Batch Control (C1-DCTEX) batch process. Use the Batch Control portal to view the parameters used by this batch process. This process should be run as needed for incremental updates.
Person (Contact) Extract File Format
Person (Contact) extract files use the following tab-separated values format:
|
Field Name |
Optional/Required |
Notes |
|---|---|---|
| External Reference Id | Optional | The contact's reference ID in the CIS application |
| Change Date Time | Optional |
The date and time on which the contact was changed. Applicable only for Incremental Uploads Will be used to sequence processing in case there are multiple changes to the same contact. |
| Initial Load Sync Flag | Required |
A value that indicates the type of upload. Valid values are:
|
| External Id | Required |
The contact's ID in the CIS application. When importing data from Customer to Meter or Cloud Cloud Service this is the Contact External ID. |
| Contact Type | Required |
The type of contact. When importing data from Customer to Meter or Cloud Cloud Service this will be either Person or Business. If the provided contact type has not been defined as a Program Subscription Contact Type in Digital Asset Management / Digital Asset Cloud Service an extendable lookup is used to map this value to the Contact Type used in Digital Asset Management / Digital Asset Cloud Service. |
| Name | Required | The contact's name. For format for this is <FIRST_NAME> <LAST_NAME> (note the space between them. |
| Home Phone | Optional | A home phone number associated with person-type contacts. |
| Mobile Phone | Optional | A mobile phone number associated with person-type contacts. |
| Phone | Optional | A phone number associated with business-type contacts. |
| Optional | An email address for the contact. | |
| Life Support Sensitive Load | Required |
A flag that indicates if the contact requires a Life Support Sensitive Load. Valid values are "true" and "false" An extendable lookup is used to map this value to the Life Support Sensitive Load flag used in Digital Asset Management / Digital Asset Cloud Service |
| Life Support Sensitive Load Description | Optional | An optional description for Life Support Sensitive Load. |
| Is Erased | Optional |
A flag that indicates if the contact has been obfuscated (if supported) in the CIS application. Valid values are Y/N (Default) Applicable only to Incremental Uploads This should be set to "N" if Object Erasure is not supported in the CIS application. |
Sample Record
Below is a sample file:
EXTREFCON11 2023-06-21T13:15:00-08:00 F1IC EXTCONTACT1 P John Smith (510)777-8888 (510)777-9090 (510)556-4556 johnsmith@gmail.com false None N