Configuring the Sync Request Process

The Sync Request process is used to synchronize customer data from Oracle Utilities Customer to Meter to Oracle Utilities Network Management System.

For Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management (separate instance) implementations, this is configured in Oracle Utilities Meter Data Management.

Batch Code

This is the batch process to run the synchronization request. It is a generic batch process that is used for different synchronization processes. It has a couple of parameters that can be used to control which synchronization request BOs to process.

Batch	Description
F1-SYNRQ	Sync Request Monitor Process

Batch Parameters	Parameter Description	Value
maintenanceObject	Sync Request maintenance object	F1-SYNC REQ This is the defaulted value.
isRestrictedByBatchCode	The ‘true’ value restricts processing to sync requests whose current state is linked to this batch code.
restrictToBusinessObject	Enter a business object code here to limit the process to sync requests linked to this business object.	D1-NMSSP CustomerSyncRequest Populate this value to run only the NMS customer sync request.
restrictToBOStatus	Enter a status code here to limit the process to sync requests in this state.	PENDING Populate this value to only process a sync request in ‘Pending’ status.

This batch process is used to run the initial load synchronization request. It has a couple of parameters that can be used to control which synchronization request BOs to process.

Batch	Description
D1-NMSSP	NMS SP Customer Sync Initial Load

Batch Parameters	Parameter Description	Value
syncRequestMO	Maintenance Object	D1-SP This is the defaulted value.
syncRequestBO	Enter a business object code here to limit the process to sync requests linked to this business object.	D1-NMSSPCustomer SyncRequest
filterAlgorithm	Enter a filter algorithm here to limit the process to sync requests that should be sent to Oracle Utilities Network Management System.	D1-NMSSPCustomerSync Request This algorithm filters for eligible service point types as defined in the NMS Sync Integration Master Configuration.

MO Algorithms

Configure the MO Audit algorithms. MO Audit algorithms contain the logic to instantiate a sync request (as long as one does not already exist in the initial state for the MO-Primary Keys combination). A generic algorithm F1-GCHG-CDCP comes with the base product and is plugged in on MOs that need to instantiate sync requests for the same MO. This algorithm instantiates the BOs defined in the Sync Request BO MO Option. For MOs that need a sync request instantiated for a different MO (for example: changes to the Person or Account MO need to be communicated via an SP sync request) need unique algorithms that contain this logic.

For more information, refer to the Maintenance Objects section.

Algorithm Type	Description
D1-CUSCDCSP	This algorithm instantiates SP-based sync request whenever a change to the Contact MO is detected (updating a person record in CCS/C2M triggers an internal sync to the contact record, which in turn will trigger this audit algorithm). Define the D1-NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters.
D1-USCDCSP	This algorithm instantiates SP-based sync request whenever a change to the Usage Subscription MO is detected (updating a SA record in CCS/C2M triggers an internal sync to the usage subscription record, which in turn will trigger this audit algorithm). Define the D1- NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters.
D1-SPIE-CDCP	This algorithm instantiates SP-based sync request whenever a change to the Install Event MO is detected. Define the D1- NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters.
D1-SPDV-CDCP	This algorithm instantiates SP-based sync request whenever a change to the Device MO is detected. Define the D1- NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters.

Maintenance Objects

Maintenance Objects	Description
D1-CONTACT	Specify the MO Audit algorithm configured in the MO Algorithms section.
D1-US	Specify the MO Audit algorithm configured in the MO Algorithms section.
D1-INSTLEVT	Specify the MO Audit algorithm configured in the MO Algorithms section.
D1-DEVICE	Specify the MO Audit algorithm configured in the MO Algorithms section.
D1-SP	Specify the generic MO Audit algorithm F1-GCHG-CDCP. Also, specify the D1-NMSSPCustomerSyncRequest BO in the Sync Request BO MO Option.

Business Objects

Business Object	Description
D1- NMSSPCustomer SyncRequest	This business object defines the behavior of the outbound sync request for NMS. It contains the schema elements monitored and synchronized to NMS. The following must be configured and defined on the NMS Sync Integration master configuration as they are necessary to create the outbound sync request: • Outbound Message Type: This contains a reference to the outbound message BO to use. The base package includes BO D1- NMSSPCustomerSyncReqOutMsg for the NMS SP Sync. Refer to the Defining Outbound Message Types section in the user documentation for more information. • External System: This contains the reference to the outbound message type and its corresponding configuration for communicating with the external system. Refer to the External Systems section in the user documentation for more information. • Specify the pre-processing algorithm configured in the MO Algorithms section. • Specify the time out algorithm as a monitor algorithm on the Awaiting Acknowledgement state for this BO. • Specify the To Do creation algorithm on the Error state for this BO. Depending on the technology used to communicate the sync request to the external system, you may need to create your own enter algorithm and plug it into the Send Request state.

Business Object

Description

D1- NMSSPCustomer SyncRequest

This business object defines the behavior of the outbound sync request for NMS. It contains the schema elements monitored and synchronized to NMS.

The following must be configured and defined on the NMS Sync Integration master configuration as they are necessary to create the outbound sync request:

• Outbound Message Type: This contains a reference to the outbound message BO to use. The base package includes BO D1- NMSSPCustomerSyncReqOutMsg for the NMS SP Sync. Refer to the Defining Outbound Message Types section in the user documentation for more information.

• External System: This contains the reference to the outbound message type and its corresponding configuration for communicating with the external system. Refer to the External Systems section in the user documentation for more information.

• Specify the pre-processing algorithm configured in the MO Algorithms section.

• Specify the time out algorithm as a monitor algorithm on the Awaiting Acknowledgement state for this BO.

• Specify the To Do creation algorithm on the Error state for this BO. Depending on the technology used to communicate the sync request to the external system, you may need to create your own enter algorithm and plug it into the Send Request state.

For more information about the sync request process, the business objects, maintenance objects, and other components use for this process, see the Data Synchronization section in the Oracle Utilities Framework Administrative User Guide.