Issue With UOM Assignment In The D6-CCOMPEVDR Script
(Doc ID 2803735.1)
Last updated on AUGUST 31, 2021
Applies to:
Oracle Utilities Customer Cloud Service - Version 21A to 21B [Release 21]Oracle Utilities Meter Data Management - Version 2.4.0.0.0 to 2.4.0.0.0 [Release 2.4]
Information in this document applies to any platform.
Symptoms
When receiving a response from the Sensus RNI head end system for an On-Demand reading the Sensus RNI sends a reading changed notification. C2M determines the unit of measure by using the <units> value. After speaking with Sensus this has been determined to be a problem as the <fieldName> and <readingTypeCode> values can vary while the <units> value stays the same and doesn’t note whether the utility has be received or delivered.
The unit of measure is determined in the D6-CCOMPEVDR script during the Create Completion Events Lifecyle state of D6-ReadingChgNotificationDR. We believe the script should use the <readingTypeCode> value as this can be configured via extendable lookup to provide a more specific unit of measure.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |