Maintenance Object Algorithm Type
Algorithm Type
Algorithm Type Description
D1-CONTACT
Specify the maintenance object Audit algorithm configured in the previous section.
D1-SP
Specify the generic maintenance object Audit algorithm D1-ODM-GCDCP. Also specify the D1-ODMSPSyncRequest business object in the Sync Request BO MO Option.
D1-INSTLEVT
Specify the generic MO Audit algorithm D1-ODM-GCDCP. Also specify the D1-InstallEventSyncRequest business object in the Sync Request BO MO Option.
Maintenance Object Algorithms
Configure the maintenance object Audit algorithms.
Maintenance object Audit algorithms contain the logic to instantiate a sync request (as long as one does not already exist in the initial state for the maintenance object-Primary Keys combination).
A generic algorithm F1-GCHG-CDCP comes with the base product and is plugged in on maintenance objects that need to instantiate sync requests for the same maintenance object. This algorithm instantiates the business objects defined in the Sync Request business object maintenance object Option. For more details, refer to the Maintenance Object section. For maintenance objects that have idiosyncratic logic, unique algorithms that contain this logic are used.
For example: Changes to the Contact maintenance object are only communicated to Oracle Utilities Operational Device Management if the Contact is linked to an Service Point.
Algorithm Type
Description
D1-CONCDCSP
Instantiates a Contact-based sync request whenever a change to the Contact maintenance object is detected and the Contact is associated with a service point. Define the sync request business object to be instantiated in the algorithm's parameters.
Extendable Lookups
Configure the following extendable lookups in Oracle Utilities Meter Data Management:
• D1-OkToEnterLookup – Configure the corresponding values from Oracle Utilities Operational Device Management (values are yes or no). Ensure that the values are mapped correctly using the DVM OUTL-BRT-ODM_MDM_OkToEnterCode.
Lookups
Configure the following lookups in Oracle Utilities Meter Data Management:
• DL_LS_SL_FLG – Configure the corresponding values from Oracle Utilities Operational Device Management (values are Life Support or NA). Ensure that the values are mapped correctly using the DVM OUTL-BRT-ODM_MDM_LifeSupportSensitiveLoad.
Menus
Ensure that users have access to the application service D1-GOTOODM. This application service is defined on the business process analysis scripts that take a user from Oracle Utilities Meter Data Management into Oracle Utilities Operational Device Management. The context menu items appear on Contact and Service Point.
Batch Scheduling
The delivered batch codes need no further setup in Oracle Utilities Meter Data Management. The following batch processes can be run from the Batch Submission page.
Note: All sync requests for all objects being synchronized are expected to be present in the Pending state.
The general process flow of the batches for the initial sync request is described as follows.
Batch Processes for Initial Sync Requests
Batch Code
Description
F1-SYSRQ
Transitions all the sync requests out of the PENDING state.
F1-SAKRQ
Pre-allocates the production key to each record and transitions all the sync requests out of the Transformed/Schema Validated state into the Key Allocated state.
D1-SIKDV
Resolves any foreign keys within the schema as well as executes the validation algorithms on the target business objects. This batch code is for processing Device initial sync requests.
D1-SILDV
Loads the records for Device into the production tables.
D1-SIIER
Transitions sync request out of the ERROR state.
 
Note: If any sync requests exist in the Validation Error state after errors have been investigated and resolved, run W1- SIIER to retry the data transformation/schema validation process. If any sync requests exist in the Resolution/Business Object Validation Error state, run its respective W1-SIK* batch job.

Refer to the above table for proper suffix to use for each master data record being synchronized.