Importing Customer-Related Data from a Customer Information System

Import Process Overview

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

1. Data to be imported is exported from the CIS into a tab-delimited values file.

2. An "Upload" batch process is used to create inbound sync requests  in the Pending state based on object-specific initial synchronization business objects. A separate inbound sync request is created for each row in the import file.

3. The inbound sync requests are processed using the Sync Request Monitor (F1-SYNRQ) batch process. 

4. An "Initial Sync Request - Load" batch process is used to create individual master data records from each inbound sync request.

Initial Load vs. Incremental Uploads

Customer data can be uploaded in one of two modes: Initial Load or Incremental. The upload mode is defined by the Initial Load Sync Flag value in the upload file. 

Initial Load uploads are used when setting up the system to import contact, metered service point, and metered service data from a customer information system such as Oracle Utilities Customer to Meter or Oracle Utilities Customer Cloud Service.

Incremental uploads are used to update customer data in Digital Asset Management / Digital Asset Cloud Service as customer data changes in the customer information system. Incremental uploads do NOT use "Import Sync Request - Load" batch processes. Records are added or updated automatically once validated.

Upload Batch Processes

Import files are uploaded using object-specific "Upload" batch processes. See Import Process Object Summary below for the specific "Upload" batch process used for each type of customer data. These should be run as needed for the initial import, as well as subsequent incremental updates. 

These processes use the following parameters:

• File Name: The name of the file to upload. File names can use wildcards (Required) 

• Flat Path: The file location where the upload file is located. 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) 

• Processed File Extension: The text appended to the file name after the file has been processed.  Default is "PROCESSED".

• Error On No Files Found: Indicates whether or not an error is issued if no files are found matching the given name in the given path.  Valid values are "true" (default) and "false".

• External System: The external system that created the upload file (Required)

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

Inbound Sync Request Business Objects

Inbound sync requests are created by the "Upload" batch processes, and are based on "Initial Sync Request" business objects. See Import Process Object Summary below for the specific "Initial Sync Request" business objects used for each type of customer data.

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

Initial Sync Request Load Batch Processes

Master data records are created from inbound sync requests using "Initial Sync Request - Load" batch processes. See below for the specific "Initial Sync Request - Load" batch processes used for each type of customer data. These should be run as needed for the initial import, as well as subsequent incremental updates.

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

Import Process Object Summary

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