Provide Oracle Utilities Customer Care and Billing with Additional Completion Information
Follow this procedure to extend the activity completion information captured by the crew and sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Customer Care and Billing.
The process describes how to extend Oracle Utilities Mobile Workforce Management business objects and their user interface as well as the integration outbound messages with your custom elements.
If the information is not already processed by the FA Completion logic in Oracle Utilities Customer Care and Billing the procedure describes how to extend the FA Completion business object to handle such logic.
Extending Oracle Utilities Mobile Workforce Management Business Objects
To extend the Oracle Utilities Mobile Workforce Management business objects you must first extend the data structures by creating CM data areas, and then extend the user interface.
Extending the Data Structures
Create CM data areas and use them to extend the corresponding Oracle Utilities Mobile Workforce Management data areas. After this is done, implement the relevant CM UI Map Fragments.
Refer to the List of Available CM Extended UI Map Fragments in Oracle Utilities Mobile Workforce Management for the exact fragment names.
Type of Information
How to Extend
Common
Completion Details
For completion details common to all activity types extend the base
M1-CommonActivityIntCmplDtls data area.
The base data area is already included in all base assignment business objects so extending it automatically extends all these business objects. It is also included in the outbound message sending completion information to the host system so the service is automatically extended as well.
Service Point, Meter or
Item Details
For service points, meter or item completion information extend the respective corresponding data area:
• Service Point (M2-SPDataDetails)
• Meter (M2-MeterDataDetails)
• Item (M2-ItemDataDetails)
These data areas are already included in relevant base activity and assignment business objects so extending them automatically extends all these business objects.
These data areas describe the entity. They are included once on the activity and assignment business objects to describe information as sent from the host.
 
They are included once more in the assignment completion group of information to capture modifications to these details made by the crew.Information as sent from host is assumed to be displayed as read only whereas the modifiable copy of the details may be presented as editable as needed. When designing your custom UI map fragments choose which completion details are editable.
Custom Assignment
Business Object Completion Details
If certain completion details are relevant to a specific type of activity that is not provided with the base product you need to design and configure custom activity and assignment business objects to handle such an activity. Use custom data areas to describe the details captured by the crew for this type of activity and include them in your assignment business object.
the Oracle Utilities Mobile Workforce Management configuration guide for more information on how to design new custom activity business objects.
Once custom business objects are configured you need to extend the activity completion outbound message to accommodate your custom completion details. To do that you need to extend the M2-CompletionDetails data area with your custom data area.
Extending the User Interface
Implement assignment CM UI Map Fragments to display your custom details as needed. Refer to the List of Available CM Extended UI Map Fragments in Oracle Utilities Mobile Workforce Management for the exact fragment names.
Extend the Field Activity Completion Process in Oracle Utilities Customer Care and Billing
To extend the field activity completion process in Oracle Utilities Customer Care and Billing you must first extend the field activity completion message then extend the field activity completion rules.
Extending the Field Activity Completion Message
Type of Information
How to Extend
Service Point, Meter or
Item Details
Create a CM service point, meter or item data area with the same details as the corresponding Oracle Utilities Mobile Workforce Management CM data area and use it to extend these data areas:
SP(C1-FWSPBODetails)
Meter(C1-FWMeterBODetails)
Item(C1-FWItemBODetails)
These data areas are included in a corresponding business object used to update the entity. By extending these base data areas you automatically extend the entity business object and hence when the object is updated so are the custom details.
 
Create another service point, meter or item interface data area and include in it the corresponding CM data area you have just created for the business object update. Use this to extend the interface data areas:
Service Point (C1-FWSPInterfaceDetails)
Meter (C1-FWMeterInterfaceDetails)
 
Item (C1-FWItemInterfaceDetails)
The interface data area includes the business object data area to ensure they have same elements allowing each to extend another data area.
Other
Completion Details
For completion details common to all activity types create a custom data area and use it to extend the base data area:
C1-FACompletionCommonDetails
For activity type specific details create a activity specific custom data area and use it to extend the base data area:
C1-FACompletionActSpecDetails
Refer to Extending Field Activity Completion Rulesfor more information on how to process this additional information.
Note. You must use the same element names as in both Oracle Utilities Customer Care and Billing and Oracle Utilities Mobile Workforce Management. If element names are different, implementations will be able to pass data between applications using the standard PIP implementation approach, but not the simplified bypass approach.
Extending Field Activity Completion Rules
The FA Completion message is stored as a Sync Request record and processed by the FA Completion business object (C1-FieldActivityCompletion).
If you have extended the FA Completion message with other completion details extend the FA Completion business object with a custom "Enter" plug-in on the Process Message state to process these details as needed.
Since the completion process is managed by a business object you may leverage other extension techniques to replace base rules with your own custom rules as needed.
To process the additional information, extend the FA Completion business object rules on C1-FieldActivityCompletion.
Example: Add an “Enter” plug-in on the Process Message state to process your custom information as needed.
Configure To Do Type/ To Do Role Related to the Extended Functionality
Create the To Do Type, To Do Role, and Error Message (as needed) to be used to create the following:
• Crew follow up request (To Do type)
• FA completion error (To Do type)
Appropriate To Do roles must be created to handle To Do entries created for these To Do Types coming from the external systems. Navigate to the To Do Type portal under the Admin menu to create these roles.
Configure Customer Contact Class and Type Related to the Extended Functionality
Define customer contact types in Oracle Utilities Mobile Workforce Management for the conditions that create customer contacts for the following:
When crews complete activities, they have the option to record contact that they made with customers. This information is set to Oracle Utilities Customer Care and Billing as part of the field activity completion process. The system creates a Customer Contact record for the person associated with the field activity.
Since Oracle Utilities Mobile Workforce Management does not send the customer contact class with the contact update, Oracle Utilities Customer Care and Billing needs to be configured to default the customer class. To implement this connection:
Set up a customer contact class to represent contacts made in the field.
Navigate to Feature Configuration and select the Schema Constant record and reference that customer contact class as the value for the customer contact class option. The system uses the value referenced on the schema constant feature configuration as the default customer contact class when creating customer contacts.