Configuring Admin Data
To configure the Oracle Utilities Customer Cloud Service setup for the integration:
1. Login to Oracle Utilities Customer Cloud Service.
2. Create message senders. Refer to the
Message Senders section for details.
4. Create an external system. Refer to the
External System section for details.
7. Create activity types. Refer to the
Activity Types section for details.
Message Senders
This section provides the message sender configuration details in Oracle Utilities Customer To Meter and Oracle Utilities Customer Cloud Service.
Configuring Message Sender in Oracle Utilities Customer To Meter
Create a new message sender for each integration service initiated from Oracle Utilities Customer To Meter.
To create a message sender:
1. Navigate to the Message Sender page from the Admin menu or from the Search menu.
2. Enter a unique message sender and its description.
3. Populate the following values:
• Invocation Type - Real-time
• Message Class - SOAPSNDR
• Active - Select the checkbox.
• MSG Encoding - UTF-8 message encoding
4. Select the Context tab and set values for the following context types:
• HTTP Header - SOAPAction:"<operation name in OIC Activated Integration wsdl url>"
• HTTP Login User - User ID to access the Oracle Integration for Cloud (OIC) flow
• HTTP Password - Password to access the OIC flow
• HTTP Method (POST/GET) - POST
• HTTP Timeout - 60
• HTTP Transport Method - SendReceive
• HTTP URL 1 - Set the Activated Integration end point URL by removing the ?wsdl from the URL.
If the URL value does not fit, use the additional HTTP URL types to set the complete URL.
• Message Namespace URI - Provide the namespace of the schema in the respective integration process.
• SOAP Insert Timestamp (Y/N) - Y
• Sender Security Type - TEXT
Important! Make sure the namespace does not include any extra spaces. Copy the namespaces into Notepad to check for any extra spaces.
Message sender configuration for integration services
Configuring Message Sender in Oracle Utilities Customer Cloud Service
Create a new message sender for each integration service initiated from Oracle Utilities Customer Cloud Service.
To create a message sender:
1. Navigate to the Message Sender page from the Admin menu or from the Search menu.
2. Enter a unique message sender and its description.
3. Populate the following values:
• Invocation Type - Real-time
• Message Class - SOAPSNDR
• Active - Select the checkbox.
• MSG Encoding - UTF-8 message encoding
4. Select the Context tab and set values for the following context types:
• HTTP Header - SOAPAction:"<operation name in OIC Activated Integration wsdl url>"
• HTTP Login User - User ID to access the Oracle Integration for Cloud (OIC) flow
• HTTP Password - Password to access the OIC flow
• HTTP Method (POST/GET) - POST
• HTTP Timeout - 60
• HTTP Transport Method - SendReceive
• HTTP URL 1 - Set the Activated Integration end point URL by removing the ?wsdl from the URL.
If the URL value does not fit, use the additional HTTP URL types to set the complete URL.
• Message Namespace URI - Provide the namespace of the schema in the respective integration process.
• SOAP Insert Timestamp (Y/N) - Y
• Sender Security Type - Basic
Message sender configuration for integration services
Outbound Message Types
To create a new outbound message type for each integration process:
1. Navigate to the Outbound Message Type page from the Admin menu or from the Search menu.
2. Enter an outbound message type, description, and detailed description.
3. Select the outbound message business object created for a specific service.
Outbound message types for integration services
External System
To create a new external system to support the integration:
1. Navigate to the External System page from the Admin menu or from the Search menu.
2. Enter a unique external system and description.
For example: Name = INT_OFSC_ES, Description = OFSC External System
3. Set the Our Name in Their System field to C2M.
4. Associate the outbound message types and message senders created to the external system.
For each outbound message type, set the following:
• Outbound Message Type - Outbound message type created for the respective integration service
• Processing Method - Real-time
• Message Sender - Set the message sender created for the integration service
• Date/Time Format - XSD
• Namespace Option - Configured on sender
For more information about message senders and outbound message type for each integration service, refer to the
Message Senders and
Outbound Message Types sections respectively.
External system configuration for integration services
Example External System - INT_OFSC_ES
External Application
Create an external application with the respective external system reference and add processing roles to invoke each integration service.
To create a new external application to support the integration:
1. Navigate to the External Application page from the Admin menu or from the Search menu.
2. Enter a unique external application and description.
For example: Name = INT_OFSC_EA, Description = INT_OFSC External Application - Field Work System
3. Set the Our Name in Their System field to C2M.
Note: The same value should be configured in the source.system property in the SOMOFSC_ConfigProps lookup in Oracle Integration Cloud.
4. Select the External System as <external system> created for this integration. For details about external system, refer to the
External System section.
For example: INT_OFSC_ES
5. Select Utility Device ID Type as Badge Number.
6. Click Save.
7. Under Processing Method List, add Processing Method for each integration service.
8. Associate the outbound message types and message senders to the external system. For each outbound message type, set the following:
• Processing Role - Select the relevant processing role.
• Business Object - Select the business object to generate the outbound message.
• Description - Describe the processing method
• Status - Active
• Default Business Object - Select the business object for the respective outbound message type.
• Default Outbound Message Type - Outbound message type for the respective integration service.
Master Configuration
The master configuration has the necessary information to support this integration.
1. Navigate to the Master Configuration page from the Admin menu or from the Search menu.
2. Select Service Order Management Master Configuration.
3. Click + next to Service Order Management Master Configuration.
4. In the Master Configuration Details zone, configure the following values.
a. In the Main section:
a. Field Work System = Refer to the external application created in the
External Application section. <External Application name>
For example: INT_OFSC_EA
b. Near Schedule Meter Read Search (Days) = 5
b. In the Completion Event Exception Handling section:
a. To Do Type = Activity To Do Type
b. To Do Role = System Default Role
c. Maximum Retries = 2
d. Retry Frequency = 00:05:00
c. In the Management Dashboard Configuration section:
a. Number of Days to Consider for Snapshot = 7
b. Weekends/Holidays Inclusion in Activity Duration = Exclude from Activity Duration
c. Work Calendar = US Bank Work Calendar
d. Default Expected Activity Completion Time (Hours) = 3
d. In the Appointment Handling section:
a. Appointment Slot Request (Hours) = 360
b. Default Appointment Handling System = <External Application name>
Example: INT_OFSC_EA
e. In the Cut for Non-Payment Service Restrictions section:
a. Life Support/Sensitive Load Option = Allow Cut Service
f. In Override Expected Completion Time Configuration section:
a. Activity Type = SOM_FIELD_ACTIVITY_TYPE
b. Task Type = Read Meter
c. Expected Completion Time (Hours) = 60
g. In the Hours Beyond Expected Activity Completion Time section:
a. On Time Completion Tolerance = 8
b. Late Completion Tolerance = 16
c. Very Late Completion Tolerance = 24
d. Normal In Progress Time = 8
e. Long In Progress Time = 16
f. Very Long In Progress Time = 24
h. In the Update Statistics section:
a. Batch Control = D1-ACTAG
i. In the Chart Options section:
a. Number of Historical Days to Include in Summary Charts = 12
j. In the Summary To Do Types section:
k. In the FA Cancelability Criteria section:
a. FA Cancellable Script = Determine FA Cancellability
Note: The values configured in the above master configuration section are the sample values for reference.
Activity Types
An activity type defines the properties common to a specific type of activity.
To create an activity type:
1. Navigate to the Activity Type page from the Admin menu or from the Search menu.
2. Enter the activity type and its description as appropriate.
The activity type includes the following:
The Field Task types are available as part of the following extendable lookup.
Business Object: D1-FieldTaskTypeLookup
Description: Field Task Type
The following activity types are supported in this integration:
• Turn on Pilot Light
• Service Investigation
• Trim Tree
• Disconnect SP at Device and Remove Device (Item)
• Item Exchange
• Connect SP at Item
• Meter Exchange
• Meter Read
• Disconnect SP at Meter and Remove Meter
• Connect SP
• Meter Install
• Disconnect Warning
• Maintain SP and Meter at Equipment
• Meter Inspect
• Meter Test
For Oracle Utilities Operational Device Management activity support ensure the following setup is present:
1. In the Oracle Utilities Customer to Meter Field Task Type section:
a. Navigate to Admin menu > E > Extendable Lookup > search for the “D1-FieldTaskTypeLookup” business object.
b. Select the respective Field Task Type.
c. Edit the Field Task Type.
d. Enable the Maintain As Asset Activity Type option as Yes.
e. Add the Asset System Data Retriever processing script.
f. Verify if the Asset Activity Type is mentioned.
2. In the Oracle Utilities Operational Device Management Asset Activity Type section:
a. Navigate to Admin menu > A > Asset Activity Type.
b. Select and edit the Activity Type.
c. Enter “Create Any Service History” in the Completion Event Type field.
3. In the Oracle Utilities Customer to Meter Device Type section:
a. Enter “Tracked by ODM” in the Track Location field.
4. In the Oracle Utilities Operational Device Management Asset Type section:
a. Add Service History Type under the Valid Service History Types section.