Business Service D1-SendReadsToExtRequester Needs New Elements to Identify Device and Measuring Component for Requester (Doc ID 2222772.1)

Last updated on JANUARY 19, 2017

Applies to:

Oracle Utilities Meter Data Management - Version 2.1.0.3 and later
Information in this document applies to any platform.

Symptoms

In many cases there is a different identifier used to identify a meter or device between the CIS system, the Head End System, and MDM itself. One may use external id on the MC and one may use Channel ID, for example.  During the collection of the reads for this business service the software includes the pre or post-VEE elements which can differ based on the source of the read and how it was entered into MDM. When using D1-SendReadsToExtRequester, there needs to be a predictable way for the requester to have access to its own identifier even if it differes from the head end.

The software should look up (in Service Provider) the Measuring Component/Device identifier used by the Requester and populate consistent elements that the requester can process to resolve the Measuring Component/Device within their system.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms