Navigation | Guidelines | Corresponding DVM |
Admin > C > Country | Create the Country codes | OUTL-BRT-ODM_MDM_Country |
Navigation | Guidelines | Corresponding DVM |
Admin > C > Contact Type | Create Contact Types | OUTL-BRT-ODM_MDM_ContactType |
Navigation | Guidelines | Corresponding DVM |
Admin > A > Asset Location Type | Create Asset Location Types | OUTL-BRT-ODM_MDM_SPNodeType |
Navigation | Guidelines | Corresponding DVM |
Admin > T > TimeZone | Create Timezone Types | OUTL-BRT-ODM_MDM_TimeZone |
Navigation | Guidelines | Corresponding DVM |
Admin > A > Asset Type | Create Asset Types | OUTL-BRT-ODM_MDM_AssetDeviceType |
Navigation | Guidelines | Corresponding DVM |
Menu > Asset Management > Specification | Create Specification codes | N/A |
Business Object | Business Object Description |
---|---|
W1-OngoingSyncRequestContact W1-OngoingSyncRequestLocation W1-OngoingSyncRequestAssetNode | Defines the behavior of inbound sync requests. The schema elements define information required to maintain the master data in Oracle Utilities Operational Device Management. As part of sync request processing, an acknowledgment message is sent to the external system (either positive or negative). The “Outbound Message Type” business object option contains a reference to the outbound message business object to use for this purpose. The base package includes business object W1-MDMAssetSyncReqOutMsg to be used on the outbound message type configuration. For more information, refer to the Configuring Outbound Messages section. |
The error states in the ongoing sync requests contain automatic To Do creation and automatic retry. The parameters relevant to these processes (To Do Retry Frequency and To Do Maximum Retries) are captured as business object status options. If your implementation needs to introduce custom values, add a higher sequenced row for the option you need to modify. The algorithms will automatically use these values. The Create To Do algorithm (W1-CRE-SRITD) has been delivered to use the base package supplied To Do Type W1-SYRQI for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters. The monitor process on the initial states of these business objects may be removed by the implementation if immediate processing of the sync requests as they are received is desired. | |
W1-MDMAssetSyncRequest | Defines the behavior of an outbound sync request. The schema elements define the information needed by Oracle Utilities Meter Data Management to maintain device master data. The business object and data area necessary to build the sync snapshot are defined as business object options on the sync request business object. The business object W1-MDMAsset and DA W1-MDMAssetSnapshot are included in the base for use with these options. If your implementation needs to use your own snapshot business object or DA, simply add a higher sequenced row for the relevant option. The Post Service Script for Extract option allows your implementation to perform additional manipulation of the data during the building of the snapshot. The Create To Do algorithm (W1-CRE-SROTD) has been delivered to use the base package supplied To Do Type W1-SYRQO for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters. |
W2-SmartMeter, W2-ManualMeter W2-CommunicationComponent | These base asset business objects need to have the audit plug-in configured to create outbound sync requests. For more details, refer to the Business Object Algorithms section. The sync request business object to use for Oracle Utilities Meter Data Management is defined as a business object Option on these business objects. The base includes W1-MDMAssetSyncRequest for this purpose. |
Algorithm Type | Description for Business Object Algorithm Types |
---|---|
W1-GCHG-CDCP | An audit algorithm that creates a sync request (if there is not already a Pending one in existence) for the particular record being modified. It retrieves the Sync Request business object option from the record's business object. |
W1-EXTSYSRST | A monitor algorithm that sets a timeout limit on the receipt of a response from the external system. It retrieves this timeout limit from the MDM Integration Master Configuration. Use the latter to define the number of hours your implementation wishes to wait for a response from Oracle Utilities Meter Data Management before transitioning the sync request into the Error state. |